No route through Tunnel Dual Wan

[xchris72]

Hi,
i installed yesterday :384.15_beta1 and configured VPN to NordVpn servers but i'm having problems routing traffic to the tunnel i describe the setup.

2 ISP : 192.168.8.1 /24 192.168.9.1/24

Dual Wan in Load balance (wan2 is on lan1).
Routing rules for all the lan.
192.168.77.16/28 all WAN 2
192.168.77.32/27 all WAN 1
192.168.77.64/26 all WAN 1
192.168.77.128/25 all WAN 1

only client between 192.168.77.1 - 192.168.77.15 have dual wan connection.
All the other on WAN1 or WAN2

Now...
i configured an OpenVpn with ovpn config files (standard)

If i route all traffic through VPN... it doesn't work. VPN connected, but traffic goes through WAN1 or WAN2
If i route specific network segments... it's the same. Traffic is not routed through the tunnel.


Any idea?
Thank you

 

[Martineau]

Hi,
i installed yesterday :384.15_beta1 and configured VPN to NordVpn servers but i'm having problems routing traffic to the tunnel i describe the setup.

2 ISP : 192.168.8.1 /24 192.168.9.1/24

Dual Wan in Load balance (wan2 is on lan1).
Routing rules for all the lan.
192.168.77.16/28 all WAN 2
192.168.77.32/27 all WAN 1
192.168.77.64/26 all WAN 1
192.168.77.128/25 all WAN 1

only client between 192.168.77.1 - 192.168.77.15 have dual wan connection.
All the other on WAN1 or WAN2

Now...
i configured an OpenVpn with ovpn config files (standard)

If i route all traffic through VPN... it doesn't work. VPN connected, but traffic goes through WAN1 or WAN2
If i route specific network segments... it's the same. Traffic is not routed through the tunnel.


Any idea?
Thank you

This should still work - VPN rules not working when Dual-WAN configured

 

[L&LD]

And I would also recommend upgrading to the RMerlin 384.15_0 release too.

 

[xchris72]

I installed the beta just yesterday
( i did the update this morning)


Thank you for the link... i didn't know it was already reported.
Thank you

 

[Martineau]

I installed the beta just yesterday
( i did the update this morning)


Thank you for the link... i didn't know it was already reported.
Thank you

The developer cannot test Dual-WAN, so my script 'hack' facilitates the use of the GUI and addresses the issue

i.e. Basically, the Dual-WAN Selective Routing RDPB rules will always have a higher priority than the VPN Client Selective Routing RPDB rules.

If you issue command

ip rule

then you will see your VPN Client RPDB rules start at RPDB priority rule number '1010x' and the Dual-WAN RPDB rules start @100,200 and 400.

So my hack attempts to ensure that (rather than use priority '1010x') the VPN rules are crammed into the higher priority range 50-100.

You don't have to use my GUI hack, i.e. you could simply move the VPN rules to the more-appropriate priority, when say the openvpn-event 'vpnclientX-route-up' event is triggered ( see openvpn-event)

 

[xchris72]

Ok thank you very much!
I tried this morning but with no luck.. but i had to keep the internet up for all the family so i could not investigate that much...

i.e. Basically, the Dual-WAN Selective Routing RDPB rules will always have a higher priority than the VPN Client Selective Routing RPDB rules.

This is a problem for me, as i have a rule for almost every ip in the lan...

However,
now i know where i have to work on!
Thank you very much


PS: The next step is to route 2 tunnels via different isp to a VPS, and to bond them on both sides.

 

[Martineau]

This is a problem for me, as i have a rule for almost every ip in the lan...

Then clearly you should be using CIDR notion to greatly reduce the number of physical rules by condensing contiguous IP ranges.

 

[xchris72]

Then clearly you should be using CIDR notion to greatly reduce the number of physical rules by condensing contiguous IP ranges.

yes of course..
i mean that every ip is covered, so those Selective Routing RDPB rules have priority!

192.168.77.16/28 all WAN 2
192.168.77.32/27 all WAN 1
192.168.77.64/26 all WAN 1
192.168.77.128/25 all WAN 1

Only ips not "ruled" are first 16.. (because they have to go through load balancing)

Thank you