NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
eric_bor
Dec 06, 2022Tutor
Interesting problem connecting to routerlogin.net
Hi, I have a RAX54 and I'm able to get it setup and configured but I run into a weird problem where I can no longer access the routerlogin.net page after I've completed the setup and make a few upda...
eric_bor
Dec 07, 2022Tutor
The ONT is verizon i211ml. What would happen is my family would kill me since I have everything already configured for 10.x and things would not be working for some time. 馃槄 I guess I could try that but I previously had R7800, R7450 and R7000 with no problems.
eric_bor
Dec 07, 2022Tutor
I should also mention that the USB shared drive still works ok.
- eric_borDec 07, 2022Tutor
Also, I'm not sure if anyone wants to get into the weeds but in Wireshark, I see the initial GET:
GET / HTTP/1.1
Host: 10.0.0.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Upgrade-Insecure-Requests: 1
A bunch of re-transmits and then a final connection reset flag set in the response back from the router.
Flags: 0x004 (RST)
000. .... .... = Reserved: Not set
...0 .... .... = Accurate ECN: Not set
.... 0... .... = Congestion Window Reduced: Not set
.... .0.. .... = ECN-Echo: Not set
.... ..0. .... = Urgent: Not set
.... ...0 .... = Acknowledgment: Not set
.... .... 0... = Push: Not set
.... .... .1.. = Reset: Set
.... .... ..0. = Syn: Not set
.... .... ...0 = Fin: Not set
[TCP Flags: 路路路路路路路路路R路路][Some of the message was filtered by the forum for containing HTML]
- eric_borDec 07, 2022Tutor
Follow-up: I had a chance to try it with 192.168.1.1 and that has the same issue. I'm also getting the dup ack in Wireshark there too.
- plemansDec 07, 2022Guru - Experienced User
When you reset it (to access it and change lan) , did you test after each change at what point the gui became in-accessible?