Bug 1243

Summary:	dhclient and dhcpd complain about bad udp checksums with virtio and vhost-net
Product:	Mageia	Reporter:	Frederik Himpe <fhimpe>
Component:	RPM Packages	Assignee:	Guillaume Rousse <guillomovitch>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cjw, pterjan, thierry.vignaud
Version:	1	Keywords:	PATCH
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	dhcp-3.2.1-0.P1.2mga1	CVE:
Status comment:

Description Frederik Himpe 2011-05-11 13:18:30 CEST

During a network installation of current Mageia Cauldron, the network works perfectly fine. However, after booting the installed system, both isc dhclient and dhcpcd fail to acquire an IP address from the DHCP server and complain of invalid UDP packets:

dhcpd: eth0: invalid UDP packet from 192.168.122.1

dhclient: 5 bad udp checksums in 5 packets.

The host is Debian testing with kernel 2.6.39-rc6 and qemu-kvm 0.14. The virtual machine is set to use virtio for the NIC and vhost-net is enabled.

The problem does not happen when using e1000 NIC in qemu-kvm.

The iptables work-around mentioned on http://www.mail-archive.com/kvm@vger.kernel.org/msg41958.html also makes the network work. Debian guests work fine with virtio and vhost-net too.

Ahmad Samir 2011-05-11 19:31:11 CEST

CC: (none) => cjw, pterjan, thierry.vignaud

Comment 1 Frederik Himpe 2011-09-12 11:52:06 CEST

So, can the RH patch from dhcp be applied to fix this problem please?

http://pkgs.fedoraproject.org/gitweb/?p=dhcp.git;a=blob;f=dhcp-4.2.2-xen-checksum.patch;h=038d346d726e131f1ab2579fe015a72b49733a0d;hb=HEAD

Manuel Hiebel 2011-09-12 12:21:55 CEST

Keywords: (none) => PATCH
Version: Cauldron => 1

Remco Rijnders 2011-09-12 13:09:12 CEST

Assignee: bugsquad => guillomovitch

Comment 2 Guillaume Rousse 2011-09-12 13:55:48 CEST

I just submitted a new dhcp package with this patch, along with 2 others imported from fedora.

Comment 3 Guillaume Rousse 2011-09-26 11:16:09 CEST

So, does the new release change anything ?

Comment 4 Frederik Himpe 2011-09-27 15:07:41 CEST

Yes, it's working now. Thanks!

Status: NEW => RESOLVED
Resolution: (none) => FIXED