Blocked network

Hi,

I've cloned a linux PC today (Redhat 9) and the network is refusing to
work.

The process was as follows:

1) clone PC,
2) Started Pc, eth0 failed to start 'Determining Ip infomation...
Failed'
3) Switched on Kudzu.
4) Reboot
5) Kudzu resolved various motherboard changes. With the NICs I dumped
the original NIC config and transferred the network setup to the new
NIC (The NIC's were the same but in different slots).
6) The eth0 still failed.
7) Changed to static ip, reboot.
8) I can ping localhost, it's self but nothing else. I cannot ping it
from another PC.

Ifconfig shows up nothing unexpected. We did have an unknown route in
the routing table but removing this didnot help, all the other routes
look normal. It's as if there is some kind of closed firewall
(ipchains is off).

Has anyone any ideas, my feeling is there is only a small change to be
made an all will work.

Best regards

Ian

(E-Mail Removed) (Ian Young) writes:

]Hi,

]I've cloned a linux PC today (Redhat 9) and the network is refusing to
]work.

]The process was as follows:

]1) clone PC,
]2) Started Pc, eth0 failed to start 'Determining Ip infomation...
]Failed'

Check to see if the ethernet is started up. Ie, look in
dmesg|less
to see if the ethernet card is started up (eg you may have a different
etehrnet card on this system, and need to load a different module to run
it)


]3) Switched on Kudzu.
]4) Reboot
]5) Kudzu resolved various motherboard changes. With the NICs I dumped
]the original NIC config and transferred the network setup to the new
]NIC (The NIC's were the same but in different slots).
]6) The eth0 still failed.

does eth0 fail or does dhcp? ifconfig -a
does it report that eth0 exists?

If not then you need to solve that problem first. If yes, then it is a
dhcp problem. Who or what is your dhcp host.

Is your network plugged into your computer?

]7) Changed to static ip, reboot.
]8) I can ping localhost, it's self but nothing else. I cannot ping it
]from another PC.

]Ifconfig shows up nothing unexpected. We did have an unknown route in
]the routing table but removing this didnot help, all the other routes
]look normal. It's as if there is some kind of closed firewall
](ipchains is off).

]Has anyone any ideas, my feeling is there is only a small change to be
]made an all will work.

]Best regards

]Ian

Bill,

Thanks for your reply.

> (E-Mail Removed) (Ian Young) writes:
>
> ]Hi,
>
> ]I've cloned a linux PC today (Redhat 9) and the network is refusing to
> ]work.
>
> ]The process was as follows:
>
> ]1) clone PC,
> ]2) Started Pc, eth0 failed to start 'Determining Ip infomation...
> ]Failed'
>
> Check to see if the ethernet is started up. Ie, look in
> dmesg|less

I've added the relavent sections (I hope) of dmesg below. I cannot see
anything to indicate that the NIC didnot start.

**************** Start of dmesg ******************
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket

......

NET4: Frame Diverter 0.46

.....

NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 32768 buckets, 256Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

.....

ip_tables: (C) 2000-2002 Netfilter core team
8139too Fast Ethernet driver 0.9.26
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 Fast Ethernet at 0xf896d000, 00:e0:4d:07:cc:33,
IRQ 16
eth0: Identified 8139 chip type 'RTL-8139B'
ip_tables: (C) 2000-2002 Netfilter core team
eth0: Setting 100mbps full-duplex based on auto-negotiated partner
ability 45e1.

.....

/dev/vmmon: Module vmmon: registered with major=10 minor=165
/dev/vmmon: Module vmmon: initialized
/dev/vmnet: open called by PID 3318 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
bridge-eth0: up
bridge-eth0: attached
/dev/vmnet: open called by PID 3341 (vmnet-netifup)
/dev/vmnet: hub 8 does not exist, allocating memory.
/dev/vmnet: port on hub 8 successfully opened
divert: allocating divert_blk for vmnet8
/dev/vmnet: open called by PID 3340 (vmnet-netifup)
/dev/vmnet: hub 1 does not exist, allocating memory.
/dev/vmnet: port on hub 1 successfully opened
divert: allocating divert_blk for vmnet1
/dev/vmnet: open called by PID 3377 (vmnet-natd)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 3379 (vmnet-dhcpd)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 3378 (vmnet-dhcpd)
/dev/vmnet: port on hub 1 successfully opened
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner
ability 45e1.
**************** Start of dmesg ******************

