Thanks for doing the tests, it sheds some light on the bug. Could you please PM me the backup file from when it wasn't connecting and a backup from now that is is connecting. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Joined: 24 Aug 2009 Posts: 2070 Location: South Florida
Posted: Sun Aug 28, 2011 13:20 Post subject:
For the PPPoE users, and if it hasn't been mentioned already, the nvram variable wan_iface may be causing the issues. I don't understand why, but in OTRW (and on several rc_firewall scripts), it must be get_wanface, which does not show up anywhere in the nvram variables...
None of the outputs in this thread indicate this, and is perhaps just one of the problems plaguing PPPoE/A users:
...Just a thought. _________________ Optware, the Right Way
Asus RT-AC68U
Asus RT-N66U
Asus RT-N10
Asus RT-N12
Asus RT-N16 x5
Asus WL520gU
Engenious ECB350
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
SonicWall NSA220W
SonicWall TZ215W
SonicWall TZ205W
SonicWall TZ105W
For the PPPoE users, and if it hasn't been mentioned already, the nvram variable wan_iface may be causing the issues. I don't understand why, but in OTRW (and on several rc_firewall scripts), it must be get_wanface, which does not show up anywhere in the nvram variables...
Compare:
nvram get wan_iface #wan_iface is an nvram variable
get_wanface #get_wanface is a command
I haven't received any backup files yet. They will tell what nvram variables are actually being changed instead of playing the guessing game. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Thanks guys for getting back. Sorry for delay.
You ask me for the whole files? Have you ever had a look at the file you have in use? You wouldn't do that.
Just tell me how to generate a useful DIFF from both nvrambak.bin files or which tool you use to analyse and compare them and about the parts that are of interest.
Notepad++ doesn't seem to be the best choice. Is there a better way to get the structure?
Thanks guys for getting back. Sorry for delay.
You ask me for the whole files? Have you ever had a look at the file you have in use? You wouldn't do that.
Just tell me how to generate a useful DIFF from both nvrambak.bin files or which tool you use to analyse and compare them and about the parts that are of interest.
Notepad++ doesn't seem to be the best choice. Is there a better way to get the structure?
I was going to semi-manually find/replace all the binary characters and then use an automatic sorter to get text that can be diff'd but that was going to be a pita anyways... If you're going to generate a diff yourself then it would be easier to load up each backup, telnet/ssh to the router and set your terminal client to log, and then run nvram show | sort to get pretty output that can easily be diff'd from your terminal client's logs. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I'm having problems with a WRT610N v1 and VLAN GUI.
From what I've read so far it should be fixed after the build posted here, but no matter what is changed new_vlan#ports doesn't change, is this to be expected?