search

ypy705 / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

Can't connect to router web interface when connected to modem #650

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Upgrade to 3.0.3.1-027 FW. Reset to default settings.
2. Connect router to cable modem.
3. Try to go to 192.168.1.1 in web browser. Page either partially loads after a 
long time, or not at all (connection times out most of the time).
4. Disconnect modem. Power cycle router.
5. Go to 192.168.1.1. Router interface comes up immediately.

What is the expected output? What do you see instead?
See above

What version of the product are you using? On what operating system?
3.0.3.1-027 router FW
Windows XP machine Firefox or IE browser
Cisco 2100 cable modem (from time warner)

Other observations:
1. Internet connection is working - I can browse the internet no problem, it's 
just the router config I can't get to.
2. I saw similar issue reported earlier that was resolved by disabling firewall 
logs, but firewall logs have never been turned on in my case.
3. I tried disabling the firewall entirely, to no effect.
4. I used Wireshark to record logs in the working (no modem) and not working 
(modem) cases. I would attach them except I see a "Issue attachment storage 
quota exceeded." message on the issue submission page. I don't know enough to 
be able to identify any issues, but just looking at differences I do see that 
in the working case the first packet starts with "msr-plugin-port > http [SYN]" 
whereas in the failing case the first packet is "lisp-data > http [SYN]". I 
have no idea if that's relevant at all.

Original issue reported on code.google.com by RobDWil...@gmail.com on 20 Dec 2012 at 9:21

GoogleCodeExporter commented 9 years ago 
More observations from the logs:
The initial GET of the html appears to work in each case (despite the lisp-data 
vs msr-plugin-port discrepancy), but immediately afterwards the two logs 
diverge: when the modem is connected the browser sends several packets that are 
never responded to, but when the modem is disconnected the packets are 
responded to. Again, the source port is different in each case:

