Forcing one host to use secondary WAN connection - cannot make it work for my life.

Hi All,

Hopefully someone could help :)

I have got second WAN connection, which normally sits as standby spare. But i decided to actually use it for some traffic. To test it first I decided to route through it my internet radio (standalone box). And whatever I do (I am on 9.353 home license) it just does not work. Is there known bug in this firmware I beg to ask?

If not than I tried all possible things I could think of / could find on forum. Typically I would set both WANs to active, set first to 100 and second to 0 to force all traffic on default through main WAN. Than I would create multipath rule to get traffic (device -> any -> WAN2) from radio push through WAN2. And it does not happen. WAN2 on dashboard stays 0 / 0 kbps and checking main connection i can see that shoutcast service continues on main WAN. I also set short persistence to see effect faster (1 minute) and also restarted device to force the rule. Nothing.

So i tried that rule on my PC (myPC -> any -> WAN2) and see exactly same behavior. I get main WAN IP address when checked in the browser. WAN2 stays with 0 traffic on it.

I also tried to masquerade (map) that device in question to WAN2 but no difference either. Is this actually needed by the way?

Just to clarify, if i set weights to 50/50 or 100/100 or anything similar than it seems to split the overall traffic between both WANs. But I cannot get just a device to exit through chosen one.

It worries me that when I want to get a server to be visible outside under specific IP (WAN2 IP) I will not be able to make it work?

Please kindly share you experience.

Thanks!