Have googled, and done all I can think
NIC works fine with F17-boot disc in rescue mode. cat5 cables have been changed and work on other nodes. Box normally gets it's reserved-ip from Dovado router. Jumbo frames disabled on everything
# ifconfig eth0 up # ifconfig eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500 ether 00:22:3f:f1:f2:d8 txqueuelen 1000 (Ethernet) RX packets 21 bytes 2853 (2.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6 bytes 468 (468.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 12 bytes 840 (840.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12 bytes 840 (840.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
# cat ifcfg-eth0 # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. DEVICE=eth0 BOOTPROTO=dhcp TYPE=Ethernet HWADDR=00:22:3f:f1:f2:d8 DHCP_HOSTNAME=mybox ONBOOT=yes IPV4_FAILURE_FATAL=yes NM_CONTROLLED=no USERCTL=yes PEERDNS=yes IPV6INIT=no NETWORKING_IPV6=no
On 03/20/2013 12:07 PM, Frank Murphy wrote:
NIC works fine with F17-boot disc in rescue mode. cat5 cables have been changed and work on other nodes. Box normally gets it's reserved-ip from Dovado router. Jumbo frames disabled on everything
If the IP is reserved, why not just set it to a static IP and be done with it? I don't know if it would help in this case, but it might simplify things. And, while I'm thinking about it, are there other machines set up the same way? If so, and they work, it's not the router.
On Wed, 20 Mar 2013 12:18:50 -0700 Joe Zeff joe@zeff.us wrote:
If the IP is reserved, why not just set it to a static IP and be done with it? I don't know if it would help in this case, but it might simplify things. And, while I'm thinking about it, are there other machines set up the same way? If so, and they work, it's not the router.
I find it easier for me, just to change things in the router. it was dhcleint-script in the end. My brain getting old.
On 03/20/2013 12:07 PM, Frank Murphy issued this missive:
Have googled, and done all I can think
NIC works fine with F17-boot disc in rescue mode. cat5 cables have been changed and work on other nodes. Box normally gets it's reserved-ip from Dovado router. Jumbo frames disabled on everything
# ifconfig eth0 up # ifconfig eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500 ether 00:22:3f:f1:f2:d8 txqueuelen 1000 (Ethernet) RX packets 21 bytes 2853 (2.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6 bytes 468 (468.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 12 bytes 840 (840.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12 bytes 840 (840.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
# cat ifcfg-eth0 # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. DEVICE=eth0 BOOTPROTO=dhcp TYPE=Ethernet HWADDR=00:22:3f:f1:f2:d8 DHCP_HOSTNAME=mybox ONBOOT=yes IPV4_FAILURE_FATAL=yes NM_CONTROLLED=no USERCTL=yes PEERDNS=yes IPV6INIT=no NETWORKING_IPV6=no
"ifconfig eth0 up" does NOT invoke the DHCP client software needed to get an IP from your DHCP server. The old "ifup eth0" should do it, or run the dhclient app yourself (as root).
# ifconfig eth0 up # dhclient eth0
---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - You possess a mind not merely twisted, but actually sprained. - ----------------------------------------------------------------------
On Wed, 20 Mar 2013 15:00:30 -0700 Rick Stevens ricks@alldigital.com wrote:
"ifconfig eth0 up" does NOT invoke the DHCP client software needed to get an IP from your DHCP server. The old "ifup eth0" should do it, or run the dhclient app yourself (as root).
# ifconfig eth0 up # dhclient eth0
Thanks Rick, Put me on the right track, it was dhclient-script got lost. re-install fixed it.
On 03/20/2013 11:35 PM, Frank Murphy issued this missive:
On Wed, 20 Mar 2013 15:00:30 -0700 Rick Stevens ricks@alldigital.com wrote:
"ifconfig eth0 up" does NOT invoke the DHCP client software needed to get an IP from your DHCP server. The old "ifup eth0" should do it, or run the dhclient app yourself (as root).
# ifconfig eth0 up # dhclient eth0
Thanks Rick, Put me on the right track, it was dhclient-script got lost. re-install fixed it.
Glad to help, Frank. Happy you got it fixed. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Polygon: A dead parrot (With apologies to John Cleese) - ----------------------------------------------------------------------
-
Frank Murphy -
Joe Zeff -
Rick Stevens