Re: Version 1.4.2
Posted: Thu Sep 22, 2011 8:02 am
problem with settings lost after reboot still present on D-Link DIR-300 

A forum to discuss the Gargoyle web interface for Openwrt
https://www.gargoyle-router.com/phpbb/
I had this problems on my 1043ND..with 1.4.1 - 1.4.2asayler wrote:I'm experiencing this issue with 1.4.2 on my WR1043ND v1.8 (purchased new in August). I updated from 1.3.16 using the system upgrade file and reloaded all my settings manually (not via the Restore function).Markuz Nightwind wrote:I've got serious problems with 1.4.x on TL-WR1043ND with wifi. Seems like the router cuts out my main computer (wifi connected) each like 20 minutes...
About every 20 minutes I lose wireless connectivity to the router. Wired seems to be unaffected (or else the act of switching my computer from wireless to wired fixes the issue). Generally I must reboot the router to fix the issue. When the wireless goes down, I lose connectivity to both the router and the Internet.
This is very similar to the issue I had on 1.4.0 (http://www.gargoyle-router.com/phpbb/vi ... t=20#p7323). I did not test 1.4.1.
For those with "working" WR1043NDs under 1.4.x, are you connecting via wireless or wired? What version of the hardware do you have (maybe an issue on newer post v1.7 models)? Can you run a continuous ping test to both the router and the Internet via a wireless connection and have it work for >30 minutes?
I've reverted to 1.3.16 which seems (mostly) stable.
Except for thsi issue, everything seems to be working fine (static WAN IP, static DHCP assignments, QOS, 40 mHz wireless, WPA, B,G,N).
Keep up the good work! Unfortunately I did not have time to do a thorough set of tests on this issue as I couldn't afford the downtime this morning. If needed, I can do more testing later to help isolate this issue. Let me know what would be helpful.
Cheers,
Andy
Router is a good old ASUS WL-500GP v1 - for browser, I use the Fox 7 beta, but it is the same with Internet Explorer 9 as well.asayler wrote:The web interface seemed to be working fine for me on a WR1043ND using Chrome (although there are other issues, see my previous post). This includes the "Applying Settings" window, which seems to disappear as it should after a few seconds and the settings get saved.Lrdx wrote:I have noticed that the "Please Wait While Settings Are Applied" text when I press apply sometimes gets stuck.
What router and browser are you using?
I'd like to use UPnP for my NAS Storage, PS3, and Skype. For debugging UPnP there's some free software which is capable of opening Ports on an UPnP Router.DoesItMatter wrote:Anything else?Lrdx wrote:Skype, MSN, torrent clients..DoesItMatter wrote:what else would use UPnP
so I could try helping with testing the issue?
I have Skype, MSN, and Bittorent running with no issues and
do not have UPnP enabled - so not a good test for my setup.
As far as the web page refresh - I suspect its your cache settings.
Try emptying any page history/cache from your browser and
going back into the Gargoyle GUI.
I tried the upgrade to 1.4.2 again and cleared the memory via the above method. Unfortunately, it did not fix my problem and I'm still experiencing the wireless issues. I ran some more testing and my results are below:shastar wrote:
I had this problems on my 1043ND..with 1.4.1 - 1.4.2
That you have to do is erase rootfs_data. and everthing should works great.
How to do this is boot into failsafe mode:
Power up your router. When the 'SYS' light starts to blink, press and hold the 'QSS' button in the front-right until the blinking gets faster. Now open a telnet session to 192.168.1.1. No user name or password required.
Type this:
mtd -r erase rootfs_data
Its gona reboot automatic. Done, now, do not restore old backup. Just type in your settings manually.
I have two v1.8 and they are working fine with 1.4.2.asayler wrote:...
Can anyone else with a 1043-ND confirm this? Does the issue occur on all 1043NDs, or just the later versions (1.7+)?
Which log did you check?hnl_dk wrote: If I where you, I would check the log. I have also had trouble with my router. It did reboot itself and looking at the log I discovered that the router was constantly complaining about my AP.