Looks like this when you right-click the tailscale icon

OMG i never knew that since I never used it for an exit node @User

Im going to look into netmaker regardless looks cool and selfhosted

@User for any local routes, Netmaker will detect if it has the local range and will not use the gateway

Perfect

@User not sure I’m understanding your scenario entirely. You’re looking to route outbound traffic to a specific set of IPs through a specific node? If so, yes you can do that with egress

@User This is the setup I am looking for: - PrivateNet1 \ / PublicIP#1 Home VM = - PrivateNet2 - = NetMaker (OVH VPS) - - PublicIP#2 - PrivateNet3 / \ PublicIP#3 - PrivateNet4 / \ PublicIP#4

Basically I need all traffic in each private subnet to go out through a specific public IP on the netmaker endpoint, and vice versa

I also need IPv6 traffic to exit through a single IPv6 public IP on the VPS

If the traffic from my service doesn't go out through the right IP address on the VPS, the service I run fails to work

I don't need the public IPs to show up on the VM, I just need something to route the traffic through that VPS onto the right IP back and forth via NetMaker's private network and out

I tried to add an egress rule with the public IP as a /32 under the nodes section, but it fails to create it and I get RTLINK error messages in the docker logs when it tries to bind the IPv6 private IP

Happy to chip in a few coffees if anyone can help me figure this out

These are the IPs on the VPS where NetMaker is installed

So I have 9 IPv4 /32's and 1 IPv6 /128 on the same network interface

I have 8 NetMaker private networks, and for each, I need the egress and ingress traffic to come through their own IP on that same interface. For all those networks, I also need the outgoing and incoming traffic to go through that single IPv6 address

When adding IPv6 during the network creation step, I also get this in the docker logs

For incoming connections, I plan on having HAProxy sit in front of NetMaker on the VPS to relay traffic to the local private IPs on the VM

The reason I'm doing all of this rather than a GRE or regular IP tunnel is due to the fact that the VM at home is behind a dynamic IP, so I need something that can communicate back with the VPS and re-establish connection ASAP when that happens.

Does anyone know how one person would go about setting up Egress & Ingress rules in this case? The documentation on the website is lacking in this area and I couldn't find anyone else with the same issue I'm facing under GitHub

Or is this more complex and I need to pay for support?

I think yours is fairly complex yes

@User That is indeed complex and not something Netmaker handles natively. If the public IP's were on different interfaces that would do it. Luckily, Netmaker has a PostUp and PostDown section in the UI that can run arbitrary commands. When you create a gateway, you'll see iptables rules get created there. You should be able to just modify those rules in the UI to specify the exact IP address that forwarding should use.

I just finished watching the site to site video on youtube but was still left confused as there seemed to be 2 situations in that. Would love some help. I want to set up a site to between 2 LANs and access the entire subnet from each using a single node on each side. This is dooable? LAN 192.168.10.0/24 and Remote LAN 192.168.0.0/24 Am I to create a new Network or just add nodes?

Or do I make two networks marked as local?

can you run the netclient on your routers?

Both sides have opnsense

but I also have promox on each side so thought about running the nodes in lxc containers

im trying trying to relate the setup of netmaker, to what I had when I used wireguard on its own

before, did you set it up on the routers?