Description of problem:
Upon insertion of the cardbus nic, dhclient successfully negotiates an IP
address. Thereafter, it does not recognize any of the responses to the
lease updates and eventually downs the interface when the original lease
tcpdump verifies that the server responses do in fact appear on the wire.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Insert nic. Wait.
The process can be sped up by setting the lease expiry
low on the server side.
Server is dhcp-3.0pl1-23 also running on RH9.
Have you checked if there is firewall rules blocking this?
Yes. Firewalling is disabled.
I belive I'm seeing this too. The client is dhclient-3.0pl1-23 and I'm told the
server is bootp running on an ancient bsdi machine. Our symptom is that
evolution reading mail in a spool on NFS will die periodically, "tail -f" of an
NFS file will die periodically, and "tcpdump -ieth0" will periodically report
that the interface has been marked "down". The times these things happen
correlate with the "expires" lines in the leases file.
Are you seeing anything in the message log for this bug?
On our end, the client logs nothing (aside from the NFS errors), and the bootp
server logs requests every few minutes from each of the redhat9 clients. If
necessary I can gather information on the bootp server, which is of ancient vintage.
I encountered the same bug. dhclient loses the IP and I can't work. DHCP-Server
works with fli4l 2.0.8.
Unreproducible with dhcp-3.0.1-7