Reply

New Firmware v2.3.2.120 (XR500)

Alittlegrumpy
Aspirant

Re: New Firmware v2.3.2.120 (XR500)

I also recently upgraded to beta 3.0 and am now getting frequent internet drops. What are the steps to downgrade?
Message 401 of 412
Netduma-Fraser
NetDuma Partner

Re: New Firmware v2.3.2.120 (XR500)

@ivanrei I believe the Content Blocking only applies to HTTP which of course isn't as helpful unfortunately as most sites now use HTTPS.

@Alittlegrumpy did you do a factory reset after the upgrade?
Message 402 of 412
Alittlegrumpy
Aspirant

Re: New Firmware v2.3.2.120 (XR500)

Yes, I did a factory reset after updating. It's been a couple weeks.
Message 403 of 412
Alittlegrumpy
Aspirant

Re: New Firmware v2.3.2.120 (XR500)

Yes I did a factory reset after updating. It's been a couple weeks
Message 404 of 412
Netduma-Fraser
NetDuma Partner

Re: New Firmware v2.3.2.120 (XR500)

What is the model of the modem/router the XR is connected to? Are ALL devices disconnecting at the time?
Message 405 of 412
Alittlegrumpy
Aspirant

Re: New Firmware v2.3.2.120 (XR500)

Coda 4582. It was perfectly fine until the update. Yes, all devices disconnect
Message 406 of 412
Netduma-Fraser
NetDuma Partner

Re: New Firmware v2.3.2.120 (XR500)

Is the XR in the DMZ of the Coda? Are all devices connected to the XR? Can you set a static IP on the Coda for the XR please and see if it is more stable?
Message 407 of 412
brandoff7
Star

Re: New Firmware v2.3.2.120 (XR500)

Just had an internet drop on .120 Beta on XR500.

 

It wasn't a full internet drop but the XR500 refused to pass any DNS queries.

 

Could ping out to the internet 1.1.1.1, 8.8.8.8, Carrier DNS & Gateway but no DNS traffic was passing for approx 5 minutes. nslookups failed for 4 servers: 1.1.1.1, 8.8.8.8, 202.142.142.142 & 202.142.142.242.

XR500 was accessible & functional during this. I did not reboot the device, functionality restored on it's own.

 

Packet capture was not running but I've uploaded the Debug Log to OneDrive and I've sent a private message to Tim Cheng with the zip of logs.

Model: XR500|Nighthawk Pro Gaming Router
Message 408 of 412
brandoff7
Star

Re: New Firmware v2.3.2.120 (XR500)

Ok, DNS drop just happened again within 40 minutes of last episode. Have rebooted the XR500 now to fix issues and I Was able to capture some LAN & WAN PCAP's. Uploading to OneDrive & Sending to Tim.

 

Here's what was happening...showing Layer 3 to the internet was up but DNS was being stopped. You'll see DNS is not looking up and DNS lookup is failing.

 

C:\Users\Brandon>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data
Reply from 1.1.1.1: bytes=32 time=10ms TTL=59

Ping statistics for 1.1.1.1:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 10ms, Average = 10ms
Control-C
^C
C:\Users\Brandon>ping google.com
Ping request could not find host google.com. Please check the name and try again.

C:\Users\Brandon>nslookup
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: 1.1.1.1

 

Hopefully reboot stabilises things today.

Model: XR500|Nighthawk Pro Gaming Router
Message 409 of 412
Netduma-Fraser
NetDuma Partner

Re: New Firmware v2.3.2.120 (XR500)

Thank you for passing it on to Tim, hopefully NG are close to resolving this fully now.
Message 410 of 412
Philippe2021
Aspirant

Re: New Firmware v2.3.2.120 (XR500)

Hello,

 

It would be good to fix the following issue which is not fixed in the 120 version: two LOCAL computers whatever they are cannot get connected by ssh if one of them is connected by wifi to the router. Everything works fine if the two computers are connected to the router by an ethernet cable. It seems that the wifi blocks ssh and therefore the port 22. There is no reason for that.

 

Please fix this issue, thanks.

 

Message 411 of 412
Netduma-Fraser
NetDuma Partner

Re: New Firmware v2.3.2.120 (XR500)

It's not just specific to SSH, it occurs as well if they just trying to connect to each other regardless. The team are aware so will see what is going on.
Message 412 of 412
Announcements