Well now what?

[JaimeZX]

Just moved.

Set up my 3200 at the new place. Worked for a couple of minutes. I wanted to login to the GUI and realized my laptop was connected to a Guest network so I hooked up a CAT6 to one of the LAN ports.

"Connected, no internet."

That's weird. I realized my phone (which had automatically connected) no longer had internet either. The router lights looked normal.

I reboot the router.

No change. I try multiple different cables. The router isn't issuing DHCP anymore, even when I connect back on wifi.

So... symptoms: All lights appear normal. Broadcasting SSID and allowing connections, but not providing any switching/routing. I can't SSH in for obvious reasons.

Anyway. I've got a backup Linksys connected right now that I'm using, but I WANT MY MERLIN/SKYNET/DIVERSION!

Any suggestions? Next step to try would be a factory reset I guess, unless y'all have some other ideas.

 

[QuikSilver]

Just moved.

Set up my 3200 at the new place. Worked for a couple of minutes. I wanted to login to the GUI and realized my laptop was connected to a Guest network so I hooked up a CAT6 to one of the LAN ports.

"Connected, no internet."

That's weird. I realized my phone (which had automatically connected) no longer had internet either. The router lights looked normal.

I reboot the router.

No change. I try multiple different cables. The router isn't issuing DHCP anymore, even when I connect back on wifi.

So... symptoms: All lights appear normal. Broadcasting SSID and allowing connections, but not providing any switching/routing. I can't SSH in for obvious reasons.

Anyway. I've got a backup Linksys connected right now that I'm using, but I WANT MY MERLIN/SKYNET/DIVERSION!

Any suggestions? Next step to try would be a factory reset I guess, unless y'all have some other ideas.

It may be faster to start over than it would be to keep troubleshooting it to narrow down the issue. Would drive me crazy not knowing especially if I could have prevented it but sometimes you have to know when to throw in the towel and get it working again.

 

[MaziahBebop]

Set up my 3200 at the new place. Worked for a couple of minutes.

Sounds fried (hardware fault), I hope not though. Could have been something about the move, or power surge at the new place. Get that factory reset started I think is your best remaining option.

 

[dosborne]

Sounds fried (hardware fault)

I wouldn't jump to that conclusion right away. Lots of software settings and issues that need to be checked first.

A full reset and manual reconfigure would be the best place to start.

 

[JaimeZX]

Well. Update.

Did a full M&M Reset.

Wireless is working fine, or appears to be, but it still refuses to connect to anything wired. Very strange. You think it's a hardware issue?

 

[L&LD]

Try following all the suggestions in the link below. I hope it helps. If not, it would seem to point to a hardware issue.

ax88 packet loss

Hi, I recently upgraded to the ax88 router and have been having connectivity issues (laggy, jittery connections). i checked, and see anywhere from 20% to 50% packet loss, when measured with ping 8.8.8.8 or 1.1.1.1 from multiple clients. this happens if client is connected to router via wifi...

www.snbforums.com

 

[Jeffrey Young]

Just curious, have you tried setting your client device to a static IP address/gateway and plugged into the router to see if you can look around the network (ping the router or see if the adapter comes up)?

 

[dosborne]

Wireless is working fine, or appears to be, but it still refuses to connect to anything wired.

I don't understand what you mean by this.

 

[JaimeZX]

Try following all the suggestions in the link below. I hope it helps. If not, it would seem to point to a hardware issue.

ax88 packet loss

Hi, I recently upgraded to the ax88 router and have been having connectivity issues (laggy, jittery connections). i checked, and see anywhere from 20% to 50% packet loss, when measured with ping 8.8.8.8 or 1.1.1.1 from multiple clients. this happens if client is connected to router via wifi...

www.snbforums.com

Will do! THX

Just curious, have you tried setting your client device to a static IP address/gateway and plugged into the router to see if you can look around the network (ping the router or see if the adapter comes up)?

Not following you 100%, but you mean setting (for example) my laptop to a static 192.168.1.10? Nope. I guess it's worth a shot.

I don't understand what you mean by this.

