Problem reproduction:
1. Change connection type from "Automatic configuration - DHCP" to "Static IP"
2. Page submits form (apply.cgi)
3. "Save" and "Apply Settings" buttons now do nothing
This happens even if I fill data in all the form fields (e.g. IP, Subnet, Gateway, DNS 1,2,3)
Maybe this is a javascript validation problem?
Any ideas?
Can I modify the static ip settings in a file? Where is the configuration stored?
Configuration:
- openvpn enabled
- ssh enabled
- wifi enabled
otherwise no changes to default settings
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Sat Apr 20, 2013 20:41 Post subject:
Hopefully you are performing 30-30-30 before and after flashing? try with clearing your browser cache and cookies. I use static IP on my config and it works fine, albeit this is on a buffalo wzr-hp-ag300h. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
I'm having the same issue... When I set a static WAN IP address I the "Apply Settings" button does not work. When setting to DHCP works fine. Does this in Chrome and IE. Haven't tried firefox yet.
1. set to Static IP
2. change IP settings
3. in Chrome, right-click on the apply button and click "Inspect element"
4. Change the entire onclick statement with the one I posted
5. Click on the apply button and it should now skip the validation and save the settings directly.
(Make sure your changes are valid because there is no validation)
Posted: Sat May 11, 2013 21:12 Post subject: root of the problem
I have the same issue with build 21286 on a Netgear 3700wndr.
According to the Chrome javascript console, the variable l2tp_dhcp is not defined. Once this causes the error, the function to_apply, which is defined in the same file, will not run because the whole script has been invalidated. It seems as though older browsers (IE8 in compatability mode) are more forgiving when they encounter a javascript error.
Just posting this as a quick note here so I don't forget when I comment on the bug formally.
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Sun May 19, 2013 13:10 Post subject: Re: root of the problem
DasFox wrote:
buddee wrote:
ccnp123 wrote:
Just posting this as a quick note here so I don't forget when I comment on the bug formally.
Being that the issue is fixed and will be covered in the next build release, why would you comment on it at all? It would be a fairly moot point now..
This is a problem on all dd-wrt firmware?
Thanks...
Not all builds, just 21286. Devs are saying 'expect a new build soon' which could be anytime, but right now they are busy porting new hardware (RT-AC66U, R6300, WNDR4500) and merging new 3.x kernel for broadcom. So for the time being, i would either roll back to a different build, and/or wait for the next beta. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