> to see if the ethernet card is started up (eg you may have a different
> etehrnet card on this system, and need to load a different module to run
> it)
>
>
> ]3) Switched on Kudzu.
> ]4) Reboot
> ]5) Kudzu resolved various motherboard changes. With the NICs I dumped
> ]the original NIC config and transferred the network setup to the new
> ]NIC (The NIC's were the same but in different slots).
> ]6) The eth0 still failed.
>
> does eth0 fail or does dhcp? ifconfig -a
> does it report that eth0 exists?

Ifconfig -a does show eth0.

>
> If not then you need to solve that problem first. If yes, then it is a
> dhcp problem. Who or what is your dhcp host.
>
> Is your network plugged into your computer?

Yes, I've also tried differnt NIC (All Realtek 8139 cards) and
plugging the cable into a laptop which successfully booted using DHCP.

>
> ]7) Changed to static ip, reboot.
> ]8) I can ping localhost, it's self but nothing else. I cannot ping it
> ]from another PC.
>
> ]Ifconfig shows up nothing unexpected. We did have an unknown route in
> ]the routing table but removing this didnot help, all the other routes
> ]look normal. It's as if there is some kind of closed firewall
> ](ipchains is off).
>
> ]Has anyone any ideas, my feeling is there is only a small change to be
> ]made an all will work.
>
> ]Best regards
>
> ]Ian

You will have realised this machine is running VMWare. This got me
thinking, I stopped VMWare starting at boot up and rebooted. The NIC
now worked with a fixed IP address. I then changed the NIC to use
DHCP, unfortunately the NIC still failed to work.

At this point I cut my losses, I needed to get the machine back into
service so I rebuilt it. I thought that resolving the VMware issue was
going to get complicated.

If you have any other ideas I might be able to try them next time.

Thanks again for your time.

Best Regards

Ian

Did you assign a static to this interface? If so, can you ping the static
IP? This is different from pinging localhost, as pinging your own ip address
is subject to more or less ipfilters and/or routing. Thereby you can
determine if this is a routing prob, or other.
Pinging 127.0.0.1 has nothing to do with eth0, in fact you can have no nic
installed at all, and still be able to ping localhost, all this proves is
that the ip stack is loading, but it have nothing to do with eth0 in this
case.
From dmesg, it does appear that the nic module is loading, I am thinking
this is more of an ip problem than kernel mods / hardware issue.
How about you post a full output of ifconfig and route -n?
All of this is pointless if dhcp is setup... unless in the process of
reloading the kernel mod for the Realtek, the nic got reset with ip info,
such as dhcp, or the lack thereof.

