Can someone please confirm or rule out my issue with dhclient sending
bad IP checksum packets. It would really suck if 7.1 was released with a
broken DHCP client.
I've had many problems lately, but none involved checksum nor the dhcpd
(btw, I assume that you are seeing bad checksum on the
I will try another em card in that server to confirm/rule out the nic
driver. I am seeing the same checksum number on both the source machine,
the dhcp server machine, and a 3rd windows xp machine sniffing the
traffic with etherreal/wireshark. The windows xp box is running an intel
nic as
Jonathan Feally wrote:
I will try another em card in that server to confirm/rule out the nic
driver. I am seeing the same checksum number on both the source
machine, the dhcp server machine, and a 3rd windows xp machine
sniffing the traffic with etherreal/wireshark. The windows xp box is
OK, so I installed a different PE1750 with BETA2 and then updated the
source via cvsup RELENG_7 from cvsup3 and all is ok now on that box.
Went back the first box and cvsup'ed the src again into an empty
directory and it compiled and worked fine. Looks like my updating of the
source along the
Can someone please confirm or rule out my issue with dhclient sending
bad IP checksum packets. It would really suck if 7.1 was released with a
broken DHCP client.
Jonathan Feally wrote:
Sorry for the cross-post, but this could be either lists problem.
I have 2 boxes running 7-STABLE as of
On Tuesday 02 December 2008 15:57:15 Jonathan Feally wrote:
Can someone please confirm or rule out my issue with dhclient sending
bad IP checksum packets. It would really suck if 7.1 was released with a
broken DHCP client.
I had 7.1-PRE (early Octover) send out DHCP requests without issue,
