Feedback: any Dual WAN user?

[venanx]

Screen Shot requested :

 

[tifozi]

Ah!

Try to change Primary WAN to LAN port 2 and Mode to Load Balance. Also you don't have to use Dual WAN to setup LAN port 2 as WAN.

 

[rvandaalen]

D̶u̶a̶l̶ ̶w̶a̶n̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶f̶i̶n̶e̶ ̶f̶o̶r̶ ̶m̶e̶ ̶s̶o̶ ̶f̶a̶r̶. However I was wondering if the following is possible? :

I have a server running plex among other, is it possible to dedicate the secondary wan to only plex / a certain port, I want the rest of my network (laptops/phones etc) and other services on the server(transmission, sabnzb, sickbeard) to use primary wan.

I can only specify ip's not ports?

Because if I add my server ip to use secondary wan, then also the other services will use secondary wan, which I don't want.

Have tested a bit more today, I have 2 big issues with dual one so far:

1- Routing rules for dual WAN is NOT working for me.
2- Cannot use Port Forwarding

I have a server running plex I assign and enable for this server a routing rule to only use for example primary wan. But still get both random WAN ip's when checking and refreshing ip. I setup The rule: all ips - > server ip = primary wan

Plex needs an open port, I can't open any ports. they are not accessible.

Can someone confirm this?

 

[rvandaalen]

Any thoughts? Can someone confirm? does another version work better? I would love not to resort to a pfsense box or other firmware.

 

[saulos]

I don't see how it can be done, the only possible setting is to switch to load balance and set source IP and destination IP on the bottom of the page this "probably" set the traffic from A to B over one of the WAN.
If this fit your need, if not you need a different router more sofisticated.

 

[tifozi]

How about Port Triggering? It might be a possible workaround but it will not achieve the other thing you want which is non-plex clients on the second WAN.

 

[rvandaalen]

How about Port Triggering? It might be a possible workaround but it will not achieve the other thing you want which is non-plex clients on the second WAN.

I tried port triggering, this did not work. But thanks for the suggestion.

But also the rule function does not work in general for me. If I select a rule for a an ip/pc then still that pc gets different primary/secondary wan ip's on refresh or checking with different whats my ip sites for example.

I select source ip = all ips (leave blank) destination is my wired pc ip. also tested with other laptop etc.

 

[saulos]

I tried port triggering, this did not work. But thanks for the suggestion.

But also the rule function does not work in general for me. If I select a rule for a an ip/pc then still that pc gets different primary/secondary wan ip's on refresh or checking with different whats my ip sites for example.

I select source ip = all ips (leave blank) destination is my wired pc ip. also tested with other laptop etc.

"port trigger" is not bind to any WAN it's good only for service like private ftp or website.
I never used that rule function so I don't know if it's a bug or design best man for answer is Merlin

 

[j0ram]

Greetings.

Routing rules was touched on a couple of weeks ago, and I'm wondering if there's been any more discovery with this.

We're going to have an AC68U with a Comcast high speed business line in the WAN, and a T1 in the LAN/Dual port.

We have 13 workstations which I'd like to have use only the WAN/cable, and a VOIP system that I'd like to use only the LAN/T1.

Any luck towards similar situations?

Thanks in advance for any feedback!

 

[bheiser1]

Dual Wan functionality

Hi - based on feedback here earlier this year I stopped trying to use the Dual Wan functionality. However having just upgraded to 3.0.0.4.375.4 (from a July release) I noticed the addition of dual-wan as a core feature. I've given it a try.

My config:
Primary: cable provider, 50mb, WAN port
Secondary: DSL provider, ~2mb, LAN port

I configured "watchdog" on, and reduced the 12 retries to 6. I see in this config, if I pull the plug on the WAN connection, approximately 3 minutes later the failover to the secondary connection occurs. Aside from it taking longer than expected, so far so good.

I noticed if I reinstate the WAN connection (plug it in), it doesn't "fail back". The simplest way seems to be to reboot the router once the wan connection is restored.

So my questions ... if it doesn't auto-detect restoration of the primary link, how would one know it is ready and available for use again? And is there a plan to incorporate auto-detect and fail-back?

Thanks in advance! I'm not complaining about the functionality, just trying to decide whether I need to spend big $$$ to buy a purpose-built dual-wan router...

Thanks for all your work on this!

 

[iotzan]

Currently on RT-N66U_3.0.0.4_374.36_beta1-sdk5.
Configured for Fail Over, the N66U router will not switch back to the primary link. I don't see a way to trigger it other than rebooting the router or toggling the Dual Wan Off/On.
The load balancing is also pretty sketchy. The ratio doesn't seem to always work, it likes to stick to one of the 2 links at random. Also missing are some more advanced routing rules such as UDP traffic on the Secondary WAN, etc.

Thank you very much, Merlin, for taking an interest in this functionality!