netbirdio
Allow traffic from Network Resource to Netbird Clients
Is your feature request related to a problem? Please describe. I can't route traffic from an internal resource (no netbird client installed) to a netbird client using a subnet router
Describe the solution you'd like A feature which allows routing of traffic from an internal resource to a netbird client via a subnet router
Describe alternatives you've considered Putting the internal resource into AWS so that it can have the netbird client installed. We have tried to install the Netbird client onto the internal resource however this does not work for us as U-TURN NAT does not work.
@stan-smith
That's where I was struggling, too. This was working in the past. It works with Masquerading/NAT, but I don't want to NAT. I want to see the real IP. My setup:
- OPNsense with Netbird 0.59.8, offering a network (i.e. 10.10.1.0/24)
- VPS with Netbird client, 0.60.7, without any other networks to route
The VPS gets the route and is able to ping ressouces in the 10.10.1.0/24 network directly. But the other way around simply won't work. I can see the packets on the OPNsense leaving through the wt0 interface, all looks fine. When I enable NAT for this connection, it starts to work. But at the cost, that I don't see the real client IP on the VPS, only the 100.x address from the OPNsense.
Tried both ways: Network routes and networks.
And there is no policy option to select the network resource as source, only as destination. Maybe that's the missing piece in the puzzle?
Same issue, we set up a route to the routing peer for the subnet the netbird clients use... but avail. This is with mascaraing disabled for the specific network resource vlan... We need to respond to the IP we receive the request from, its sent to a different udp port than the original request is sent at.
