Router causing LAN drop - Log included

[xInDiGo]

I recently bought an N66U when my Linksys WRT54GS went out. Everything seems fine but I noticed a few issues. Clients connected via LAN would sometimes drop connection. In windows 7 you can see the bottom right network monitor will get a red X across it indicating it’s not plugged in. Similarly my PS3 will lose connection via LAN. My network only has cat 5 cables, not 5e or 6, so this may be an issue, but i'd rather not rerun my cables through the house if its not the issue. Anyways, heres the log, and I hope somebody can help me make sense of this.

Mar 3 11:25:58 dnsmasq-dhcp[539]: DHCPREQUEST(br0) 192.168.1.245 6c:62:6d:ef:84:ab
Mar 3 11:25:58 dnsmasq-dhcp[539]: DHCPACK(br0) 192.168.1.245 6c:62:6d:ef:84:ab InDiGo-PC

Thanks!

 

[joegreat]

Mar 3 11:25:58 dnsmasq-dhcp[539]: DHCPREQUEST(br0) 192.168.1.245 6c:62:6d:ef:84:ab
Mar 3 11:25:58 dnsmasq-dhcp[539]: DHCPACK(br0) 192.168.1.245 6c:62:6d:ef:84:ab InDiGo-PC

Hi,

I have checked my syslog.log and there I also found a long list of this entries, but this is not a problem in my case.

Looks like this kind of entries are normal and your case (was it not already discussed here?) has a different reason.

With kind regards
Joe

 

[xInDiGo]

Thanks Joe for the response.

The issue was looked at but no information was given regarding the log. I'm trying to avoid rerunning network cables through the house (major pain in the rear!) & if this is a simple setting I can toggle then I'd love to save me the trouble.

On another note, I'd love to know what is actually happening when the router produces these logs. What packets are being sent/received?

 

[joegreat]

On another note, I'd love to know what is actually happening when the router produces these logs. What packets are being sent/received?

I think this DHCP messages are the RESULT of your network problems: When a client looses the connection, it will request a new IP address (via DHCP) when the connection is coming back.

As already stated in the other thread: Check you cabeling.
The simple way is to by a long, long, long cable and connect one or two of your devices with this cable and see if this helps for the specific devices.
I did the same somet time age, before I ordered a professional to replace the cables in the wall.

With kind regards
Joe

 

[xInDiGo]

I think this DHCP messages are the RESULT of your network problems: When a client looses the connection, it will request a new IP address (via DHCP) when the connection is coming back.

Makes sense! I guess i'll have to pick up a really long cable to see if this will solve my issues! thanks for the help!

 

[Mistermoonlight]

Makes sure that your cable support gigabit connection if your lan client is connecting at gigabit speed to your router.

Cat-5 cable is ok, but cat-5e or cat-6 could give maybe a more reliable gigabit connection in some situations. If your wall cables are cat-5 and your client can be configured to force 100mbits connection type, do it. If your connection is now reliable, you have your answer. In that case, you may try a different better long cable that the one you are actually using.

N.B. For example you can configure your NIC driver on windows for many cards to a specified connection speed (both side of the cable must support it )