FIbre Support

Get expert support with your Fibre connection.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Eth ports, DNS + DHCP dead on router during upstream DNS communication.

Himcules
Popular Poster
Message 7 of 7

I also have the same issue. In debug logs I see often TalkTalk's DNS servers being mentioned.

 

My local DNS and DHCP fails, I reset all my ethernet equipment up to the router, and the router is the issue. Intermittent but more frequent in the evenings. WiFi is usually ok. The router is 40% CPU usage which is quite high compared to usually around 20%. No idea on context switch counts etc. Wish we had extended stats...

75% packet loss or more from router doing local pings during these times from ethernet.

 

"I suspect that the router is waiting for some response from TalkTalk's DNS servers which it isn't getting and this then causes the ethernet ports to freeze, but not the wifi. " Unusual but I agree this is what is happening.

 

I think this is an upstream matter rather than local, but also I heard of some FW update that can be applied, may be worth checking that. 

0 Likes
6 REPLIES 6

Himcules
Popular Poster
Message 1 of 7

It appears to be fixed without any changes my side. 

TT must've sorted out whatever it was. I wonder what is was

0 Likes

Himcules
Popular Poster
Message 2 of 7

After issues most of the day now the situation appears temporarily stable for the moment. @Debbie-TalkTalk are you able to check with anyone internally at TT who may know why this is happening? 

 

I tried Googles DNS but issue remains unchanged and 79.79.79.79 + .80 are still being contacted. Debug log (removed a few details):

 

2021-08-13 18:03:09 [Critical][Debug-Log] static:[dhcpd]xid[] choose [main] address pool
2021-08-13 18:03:11 [Debug][Debug-Log] static:[dhcpd]send Ack, xid[], mac[], request serverip[192.168.1.254], yourip[192.168.1.12], dns1[8.8.8.8], dns2[8.8.4.4]
2021-08-13 18:05:52 [Debug][Debug-Log] static:[dhcpc]receive Ack, wan[wan3], xid[], mac[], request serverip[], clientip[], yourip[], dns1[79.79.79.79], dns2[79.79.79.80]
2021-08-13 18:11:53 [Debug][Debug-Log] static:[dhcpc]receive Ack, wan[wan3], xid[], mac[] request serverip[], clientip[81.170.104.70], yourip[], dns1[79.79.79.79], dns2[79.79.79.80]
2021-08-13 18:15:04 [Error][Debug-Log] static:[dhcpd]request packet has no lease,send nak!
2021-08-13 18:15:08 [Error][Debug-Log] static:[dhcpd]request packet has no lease,send nak!
2021-08-13 18:15:19 [Error][Debug-Log] static:[dhcpd]request packet has no lease,send nak!
2021-08-13 18:15:23 [Debug][Debug-Log] static:[dhcpd]receive Discover, xid[], mac[]
2021-08-13 18:15:23 [Critical][Debug-Log] static:[dhcpd]xid[] choose [main] address pool
2021-08-13 18:15:23 [Critical][Debug-Log] static:[dhcpd]receive arp reply from mac[], ip[]
2021-08-13 18:15:25 [Debug][Debug-Log] static:[dhcpd]send Ack, xid[], mac[], request serverip[192.168.1.254], yourip[192.168.1.97], dns1[8.8.8.8], dns2[8.8.4.4]
2021-08-13 18:17:53 [Debug][Debug-Log] static:[dhcpc]receive Ack, wan[wan3], xid[], mac[], request serverip[], clientip[], yourip[], dns1[79.79.79.79], dns2[79.79.79.80]
2021-08-13 18:23:53 [Debug][Debug-Log] static:[dhcpc]receive Ack, wan[wan3], xid[], mac[], request serverip[], clientip[81.170.104.70], yourip[], dns1[79.79.79.79], dns2[79.79.79.80]
2021-08-13 18:29:53 [Debug][Debug-Log] static:[dhcpc]receive Ack, wan[wan3], xid[], mac[], request serverip[], clientip[], yourip[], dns1[79.79.79.79], dns2[79.79.79.80]

0 Likes

Message 3 of 7

Ok I see. Would any logs I can attach be of help? As I see on the forums this affects other customers the same way.

0 Likes

Message 4 of 7

Hi Himcules

 

All Sagemcom routers will be updated soon. We have to wait for the FW update to be fully rolled out.

 

Thanks

 

Debbie

0 Likes

Himcules
Popular Poster
Message 5 of 7

I use ethernet heavily, so for me this is very much unusable. I wonder what has caused this all of a sudden.

 

No thanks, as I recall we replaced our Huawei WIFI hub with this one because that one had Wifi dropout issues several times within each hour for us. ( As previously mentioned on my old forum post )

 

I have this model :

Device Type:DG8041W
Description:EchoLife DG8041W Home Gateway
  
Hardware Version:I.1.01
Software Version:v1.05t

 

I started going a bit crazy trying to find where to specify the upstream DNS server settings. Appears this was within the DHCP options at the bottom. Can that be changed to have a separate category so it is easier to find within the LAN menu?

 

ping 192.168.1.254 -t

 

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=2920ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1078ms TTL=64
Reply from 192.168.1.254: bytes=32 time=885ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1656ms TTL=64
Reply from 192.168.1.254: bytes=32 time=721ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1345ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1679ms TTL=64
Reply from 192.168.1.254: bytes=32 time=398ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.254: bytes=32 time=559ms TTL=64
Reply from 192.168.1.254: bytes=32 time=139ms TTL=64
Request timed out.

 

Loss varies from 15% - 95%

 

This is pretty bad for a local 1G eth connection. Maybe I can work with someone to diagnose or have FW pushed out a bit early to test with?

0 Likes

Debbie-TalkTalk
Support Team
Message 6 of 7

Hi Himcules

 

Would you like me to send a Huawei WIFI hub for testing to see how the connection compares?

 

We do have new firmware coming soon for the Sagemcom hub and this should be rolled out within the next few weeks.

 

Thanks

 

Debbie

0 Likes