voinageo wrote:
So can we have a better explanation what is the command doing ? How it fixes the issue ? From what I can see it is adding some default routes to the routing tables of the interfaces that are part of the load balancing. Am I right ?
Well I'm still trying to figure out what changed between v1.8.5 and v1.9.0. The most obvious change is l2tp kernel mode, but at least removing the kernel modules didn't change things.
As for what that script does is to add all the connected routes to the individual WAN routing tables. By default the load-balance feature creates new routing tables for each WAN. Currently that routing table only contains the default gateway for that WAN. So when your LAN is trying to talk to a l2tp session if it tries to use the new routing table it will send the traffic out the WAN. That's why add rules to the modify ruleset to do things like "if it's LAN to LAN use the main routing table instead".
