Network Card going down after running dhclient

[Mukund Deshpande]

Hi All,

[root at Marvell1 dhcp-4.2.3]# /usr/sbin/dhclient -4 -d -sf
/sbin/dhclient-script eth1
Internet Systems Consortium DHCP Client 4.2.3
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/00:1b:21:52:ad:69
Sending on   LPF/eth1/00:1b:21:52:ad:69
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPOFFER from 7.7.7.11
DHCPACK from 7.7.7.11
bound to 7.7.7.12 -- renewal in 35300 seconds.
receive_packet failed on eth1: Network is down


I am facing this problem from a few days, tried on a few machines.

kernel version is 2.6.27.21

After this getting port up is not possible . Only solution is reboot.



Checked dmesg (/var/log/messages also)

eth0: no IPv6 routers present
ADDRCONF(NETDEV_UP): eth1: link is not ready
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
scp used greatest stack depth: 5336 bytes left
e100: eth1: e100_watchdog: link down
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
NFSD: starting 90-second grace period
e100: eth1: e100_watchdog: link down
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
ADDRCONF(NETDEV_UP): eth1: link is not ready
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present



[root at Marvell1 mukund]# ping 7.7.7.12
connect: Invalid argument
[root at Marvell1 mukund]# ping 7.7.7.12
connect: Invalid argument
[root at Marvell1 mukund]# ping 7.7.7.12
connect: Invalid argument

What could be the issue? Can any one suggest me what could the problem be ?
This happens only after dhclient is run on the interface.


-- 
Regards,
Mukund
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120504/2559f6bb/attachment.html>