I mean if WAN is connected to the 3200, it shows "Online," and I can connect wirelessly to the router's SSID and access the intarwebs via wifi. If I plug a LAN cable between a computer and the 3200, the port light on the 3200 comes on and flashes normally, but the router software doesn't seem to recognize this connection. The client device does not show up under "Devices" in Network Map, and the client device is not given any connection information via DHCP. It would be sort of interesting to try and run wireshark on this process to see if there are any ARP packets flowing... but I really just want my intarwebs back.
[Edit: On reflection, I should say it USUALLY doesn't work for wired devices, because I did the initial setup after the M&M Reset via one of my laptops obviously. But once I unplugged the cable the first time it wouldn't re-recognize that laptop, and it wouldn't recognize anything else I connected. Multiple cables across multiple test devices.]

If the router is broken I will file a claim with the movers. My UPS and tower computer are both dead so I dunno what the conditions inside that truck were... no physical damage. Haven't even tried to hook up this printer yet. Now I'm thinking I should.... My 6-month old monitor is working okay though, fortunately. *knock on wood*

 

[JaimeZX]

OK - followed all of L&LD's steps. (Maybe?) slight progress. The 3200 will assign LAN/DHCP to things plugged in when it boots. Anything plugged in to a LAN port after boot does nothing. As before, the port light on the router comes on, but there is no network connection and the router log does absolutely nothing with plug/unplug. (Edit: "Maybe" because I didn't actually test this function yesterday.)

Wifi connections continue to work normally and watching the log during a wifi connection shows the expected DISCOVER/OFFER/REQUEST/ACK traffic.

So. My options seem to be: 1. Deal with it as-is. 2. Pull out my spare 3100 and see if I can get it to work better than this 3200.
I will probably go with option 2 this evening after work, pending any further suggestions.

//BREAK BREAK//

Went to Speedtest.net out of curiosity. I am paying for 100mbps service. DL speed: 94mbps. UL speed: 835mpbs. LOOOOOL didn't expect that!

 

[JaimeZX]

WELL.
THIS IS JUST TOO BIZARRE.

One thing I didn't mention because it I thought it might be a symptom of weird signal from the router... my Ethernet IP kept showing up as 192.168.1.137.

So I grabbed the Asus Firmware Restoration/Rescue program in a last-ditch attempt to fix this thing. Part of the configuration for a firmware rescue is setting a local static IP as 192.168.1.10. I go into the Windows Adapter settings to execute this and it's set to a static IP of 192.168.1.137!!!

TOO BIZARRE. I would never have done this, it makes no sense.

Only thing I can think of is I sent this laptop back for service a couple of months ago, they may have set a Fixed IP for some reason... and I may just not have used Ethernet since then? Too, too weird.

 

[MaziahBebop]

WELL.
THIS IS JUST TOO BIZARRE.

One thing I didn't mention because it I thought it might be a symptom of weird signal from the router... my Ethernet IP kept showing up as 192.168.1.137.

So I grabbed the Asus Firmware Restoration/Rescue program in a last-ditch attempt to fix this thing. Part of the configuration for a firmware rescue is setting a local static IP as 192.168.1.10. I go into the Windows Adapter settings to execute this and it's set to a static IP of 192.168.1.137!!!

TOO BIZARRE. I would never have done this, it makes no sense.

Only thing I can think of is I sent this laptop back for service a couple of months ago, they may have set a Fixed IP for some reason... and I may just not have used Ethernet since then? Too, too weird.

Hmmm, this is looking like real progress. My apology for jumping in too quick earlier when I said your router could be fried; I didn't stop to think about the laptop as the cause of your problems. Can you remove that static IP option on the laptop and see if DHCP kicks in? Also can you test things from another client other than the laptop?

 

[JaimeZX]

No, sorry I didn't explain myself well enough. Yes, I set the laptop back to "automatic" and the router immediately issued an appropriate IP. So... as far as I'm concerned everything is (seems to be) fixed at this point. So, so weird. Still absolutely baffled as to how a weird static IP got into the settings.