WireGuard Allow routing between clients (How?)

[ZebraOnPC]

i have a server and 2 clients
it has been a week i tried to connect 2 client through the server.
Packets go beetwin server networks and clients but not beetwin clients
What did i missed ?
all networks are defferent

22.0/24 server (9.1/32)

33.0/24 client 1 (9.2/32)
44.0/24 client 2 (9.3/32)

LAN and VPN in one firewall zone on server and clients

[orangepizza]

client should other clinets as peer in their config file too

[vgaetera]

Add each client subnet to the allowed IPs in the respective peer on the server.

[ZebraOnPC]

I just got it works!! finaly!
i just had to add client 1 vpn ip to client 2 allowed IPs
adn client 2 vpn ip to client 1 allowed IPs

[ZebraOnPC]

Yes
Allowed IPs
on client1
192.168.22.0/24 -server subnet
192.168.9.1/32 - server vpn IP
192.168.222.0/24 -client2 subnet
192.168.9.3/32 - client2 vpn IP
but i dont understand why i cant just type 192.168.9.0/24 instead

[vgaetera]

Star network

This is an implementation of a star network topology using WireGuard:

# server
192.168.9.1/24 - VPN
192.168.22.1/24 - LAN
# server_peers > client1 > allowed_ips
192.168.9.2/32
192.168.33.0/24
# server_peers > client2 > allowed_ips
192.168.9.3/32
192.168.44.0/24

# client1
192.168.9.2/24 - VPN
192.168.33.1/24 - LAN
# client1_peers > server > allowed_ips
192.168.9.0/24
192.168.22.0/24
192.168.44.0/24

# client2
192.168.9.3/24 - VPN
192.168.44.1/24 - LAN
# client2_peers > server > allowed_ips
192.168.9.0/24
192.168.22.0/24
192.168.33.0/24

[ZebraOnPC]

But i really dont understand why i cant add on server in peer 192.168.9.2/24 but 192.168.9.2/32
but on clent i can use 24 mask

[vgaetera]

Both clients connect to the same server simultaneously.
They should be declared with non-overlapping ranges.
This is required to avoid routing collisions.