Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 5 subscribers
  • Views 21503 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

JohnSmith4

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!



This thread was automatically locked due to age.
Parents
  • 0
    BAlfson,

    I agree with what you said about incoming traffic but thats not what I am trying to achieve. Sometimes the other side require static IP here to be allowed in = server has to go out through specific connection.

    Point is that main connection (fibre, very vast) does not have static IP, I use dyndns but this is not enough often for certain things. Some services will let me connect to if my traffic comes from known IP address only. Therefore I have second connection with static IP but slow.

    In masq I have all masked to WAN1 (Internal -> WAN1) as this is main connection. Is this correct in my case?
Reply
  • 0
    BAlfson,

    I agree with what you said about incoming traffic but thats not what I am trying to achieve. Sometimes the other side require static IP here to be allowed in = server has to go out through specific connection.

    Point is that main connection (fibre, very vast) does not have static IP, I use dyndns but this is not enough often for certain things. Some services will let me connect to if my traffic comes from known IP address only. Therefore I have second connection with static IP but slow.

    In masq I have all masked to WAN1 (Internal -> WAN1) as this is main connection. Is this correct in my case?
Children
No Data
Unfiltered HTML