Page 1 of 1
Recursive route with %interface
Posted: Wed Mar 07, 2018 1:45 pm
by thomsen
I have several WANs interfaces and two of them have common gateway. In route list i use this gateway 1.1.1.1%eth2 - and next one 1.1.1.1%eth3
I'd like use the recursive routing but it doesn't work in my configuration (%interface). Does someone have any idea? Netwatch?
Re: Recursive route with %interface
Posted: Wed Mar 07, 2018 10:08 pm
by sindy
I have several WANs interfaces and two of them have common gateway. In route list i use this gateway 1.1.1.1%eth2 - and next one 1.1.1.1%eth3
I'd like use the recursive routing but it doesn't work in my configuration (%interface). Does someone have any idea? Netwatch?
The first question is what is your use case. As the two WAN interfaces have the same gateway, it means that they are in the same subnet. So if the gateway device or something else inside the ISP's network fails, both recursive routes which use that gateway fail regardless via which physical interface they go. So from this perspective, there is no point in having one of them as a backup for the other one. So I would bond the two physical interfaces together, to have a backup at LAN level, and if you need to use both IP addresses, attach both to the bond interface. The only obstacle here might be if you receive both addresses using DHCP.
Re: Recursive route with %interface
Posted: Thu Mar 08, 2018 2:55 pm
by thomsen
I have several WANs interfaces and two of them have common gateway. In route list i use this gateway 1.1.1.1%eth2 - and next one 1.1.1.1%eth3
I'd like use the recursive routing but it doesn't work in my configuration (%interface). Does someone have any idea? Netwatch?
The first question is what is your use case. As the two WAN interfaces have the same gateway, it means that they are in the same subnet. So if the gateway device or something else inside the ISP's network fails, both recursive routes which use that gateway fail regardless via which physical interface they go. So from this perspective, there is no point in having one of them as a backup for the other one. So I would bond the two physical interfaces together, to have a backup at LAN level, and if you need to use both IP addresses, attach both to the bond interface. The only obstacle here might be if you receive both addresses using DHCP.
It's not about that. For failover i have a different ISP (additional 3rd interface)
Eth1-Backup-ISP2
Eth2-Company1-ISP1
Eth3-Company2-ISP1
I use this configuration because one organization include two small companies and each has its own connection to the ISP with different tariffs and bandwidth.
The problem is that if i use the gateway like [1.1.1.1%eth2] the recursion does not work (route is unreachable). Either here i need to do something differently, or use a netwatch.
Re: Recursive route with %interface
Posted: Thu Mar 08, 2018 3:54 pm
by sindy
I have several WANs interfaces and two of them have common gateway. In route list i use this gateway 1.1.1.1%eth2 - and next one 1.1.1.1%eth3
I'd like use the recursive routing but it doesn't work in my configuration (%interface). Does someone have any idea? Netwatch?
The first question is what is your use case. As the two WAN interfaces have the same gateway, it means that they are in the same subnet. So if the gateway device or something else inside the ISP's network fails, both recursive routes which use that gateway fail regardless via which physical interface they go. So from this perspective, there is no point in having one of them as a backup for the other one. So I would bond the two physical interfaces together, to have a backup at LAN level, and if you need to use both IP addresses, attach both to the bond interface. The only obstacle here might be if you receive both addresses using DHCP.
It's not about that. For failover i have a different ISP (additional 3rd interface)
Eth1-Backup-ISP2
Eth2-Company1-ISP1
Eth3-Company2-ISP1
I use this configuration because one organization include two small companies and each has its own connection to the ISP with different tariffs and bandwidth.
The problem is that if i use the gateway like [1.1.1.1%eth2] the recursion does not work (route is unreachable). Either here i need to do something differently, or use a netwatch.
The manual says that next-hop resolution does not work with interface names. So it seems that rather than ignoring the interface name and routing to the gateway anyway, they've decided not to route on ip%interface recursively at all. So if you need to physically route each company's traffic via its own cable because the traffic is measured on ISP's switch ports rather than by IP or MAC address, netwatch seems to be your only option.
Re: Recursive route with %interface
Posted: Thu Mar 08, 2018 4:04 pm
by tippenring
Re: Recursive route with %interface
Posted: Thu Dec 15, 2022 1:04 pm
by axdr
Has anyone found a solution?
If possible without using VRF
And how can it be done with netwatch in detail?