Jump to content
Axelrod360

XR500 WiFi disconnect issues

Recommended Posts

I just don't want to miss the return window if this is going to continue being a problem with this router. If it never gets fixed, I'd want to replace it for a different model. I know it's hard to say, but how long until a fix would be available and how likely is it to even happen?

Share this post


Link to post
Share on other sites

That's really hard to say, we'd first need to see if we could even reproduce the issue, then identify what causes it, then fix it. Then finishing the rest of the firmware build and testing. It's just too hard to say unfortunately. One thing I would suggest you try is setup guest WiFi and see if they can connect to that.

Share this post


Link to post
Share on other sites

I replaced my router at the store in hopes it was a hardware specific problem. Unfortunately this one has the same exact issues as the other. Once again toggling IPv6 from off to on and then back to off seems to help fix it temporarily which is weird. I also tried changing the LAN DHCP range to make sure it wasn't conflicting with something but didn't help anything.

I also found out that .32 has a problem setting up QoS priority traffic which I was trying to use but since .32 is the most stable, I can't upgrade to grab the fix.

I really wanted to use DumaOS but I'm thinking I'm going to return this router since it's failing to do basic things that routers are expected to.

Share this post


Link to post
Share on other sites

I have seen some people talk about having similar problems when behind the same modem as I am. It's AT&T's BGW210. Does that give any new ideas? Maybe I'll try getting a 3rd party modem.

Edit:

Tomorrow I'll try seeing if my devices can connect to my router if I don't plug my router into my modem. Then it will be completely isolated

Share this post


Link to post
Share on other sites

Really sorry to hear that. It could be to do with the modem if both routers have the issue as not everyone has this issue which rules out a widespread firmware issue. If you could double check with another modem that would be really helpful. That's a good idea just keep in mind they won't have internet but will be able to access the interface via the LAN IP. Let us know how you get on!

Share this post


Link to post
Share on other sites

OMG! It is the modem. After reflashing and resetting my router many times, I found that if the router starts and lets devices connect before I plug it into the modem, the internet works for all the devices that connected before I made the connection. If I turn the router on while it's already connected to the modem, that's when I get random devices failing to connect. How can this be? It's a modem and the devices shouldn't care what's beyond the router. I found this problem happening in both versions .40 and .56. I'll contact AT&T and see if they can give me any advice or replace the modem.

Share this post


Link to post
Share on other sites

Fantastic to hear that, well done finding that out. I'm not sure why exactly that would be, sometimes the order of things can be particular for no real reason.

Share this post


Link to post
Share on other sites

Well I've talked to AT&T support 3 times, got a support specialist sent to my place, and they all end up saying it's out of their control. I've even tried using an older AT&T modem but that didn't help no matter what settings I used. Is there anything else I can do to help you guys figure out what might be causing the problem? The old AT&T modem didn't even show up as a double NAT using trace route so I'm not sure what's happening. It's still weird that .32 worked but not anything later. Anything that changed in the firmware for how the DHCP server worked?

Share this post


Link to post
Share on other sites

Are you able to replace the AT&T modem with your own modem at all? That could potentially help the issue. Perhaps get one that you could take back to the store but try it to check. Not that I'm aware of. You could try giving all devices a reserved IP on the router and then disable the DHCP server.

Share this post


Link to post
Share on other sites

No, AT&T has some special authentication stuff built into the firmware from what I have read that prevents it from being replaced by a 3rd party modem.

Share this post


Link to post
Share on other sites

Yeah, I have it in IP passthrough and on the other modem they sent me, I used the DMZ+ which should be the same thing. My XR500 gets a public IP so it seems like it should be working.

I'm wondering if it's something to do with UPnP since most of the devices having a hard time are smart devices that might try using it. Either that or some IPv4 vs IPv6 problems. Like when I enable the AT&T modem to use IPv6 on LAN, the XR500 detects it as a IPv6 DHCP connection but when I disable it on AT&T, it shows as 6to4 tunneling on the XR500. I'm not sure if either of those are potentially the problem but just ideas.

Share this post


Link to post
Share on other sites

They have their own LAN IP's.

Looking through the logs when I first boot it, there are some entrees I'm not sure are normal. Can you take a look at these?

[DumaOS] DHCP lease change.

[DumaOS] Marking device that is marked 192.168.1.13 4 11.

[DoS Attack: ACK Scan] from source: ...

Share this post


Link to post
Share on other sites

A couple more notes while I had time to play around with the router, no devices are requesting UPnP so I don't think that's the problem. As for port forwarding, I can access my router's remote management through the external IP the AT&T modem gives it so that seems fine from the modem standpoint.

Share this post


Link to post
Share on other sites

They all seem fine, nothing unusual there. I think for now keep on .32 as I think we've exhausted the suggestions on this firmware, lets hope the next firmware will resolve the issues.

Share this post


Link to post
Share on other sites

I got it to work using my R7000 in AP mode and using the AT&T gateway's DHCP. Not sure if that info helps with my other problem but it's still interesting.

Slight recap/summary: The problem with the XR500 in router mode is whenever it is connected to the gateway (even when the gateway is in complete IP passthrough and the XR500 gets a public IP) is my devices have a hard time getting local IP's from the XR500. They shouldn't even be able to see the gateway's DHCP server, should they? I couldn't get it to work even when turning off my gateway's DHCP server and setting my XR500 to a static IP).

Share this post


Link to post
Share on other sites

No, I forgot what problems I was specifically having but I remember devices getting dropped off WiFi 5GHz band for some reason. It worked better when I downgraded firmware on that router too. Although now I'm running the R7000 with the latest firmware and it's working fine in AP mode so doesn't seem like it would have actually a wireless problem that I was experiencing at first.

Another quick summary: I've tried 2 different Netgear routers and even tried the XR500 with 2 different AT&T gateways all of which had problems. Both routers work on older firmware. I can't pin down exactly which device the problem is coming in from. When I'm having the problem, everything from simple smart light switches to my Windows 10 wireless card to my Samsung phone and many other devices have problems so it isn't like a certain device is having a hard time connecting.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...