Bug 76570 – After booting install-amd64-universal-2004.3-r1 CD i can't bring eth0 to work

• Product: Gentoo Release Media
• Status: RESOLVED NEEDINFO

[Description Karl Treiber 2005-01-03 15:44:48 UTC]

I have a new AMD64 3400 with a Gigabyte GA-K8NS Pro motherboard
After booting the CD (install-amd64-universal-2004.3-r1) no network card 
is detected  automatically. Beside the onboard 10/100/1000 NIC i have added
2 intel EtherExpress Pro 10/100B. 
I do a modprobe e100 to load NIC module. with dmesg i can see both nic's are loaded correctly ( different base addresses and INT's are assigned) and the 2 
MAC addresses are listed.  
After that i assign a IP address to eth0 with 
ifconfig eth0 10.21.6.77 netmask 255.255.0.0 broadcast 10.21.255.255
So far so good. 
A ping to a device in the same subnet returns -> destination host unreachable
A sniffer trace shows that eth0 is sending an ARP request and receives the 
correct ARP response, but it looks like eth0 is not listening to the responses 
instead it repeates the ARP request again and again. 

This is also the case with the onboard NIC which requires to load 
the sk98lin module for the Marvell Yukon chips.
  


Reproducible: Always
Steps to Reproduce:
1. Boot from install CD install-amd64-universal-2004.3-r1
2. modprobe e100
3. ifconfig eth0 
4. ping a device 
Actual Results:  
ping returns destination host unreachable

Expected Results:  
normal positive ping results

[Comment 1 Mike Doty (RETIRED) 2005-01-04 06:36:19 UTC]

chage this line to:
ifconfig eth0 10.21.6.77 netmask 255.255.0.0 broadcast 10.21.255.255 up

[Comment 2 Karl Treiber 2005-01-05 15:24:33 UTC]

Hi,   
I tried your hint to add the "up" option in the ifconfig, but i still can't
ping 10.21.1.77 (which is definitly up and running).  The response is still 
destination host unreachable.

By the way the "up" and "down" in the ifconfig reacts as expected. 

If i do the ifconfig line without the "up", a second ifconfig to show the 
status of eth0 and lo0 shows the  status up.  I belive it must be up otherwise the NIC card would't sent out the arp request for 10.21.1.77  

[Comment 3 Simon Stelling (RETIRED) 2005-03-28 03:07:08 UTC]

is this still an issue with 2005.0?

[Comment 4 Alex Howells (RETIRED) 2005-03-28 08:46:14 UTC]

This sounds a lot like a user problem (routing issue), rather than a bug. It has been open for several months, we've moved into a new release now (2005.0) so I'm going to close this bug with status 'NEEDINFO'. Should the user wish to reopen and update us with the current situation, that's fine :o)