"Ian Young" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Bill,
>
> Thanks for your reply.
>
> > (E-Mail Removed) (Ian Young) writes:
> >
> > ]Hi,
> >
> > ]I've cloned a linux PC today (Redhat 9) and the network is refusing to
> > ]work.
> >
> > ]The process was as follows:
> >
> > ]1) clone PC,
> > ]2) Started Pc, eth0 failed to start 'Determining Ip infomation...
> > ]Failed'
> >
> > Check to see if the ethernet is started up. Ie, look in
> > dmesg|less
>
> I've added the relavent sections (I hope) of dmesg below. I cannot see
> anything to indicate that the NIC didnot start.
>
> **************** Start of dmesg ******************
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
>
> .....
>
> NET4: Frame Diverter 0.46
>
> ....
>
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 32768 buckets, 256Kbytes
> TCP: Hash tables configured (established 262144 bind 65536)
> Linux IP multicast router 0.06 plus PIM-SM
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>
> ....
>
> ip_tables: (C) 2000-2002 Netfilter core team
> 8139too Fast Ethernet driver 0.9.26
> divert: allocating divert_blk for eth0
> eth0: RealTek RTL8139 Fast Ethernet at 0xf896d000, 00:e0:4d:07:cc:33,
> IRQ 16
> eth0: Identified 8139 chip type 'RTL-8139B'
> ip_tables: (C) 2000-2002 Netfilter core team
> eth0: Setting 100mbps full-duplex based on auto-negotiated partner
> ability 45e1.
>
> ....
>
> /dev/vmmon: Module vmmon: registered with major=10 minor=165
> /dev/vmmon: Module vmmon: initialized
> /dev/vmnet: open called by PID 3318 (vmnet-bridge)
> /dev/vmnet: hub 0 does not exist, allocating memory.
> /dev/vmnet: port on hub 0 successfully opened
> bridge-eth0: up
> bridge-eth0: attached
> /dev/vmnet: open called by PID 3341 (vmnet-netifup)
> /dev/vmnet: hub 8 does not exist, allocating memory.
> /dev/vmnet: port on hub 8 successfully opened
> divert: allocating divert_blk for vmnet8
> /dev/vmnet: open called by PID 3340 (vmnet-netifup)
> /dev/vmnet: hub 1 does not exist, allocating memory.
> /dev/vmnet: port on hub 1 successfully opened
> divert: allocating divert_blk for vmnet1
> /dev/vmnet: open called by PID 3377 (vmnet-natd)
> /dev/vmnet: port on hub 8 successfully opened
> /dev/vmnet: open called by PID 3379 (vmnet-dhcpd)
> /dev/vmnet: port on hub 8 successfully opened
> /dev/vmnet: open called by PID 3378 (vmnet-dhcpd)
> /dev/vmnet: port on hub 1 successfully opened
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Tx queue start entry 4 dirty entry 0.
> eth0: Tx descriptor 0 is 00002000. (queue head)
> eth0: Tx descriptor 1 is 00002000.
> eth0: Tx descriptor 2 is 00002000.
> eth0: Tx descriptor 3 is 00002000.
> eth0: Setting 100mbps full-duplex based on auto-negotiated partner
> ability 45e1.
> **************** Start of dmesg ******************
>
> > to see if the ethernet card is started up (eg you may have a different
> > etehrnet card on this system, and need to load a different module to run
> > it)
> >
> >
> > ]3) Switched on Kudzu.
> > ]4) Reboot
> > ]5) Kudzu resolved various motherboard changes. With the NICs I dumped
> > ]the original NIC config and transferred the network setup to the new
> > ]NIC (The NIC's were the same but in different slots).
> > ]6) The eth0 still failed.
> >
> > does eth0 fail or does dhcp? ifconfig -a
> > does it report that eth0 exists?
>
> Ifconfig -a does show eth0.
>
> >
> > If not then you need to solve that problem first. If yes, then it is a
> > dhcp problem. Who or what is your dhcp host.
> >
> > Is your network plugged into your computer?
>
> Yes, I've also tried differnt NIC (All Realtek 8139 cards) and
> plugging the cable into a laptop which successfully booted using DHCP.
>
> >
> > ]7) Changed to static ip, reboot.
> > ]8) I can ping localhost, it's self but nothing else. I cannot ping it
> > ]from another PC.
> >
> > ]Ifconfig shows up nothing unexpected. We did have an unknown route in
> > ]the routing table but removing this didnot help, all the other routes
> > ]look normal. It's as if there is some kind of closed firewall
> > ](ipchains is off).
> >
> > ]Has anyone any ideas, my feeling is there is only a small change to be
> > ]made an all will work.
> >
> > ]Best regards
> >
> > ]Ian
>
> You will have realised this machine is running VMWare. This got me
> thinking, I stopped VMWare starting at boot up and rebooted. The NIC
> now worked with a fixed IP address. I then changed the NIC to use
> DHCP, unfortunately the NIC still failed to work.
>
> At this point I cut my losses, I needed to get the machine back into
> service so I rebuilt it. I thought that resolving the VMware issue was
> going to get complicated.
>
> If you have any other ideas I might be able to try them next time.
>
> Thanks again for your time.
>
> Best Regards
>
> Ian