Routing ailases to gateways working in 2.0.x, stopped working in 2.1.x
-
Is it just me or did routing change in 2.1.x?
I manually copied my working rules from my older 2.0.3 router to 2.1.3 and they don't work anymore.
The senario below worked fine on 2.0.3, but not on 2.1.x…
Here is the scenario:
2 ISP's: DSL (16Mbit) & CABLE (100Mbit)CABLE = WAN01
DSL = WAN02I made two gateway groups that each monitor gateway heath and fail over to the other if one fails.
USE_WAN01_FIRST = favors WAN01 first & fails over to WAN02 if there are problems.
USE_WAN02_FIRST = favors WAN02 first & fails over to WAN01 if there are problems.Now, I wanted all the streaming media devices and other slower, lesser critical devices in the building to use the DSL connection as their primary connection (WAN02). The remainder of the PCs, etc. should use WAN01 as their primary.
To make things simple and easy to administer, I grouped the hosts i wanted to dire4ct traffic for into ALIASES.
Now, the firewall rules are simple.The alias "STREAMING_MEDIA_DEVICES" was told to use the Gateway Group "USE_WAN02_FIRST"
I let everything else default to the "USE_WAN01_FIRST" gateway.
I placed the rule for "STREAMING_MEDIA_DEVICES", above the other rules on the network that they resided on.
On 2.0.3, this worked fine.
Now on the 2.1.3 installation, these devices send ALL traffic to the gateway - INCLUDING packets destined for INTERNAL ADDRESSES!
What did i do wrong?
Or, maybe something has changed in 2.1.3 FW rule parsing? -
Anyone want to tackle this questions?
It's maddening and preventing my ability to balance my WAN usage.