Bug 753143 – net-misc/dhcp-4.4.2-r2 from dhcpd 5 bad IP checksums seen in 5 packets

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Andrea Postiglione 2020-11-04 19:14:08 UTC]

I have a dhcp server to test the virtual machine boot via pxe but I don't get any ip

this is the syslog dhcpd
Nov  4 20:05:32 thunderdome dhcpd[11327]: DHCPDISCOVER from 08:00:27:8a:48:da via br0
Nov  4 20:05:33 thunderdome dhcpd[11327]: DHCPOFFER on 192.168.178.149 to 08:00:27:8a:48:da via br0
Nov  4 20:05:46 thunderdome dhcpd[11327]: DHCPDISCOVER from 08:00:27:8a:48:da via br0
Nov  4 20:05:47 thunderdome dhcpd[11327]: DHCPOFFER on 192.168.178.150 to 08:00:27:8a:48:da via br0
Nov  4 20:07:19 thunderdome dhcpd[11327]: DHCPDISCOVER from 08:00:27:8a:48:da via br0
Nov  4 20:07:20 thunderdome dhcpd[11327]: DHCPOFFER on 192.168.178.151 to 08:00:27:8a:48:da via br0


but on the vm the output of dhclient is this!
i also tried from other devices to make dhcp requests but no response



customsrescuecd ~ # dhclient -v eth0
Internet Systems Consortium DHCP Client 4.4.2 Gentoo-r2
Copyright 2004-2020 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/08:00:27:8a:48:da
Sending on   LPF/eth0/08:00:27:8a:48:da
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
5 bad IP checksums seen in 5 packets
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[Comment 1 Andrea Postiglione 2020-11-04 19:40:26 UTC]

this is the conf


ddns-update-style interim;
ignore client-updates;
authoritative;
allow booting;
allow bootp;
allow unknown-clients;




 subnet 192.168.178.0 netmask 255.255.255.0 {
 range 192.168.178.2 192.168.178.250;
 option domain-name-servers 192.168.178.1;
 option domain-name "fritz.box";
 option routers 192.168.178.1;
 option broadcast-address 192.168.178.255; #not important
 default-lease-time 86400;
 max-lease-time 86400;
}

 next-server 192.168.178.250;


 class "pxeclients" {
  match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";

  if option pxe-system-type = 00:00 {
   filename "bios/pxelinux.0";
  } elsif option pxe-system-type = 00:09 {
   filename "efi/syslinux.efi";
  } elsif option pxe-system-type = 00:07 {
   filename "efi/syslinux.efi";
  } elsif option pxe-system-type = 00:06 {
   filename "path/to/EFIia32/syslinux.efi";
  }
 }

[Comment 2 Jonas Stein 2020-11-04 22:49:45 UTC]

The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/