.34 Dual WAN not saving settings

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

MrLawliet

Occasional Visitor
Hi Merlin,

I've updated to .34 for the AC66U and I have this setup:

Primary WAN: Static IP
Secondary WAN: LAN1, Automatic IP

The problem is the Secondary WAN is showing the Static IP option selected with blank values of the Primary WAN under Network Map when clicked on, but in WAN settings LAN is set correctly to Automatic IP.

Screenshot of Secondary WAN in Network Map: http://i.imgur.com/LNC4FYS.png

Since it says "Connected" for it I assume it is doing Automatic IP, but I can't test the fallback until later today.

If you can, let me know if this looks cosmetic or may be a bigger issue.
 
I'm not sure because I don't deal with the Dual WAN code, but I suspect that Connected merely indicates that the Ethernet cable is connected. If you are in failover mode, it won't obtain an IP until needed AFAIK.
 
I have DW on 34 and all seem to be OK but I have PPOE not static IP, from your screenshot it looks like is not connecting.
Check the second WAN setting, as is a fallback it my be possible that you have set a value different from 0 on
"Idle Disconnect Time in seconds: Disconnect after time of inactivity (in seconds)"
if so it will not connect until he needs.
I use the balance, it's not perfect ( some lag and disconnection ) but at list give me more speed ;)
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top