I wanted to know whether netmaker supports routing traffic through another available path in a mesh network when vpn tunnel goes down between specific peers in a mesh network.
Assume netmaker full mesh network consists of 4 nodes -
A (192.168.0.1/24)
B (192.168.0.2/24)
C (192.168.0.3/24) (lan: 192.168.3.0/24)
D (192.168.0.4/24)
Node C is an egress node with lan network. I want to route traffic from B to C for lan subnet (192.168.3.0/0) through A or D when B to C tunnel goes down.
One way I could do this is by making node A or D as egress node and advertise specific /32 IP from C's lan subnet e.g. 192.168.3.2/32 which installs a new static route on each node for 192.168.3.2.
Advertising individual IP addresses is tedious process so I was wondering if I could advertise entire lan network 192.168.3.0/0 through A which should act as backup route so that I don't have to specify individual IPs and traffic is routed through backup route when B to C tunnel goes down.
Currently advertising same network through different egress nodes is not working as expected as its breaking the routing for origin nodes LAN users.
Contact Details
No response
What happened?
I wanted to know whether netmaker supports routing traffic through another available path in a mesh network when vpn tunnel goes down between specific peers in a mesh network.
Assume netmaker full mesh network consists of 4 nodes -
Node C is an egress node with lan network. I want to route traffic from B to C for lan subnet (192.168.3.0/0) through A or D when B to C tunnel goes down.
One way I could do this is by making node A or D as egress node and advertise specific /32 IP from C's lan subnet e.g. 192.168.3.2/32 which installs a new static route on each node for 192.168.3.2.
Advertising individual IP addresses is tedious process so I was wondering if I could advertise entire lan network 192.168.3.0/0 through A which should act as backup route so that I don't have to specify individual IPs and traffic is routed through backup route when B to C tunnel goes down.
Currently advertising same network through different egress nodes is not working as expected as its breaking the routing for origin nodes LAN users.
Let me know if this can be implemented more.
Version
v0.21.0
What OS are you using?
Linux
Relevant log output
No response
Contributing guidelines