Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Networking
User Name
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.


  Search this Thread
Old 10-04-2016, 10:37 PM   #1
LQ Newbie
Registered: Jul 2016
Posts: 5

Rep: Reputation: Disabled
bad udp checksums VMware

Hello guys a have a problem which i never faced until now.

I have a VMware ESXi 4.0 running as a Captive Portal solution for a hotel but since this morning users are reporting that they cannot connect anymore on wifi network. I have checked syslog and found this strange message:

2016 Oct 5 05:35:14 controller dhcpd: DHCPREQUEST for from f4:5c:89:09:ea:c5 (KitchenardsiPad) via
2016 Oct 5 05:35:14 controller dhcpd: DHCPACK on to f4:5c:89:09:ea:c5 (KitchenardsiPad) via
2016 Oct 5 05:35:14 controller dhcpd: 4 bad udp checksums in 6 packets

After every DHCPACK is bad udp checksums.

Please tell me what infos should I give you for help.

Best regards.

Last edited by Gruchaa333; 10-04-2016 at 10:45 PM.
Old 10-05-2016, 05:55 PM   #2
Registered: Mar 2008
Posts: 21,895

Rep: Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616Reputation: 3616
UDP is bad by design. It is connectionless. However that is not the checksum issue and may or may not be related to this connection issue. Let's start with checksum.
One site suggests this. "The simplest workaround is to change the virtual NIC type from virtio to Intel e1000 in KVM. Apparently this driver calculates checksums. But virtio is the default driver type." The virtual nic usually has a setting to offload the checksum and by most apps, the checksum will fail when the work is offloaded. Wireshark will reveal this also.

Try that first. I get the feeling however that you have other issues with how a device is allowed to connect. May be something like no more leases for some reason. May be that you need to use wireshark to see why the handshake is stopping or where it failed then act on that.

The real question is we have to ask that I assume this did work at one time. Then some change happened. Can we discover the change? What all could have changed? Could it be some update? Some failure of the software? Some hardware fail(not likely)? Or is it possible that some attack or data failure caused this?

Last edited by jefro; 10-05-2016 at 05:57 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
UDP: Short Packets: and UDP bad checksum: entries in dmesg minutes2memories Linux - Networking 2 02-26-2006 08:28 PM
Bad Checksums In Rkhunter sovietpower Linux - Security 3 09-07-2004 08:11 PM
Ignoring bad checksums (!) antares Linux - Software 2 08-21-2004 06:33 AM
Redhat 8.x, how to ignore bad checksums (!) antares Red Hat 1 08-21-2004 06:16 AM
RKHUNTER: Bad MD5 Checksums Scarpa Linux - Security 2 06-18-2004 06:56 AM > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 01:16 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration