When setting the IP addresses for Wireguard interfaces it works only for the first 10 networks.
I set 192.168.1.1/30, 192.168.1.5/30, …, 192.168.1.37/30 and this ranges work.
But 192.168.1.41/30 and so on doesn’t work.
So I can connect to Wireguard with the peer that has 192.168.1.42 and ping 192.168.1.41, but the other addresses 10.0.0.x i cannot ping.
If I change the IP to 192.168.2.1/30 then it works.
Is this a bug? A design limit?
Most likely a config/user error.
Where? The firewall rules are disabled for testing. The connection is active. Changing IP works. Maybe on the wireguard client on the windows pc?
Show the edited configs and I’m sure that the problem will show itself.
Really, if you know where the problem is then fix it, if not show the configs so we can help parse out the problem area(s).
Found, a so banal thing…
I molim vas, što bi to bilo???
Treba li se zapitati, previše pristojnosti da to zapišete?
Laku noc…
And please, what would it be???
One has to wonder, too polite to write it down?
He fixed a bug in the kernel.
![]()
unexpected
You couldn’t find anything more banal that that? ![]()
@rextended… I think Znevna nailed it on his first post!