issue with routing masquerading off

[hacklhar]

Hi guys, we´ve following setup

Client A (Peer) , netbird agent installed, private ip 192.168.0.65, netbird ip 100.84.174.255 Client B (Routing Peer), netbird agent installed, private ip 10.40.2.4, netbird ip 100.84.174.207 Client C (Webserver), no netbird agent installed, private ip 10.40.4.4

If we add routes for 10.40.2.0/24 and 10.40.4.0/24, masquerading enabled on manager and add Client A & Client B to the Distribution group. We are able to communicate between Client A and Client B (via private ip and netbird ip), and it´s also possible to communicate from Client A to Client C. But Client C can´t reach Client A.

If we add routes for 10.40.2.0/24 and 10.40.4.0/24, masquerading disabled on manager and add Client A & Client B to the Distribution group. We are able to communicate between Client A and Client B (via private ip and netbird ip). But now we are unable to communicate from Client A to Client C and vice versa.

We tried to add a manually route on Client C for the netbird vpn subnet, to route the traffic to routing peer 10.40.2.4. But this is also not working.

We didn´t find more details about the required configuration in the documentation. Would be great if someone has an idea to solve the routing issue.

Regardsm Harald

[hacklhar]

Sorry forget to mention our goal ;) We need to communicate from Client A to Client C and vice versa while masquerading is disabled

[Hobby-Student]

I just tried the same and got the same result. I'd love to see A<->C (in both directions) communication working until the BSD (opnsense) client is fully working.