cancel
Showing results for 
Search instead for 
Did you mean: 

Frequent reconnects to DHCP server

nozzer
Hero
Posts: 3,298
Thanks: 676
Fixes: 3
Registered: ‎04-08-2009

Frequent reconnects to DHCP server

Anyone any idea what's causing this? The DSL had been up for 130 days (working perfectly) until this morning  when it resynced of its own accord, and ever since then it's been a pig to link a laptop to the router. I'm getting the entries below in the system log all day... frequent reconnects every few seconds...  which just make the laptop hang. It's fine when connected with a LAN cable. Does this look like radio interference of some kind causing the wireless link to drop out?
 Mar 30 17:34:09  user  syslog: web: ::ffff:192.168.1.110 logout
 Mar 30 17:40:40  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.110
 Mar 30 17:40:43  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.110
 Mar 30 17:42:09  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.110
 Mar 30 17:42:12  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.110
 Mar 30 17:44:03  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.110
 Mar 30 17:44:06  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.110
 Mar 30 17:44:40  user  syslog: web: ::ffff:192.168.1.110 login

Edit:  sorted! My fault!  Roll_eyes
2 REPLIES 2
adamwalker
Plusnet Help Team
Plusnet Help Team
Posts: 16,871
Thanks: 882
Fixes: 221
Registered: ‎27-04-2007

Re: Frequent reconnects to DHCP server

What was the issue and what fixed it out of interest?
Adam
If this post resolved your issue please click the 'This fixed my problem' button
 Adam Walker
 Plusnet Help Team
nozzer
Hero
Posts: 3,298
Thanks: 676
Fixes: 3
Registered: ‎04-08-2009

Re: Frequent reconnects to DHCP server

I had recently changed to using wireless "n" protocol and for reasons I'm not sure about, either my laptop's wifi card, or the router's wireless transmission, has developed a dislike for 802.11n. Something is causing the signal to be corrupted. I did a scan using Pingplotter which showed a lot of packet loss, even between the router and the laptop, and this kept fooling the router to think the laptop had logged out.
The cure was to revert to 802.11g, which seems to be totally clean. Having said that, I've just tried "n" it again and it seems ok. Might be a radio ham lurking!