WORKING CASE:
     52 7.993302000    192.168.1.1           192.168.1.175         HTTP     167    HTTP/1.0 200 Ok  (text/html)
     53 7.993313000    192.168.1.175         192.168.1.1           TCP      66     msr-plugin-port > http [ACK] Seq=417 Ack=33381 Win=260760 Len=0 TSval=6123620 TSecr=4294917249
     54 7.993893000    192.168.1.175         192.168.1.1           TCP      66     msr-plugin-port > http [FIN, ACK] Seq=417 Ack=33381 Win=260760 Len=0 TSval=6123620 TSecr=4294917249
     55 7.994113000    192.168.1.1           192.168.1.175         TCP      66     http > msr-plugin-port [ACK] Seq=33381 Ack=418 Win=15552 Len=0 TSval=4294917249 TSecr=6123620
     56 7.998483000    192.168.1.175         192.168.1.1           TCP      78     dyn-site > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     57 7.998820000    192.168.1.1           192.168.1.175         TCP      74     http > dyn-site [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=4294917250 TSecr=0 WS=2
     58 7.998835000    192.168.1.175         192.168.1.1           TCP      66     dyn-site > http [ACK] Seq=1 Ack=1 Win=262144 Len=0 TSval=6123620 TSecr=4294917250
     59 7.999791000    AsustekC_3d:35:d6     Spanning-tree-(for-bridges)_00 STP      60     Conf. Root = 32768/0/10:bf:48:3d:35:d6  Cost = 0  Port = 0x8001
     60 7.999890000    192.168.1.175         192.168.1.1           TCP      78     plbserve-port > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     61 8.000210000    192.168.1.1           192.168.1.175         TCP      74     http > plbserve-port [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=4294917251 TSecr=0 WS=2
     62 8.000228000    192.168.1.175         192.168.1.1           TCP      66     plbserve-port > http [ACK] Seq=1 Ack=1 Win=262144 Len=0 TSval=6123620 TSecr=4294917251
     63 8.002118000    192.168.1.175         192.168.1.1           TCP      78     sunfm-port > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     64 8.002345000    192.168.1.1           192.168.1.175         TCP      74     http > sunfm-port [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=4294917251 TSecr=0 WS=2
     65 8.002361000    192.168.1.175         192.168.1.1           TCP      66     sunfm-port > http [ACK] Seq=1 Ack=1 Win=262144 Len=0 TSval=6123620 TSecr=4294917251
     66 8.018490000    192.168.1.175         192.168.1.1           HTTP     460    GET /state.js HTTP/1.1 
     67 8.018716000    192.168.1.175         192.168.1.1           HTTP     460    GET /popup.js HTTP/1.1 

FAILING CASE:
     62 21.410539000   192.168.1.1           192.168.1.175         HTTP     1187   HTTP/1.0 200 Ok  (text/html)
     63 21.410660000   192.168.1.175         192.168.1.1           TCP      66     lisp-data > http [ACK] Seq=417 Ack=33407 Win=261016 Len=0 TSval=6119169 TSecr=17853
     64 21.411445000   192.168.1.175         192.168.1.1           TCP      66     lisp-data > http [FIN, ACK] Seq=417 Ack=33407 Win=261016 Len=0 TSval=6119169 TSecr=17853
     65 21.411671000   192.168.1.1           192.168.1.175         TCP      66     http > lisp-data [ACK] Seq=33407 Ack=418 Win=15552 Len=0 TSval=17854 TSecr=6119169
     66 21.428130000   192.168.1.175         192.168.1.1           TCP      78     lisp-cons > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     67 21.430378000   192.168.1.175         192.168.1.1           TCP      78     unicall > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     68 21.431590000   192.168.1.175         192.168.1.1           TCP      78     vinainstall > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     69 21.432505000   192.168.1.175         192.168.1.1           TCP      78     m4-network-as > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     70 21.433897000   192.168.1.175         192.168.1.1           TCP      78     elanlm > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     71 21.435168000   192.168.1.175         192.168.1.1           TCP      78     lansurveyor > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     72 21.669458000   192.168.1.175         192.168.1.1           TCP      78     itose > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     73 21.670589000   192.168.1.175         192.168.1.1           TCP      78     fsportmap > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     74 21.671391000   192.168.1.175         192.168.1.1           TCP      78     net-device > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     75 21.672172000   192.168.1.175         192.168.1.1           TCP      78     plcy-net-svcs > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     76 21.673041000   192.168.1.175         192.168.1.1           TCP      78     pjlink > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1
     77 21.684282000   192.168.1.175         192.168.1.1           TCP      78     f5-iquery > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=0 TSecr=0 SACK_PERM=1

Original comment by RobDWil...@gmail.com on 20 Dec 2012 at 10:01

GoogleCodeExporter commented 9 years ago 
After more investigation it seems like the source port is a red herring... it 
appears to change randomly each time I re-test, both with the modem connected 
and disconnected. The only thing the log shows is that the router stops 
responding after the first full html page is returned - which isn't much help.

I tried looking at the router logs for the two cases but there's no difference 
- it looks like the logs only show the router initialization and nothing that's 
going on during actual use.

I decided to just configure it with the modem disconnected and then plug the 
modem in afterwards. I did that, but as soon as I switched from a wired to 
wireless connection I lost the WAN connection entirely. So now I switched back 
to the ASUS FW build 3.0.0.4.260

Original comment by RobDWil...@gmail.com on 21 Dec 2012 at 1:18

GoogleCodeExporter commented 9 years ago 
I'm also facing the same issue and i had to switch to ASUS FW build 3.0.0.4.260.
Missing the ssh and transmission features since a month..

Devs please help..

Original comment by jagdish....@gmail.com on 22 Dec 2012 at 3:26

GoogleCodeExporter commented 9 years ago 
I have a similar problem, no SSH, No transmission
Even if I create the transmission in home/root directory myself it will still 
not work!!

But then when creates and stat Filezilla it does not show that I created such a 
directory even though a can go to it "cd transmision" 

I have no clue what I am doing wrong

Original comment by arendo...@gmail.com on 27 Dec 2012 at 1:37

GoogleCodeExporter commented 9 years ago 
I have a similar problem, no SSH, No transmission
Even if I create the transmission in home/root directory myself it will still 
not work!!

But then when creates and stat Filezilla it does not show that I created such a 
directory even though a can go to it "cd transmission" 

I have no clue what I am doing wrong

Original comment by arendo...@gmail.com on 27 Dec 2012 at 1:37

GoogleCodeExporter commented 9 years ago 
I tried FW version 3.0.2.6-018 since I was having other problems with the ASUS 
FW but the result is the same: no or very slow response from the Web GUI when 
connected to WAN.

Original comment by RobDWil...@gmail.com on 3 Jan 2013 at 9:15

GoogleCodeExporter commented 9 years ago 
I have the same issue. 

Windows XP hard wired to router, when I try to go to configuration page it 
times out. It does the same thing on an XP machine connected via 2.4G. 

No other issues with internet access. All other OS'es (Apple, Android, etc.) 
seem to work just fine, so I wind up configuring the router on my phone.

It appears it may be something to do with the interaction of the router and the 
Windows XP IP stack, but that's just a guess.

Original comment by kamw...@gmail.com on 3 Apr 2013 at 2:38

GoogleCodeExporter commented 9 years ago 
Forgot to mention I'm running RT-N56U_3.0.3.4-048_full.zip

Original comment by kamw...@gmail.com on 3 Apr 2013 at 2:41

GoogleCodeExporter commented 9 years ago 
I have the exact same issue too. And I'm running the latest version of the FW 
at the time (3.0.3.4-048) as well.

Original comment by varuncva...@gmail.com on 9 Apr 2013 at 8:09

GoogleCodeExporter commented 9 years ago 
I also have the same problem.
Windows XP hard wired to router, when I try to go to configuration page it 
times out. 

No other issues with internet access. All other OS'es (Apple, Android, etc.) 
seem to work just fine.

I'm running RT-N56U_3.0.3.4-048_full.zip

Original comment by willngks...@gmail.com on 4 Feb 2014 at 6:31