RE: Determining IP information for eth0 failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jeff, all,

Thx for the reply, see text for comments,

Cheers,
Jeroen

> >Hi Jeroen (lol), hi all,
> >
> >Fishy stuff.
> >I have the same issue, similar config
> >Core 1 on a Sony Vaio PCG-C1VE, xircom pcmcia eth adapter (lunix 
> >status: newbie)
> >
> >Tried adding the sujested lines in
> >'/etc/sysconfig/network-scripts/ifcfg-eth0', issue stands
> >  
> >
> What did you add there?
> The adapter is configured by DHCP so minimal information is 
> used in that file.
-----------------------------------------------------
I added (and deleted)
check_link_down() {
return 1;
}
in '/etc/sysconfig/network-scripts/ifcfg-eth0'
-----------------------------------------------------
> 
> >-------------------
> >DHCP: i should get all info, ip, subnet, dns, and gateway.
> >This works. The ip eth0 receives is from the pool gw, dns 
> and subnet are ok.
> >The laptop even shows up in the dhcp client list of the (US robotics 
> >-cheapo, but working)router.
> >In the dhcp client list the hostname shown for the laptop is: "25924 
> >8242:136" (Can i change this?)
> >  
> >
> Change that on the DHCP server end.
-----------------------------------------------------
Ok, thx
-----------------------------------------------------
> 
> >everything is looking great so far
> >When i try to ping my gateway, i get "Destination host unreachable"
> >*I think dhcp packets are sent using UDP, apparently that 
> works, could 
> >it be a problem with icmp or tcp?
> >
> >When i boot the laptop i get an error when it tries to 
> initialize the 
> >network interface.
> >something like "xircom_cb eth0 not present, delaying initialisation"
> >-I use a xircom pcmcia adater as i have no network on board.
> >*During startup pcmcia is initialised after eth0 fails to initialise.
> >
> >  
> >
> I have mentioned this before, and your line above says it.  
> The sequence of starting the services is at fault here.
> Since pcmcia services are not by default started until after 
> the network is started you see this failure.
> If you go into /etc/rcX.d and change the sequence of these 
> services starting the problem with failing to start the 
> network will be fixed.
-----------------------------------------------------
nice,
How do i know which X in rcX.d to change (1 or 4 or 5 or doesnt it matter?)
Do i change sequence just by renaming files:
K90network -> K96network
K96pcmcia -> K90network?
-----------------------------------------------------
> 
> As far as the ping failing, have you verified the eth0 
> adapter is initialized and running.?
> "serivce network restart" as root will handle that usually if 
> not already up.
> 
-----------------------------------------------------
The GUI said it is active... (?) how can i be sure?
'service network restart' fails on bringing up eth0... so i guess thats my
problem
-----------------------------------------------------
> >thats one to chew on, i have been anyhow.
> >
> >Cheers,
> >Jeroen
> >
> >
> >
> >-----Original Message-----
> >From: fedora-list-bounces@xxxxxxxxxx 
> >[mailto:fedora-list-bounces@xxxxxxxxxx]
> >On Behalf Of Sami Maisniemi
> >Sent: Thursday, April 01, 2004 9:57 PM
> >To: For users of Fedora Core releases
> >Subject: Re: Determining IP information for eth0 failed
> >
> >Hi,
> >
> >RH 9.0 and Fedora Core 1 have a similar problem with some 
> network cards. 
> >I found the following solution:
> >
> >Add to the configuration file 
> '/etc/sysconfig/network-scripts/ifcfg-eth0':
> >
> >check_link_down() {
> >return 1;
> >}
> >
> >If you indeed have the same problem, this should work.
> >
> >Regards Sami
> >
> >Jeroen Van Goey wrote:
> >
> >  
> >
> >>Thanks for the support, but it still won't work. So, let's 
> >>recapitulate my
> >>    
> >>
> >settings:
> >  
> >
> >>*Fast Ethernet 10/100M PCI network card
> >>*FC1 Gnome
> >>*module 8139too loaded
> >>*When I try to activate eth0 via redhat-config-network or 
> dhclient, I 
> >>recieve the error "Determining IP information for eth0.... Failed"
> >>
> >>In /etc/hosts I have: 
> >>127.0.0.1             localhost.localdomain        localhost 
> >>
> >>In etc/modules.conf I have: 
> >>alias usb-controller usb-uhci
> >>alias eth0 8139too
> >>
> >>(deleted the "options 8139too io=0xe400 irq=11")
> >>
> >>In $ cat /etc/sysconfig/network-scripts/ifcfg-lo I have: 
> >>DEVICE=lo
> >>IPADDR=127.0.0.1
> >>NETMASK=255.0.0.0
> >>NETWORK=127.0.0.0
> >># If you're having problems with gated making 127.0.0.0/8 a 
> martian, # 
> >>you can change this to something else (255.255.255.255, for example)
> >>BROADCAST=127.255.255.255
> >>ONBOOT=yes
> >>NAME=loopback
> >>
> >>In /etc/sysconfig/networking/devices/ifcfg-eth0 I have: 
> >>USERCTL=yes
> >>PEERDNS=yes
> >>TYPE=Ethernet
> >>DEVICE=eth0
> >>HWADDR=00:40:f4:6f:b4:90
> >>BOOTPROTO=dhcp
> >>
> >>(Information for NETMASK, DOMAIN, IPADDR, DHCP_HOSTNAME, GATEWAY, 
> >>NETWORK and BROADCAST seem to be missing. Should I fill in these 
> >>myself,(and with which values), or should DHCP/something 
> else do this 
> >>for me?)
> >>
> >>The command "ifconfig -a" gives: 
> >>eth0      Link encap:Ethernet  HWaddr 00:40:F4:6F:B4:90 
> >>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
> >>         RX packets:236210 errors:0 dropped:0 overruns:0 frame:0 
> >>         TX packets:845 errors:0 dropped:0 overruns:0 carrier:0 
> >>         collisions:0 txqueuelen:1000 
> >>         RX bytes:14275029 (13.6 Mb)  TX bytes:288990 (282.2 Kb) 
> >>         Interrupt:11 Base address:0x6000
> >>
> >>lo        Link encap:Local Loopback 
> >>         UP LOOPBACK RUNNING  MTU:16436  Metric:1 
> >>         RX packets:5939 errors:0 dropped:0 overruns:0 frame:0 
> >>         TX packets:5939 errors:0 dropped:0 overruns:0 carrier:0 
> >>         collisions:0 txqueuelen:0 
> >>         RX bytes:5271644 (5.0 Mb)  TX bytes:5271644 (5.0 Mb)
> >>
> >>(The IPs for inet addr, Bcast and  Mask are missing)
> >>
> >>I can only ping localhost, every other IP gives "Network 
> unreachable". 
> >>Defining a static IP in the GUI of redhat-config-network doesn't 
> >>change a thing (and my ISP works with dynamic IPs anyway, 
> so I don't 
> >>think I need
> >>    
> >>
> >to define any static IP).
> >  
> >
> >>PING localhost.localdomain (127.0.0.1) 56(84) bytes of data. 
> >>64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=0 ttl=64
> >>    
> >>
> >time=0.140 ms
> >  
> >
> >>         ..... 
> >>64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=5 ttl=64
> >>time=0.132 ms
> >>--- localhost.localdomain ping statistics ---
> >>6 packets transmitted, 6 received, 0% packet loss, time 5012ms rtt 
> >>min/avg/max/mdev = 0.126/0.135/0.140/0.004 ms, pipe 2
> >>
> >>In the GUI-interface for redhat-config-network, I selected 
> >>"automatically obtain IP adress settings with DHCP", so I 
> should get 
> >>my DNS information from there. But even if I do specify the 
> domain of 
> >>my ISP, and a primary and secondary nameserver in 
> /etc/resolv.conf, I 
> >>still
> >>    
> >>
> >get the dreaded "Determining IP information for eth0...
> >  
> >
> >>failed"error when I try to activate  eth0.
> >>
> >>If I start DHCP Client manually (command "dhclient"), I get the
> >>    
> >>
> >(error)message: 
> >  
> >
> >>Listening on LPF/eth0/00:40:f4:6f:b4:90 
> >>Sending on   LPF/eth0/00:40:f4:6f:b4:90 
> >>Listening on LPF/lo/ 
> >>Sending on   LPF/lo/ 
> >>Sending on   Socket/fallback 
> >>DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 3 
> DHCPDISCOVER 
> >>on eth0 to 255.255.255.255 port 67 interval 3  ....
> >>DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 
> >>DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 1 No 
> DHCPOFFERS received.
> >>No working leases in persistent database - sleeping. 
> >>
> >>(looks like no broadcast is received)
> >>
> >>
> >>I'm not sure it's relevant, but when the fibrecable from 
> the ISP comes 
> >>into my house, it goes to a switch> From there one cable goes to a 
> >>Windows PC, and one to an ex-Windows-now-Limux PC (mine, 
> the one with 
> >>troubles)>
> >>
> >>      printer 
> >>     /
> >>pc1 (windows)
> >>  \ 
> >>   \
> >> 
> Switch/hub--------cablemodem-----fibrecable-------myISP-------
> --Internet 
> >>   /
> >>  /
> >>pc2 (Linux)
> >>
> >>I mention this, because I was thinking that I should search the 
> >>solution into masquarading, gateways, etc.
> >>
> >>
> >>The output of "route -n" 
> >>Kernel IP routing table 
> >>Destination     Gateway         Genmask         Flags 
> Metric Ref    Use
> >>    
> >>
> >Iface
> >  
> >
> >>169.254.0.0     0.0.0.0         255.255.0.0     U     0     
>  0        0 lo 
> >>127.0.0.0       0.0.0.0         255.0.0.0       U     0     
>  0        0 lo 
> >>
> >>The output of "iptables -L -n -v" (because I tought it 
> maybe could be 
> >>a firewall related
> >>problem):
> >>Chain INPUT (policy ACCEPT 0 packets, 0 bytes) 
> >>pkts bytes target     prot opt in     out     source
> >>    
> >>
> >destination
> >  
> >
> >>2728  303K RH-Firewall-1-INPUT  all  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) 
> >>pkts bytes target     prot opt in     out     source
> >>    
> >>
> >destination
> >  
> >
> >>  0     0 RH-Firewall-1-INPUT  all  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>Chain OUTPUT (policy ACCEPT 277 packets, 55759 bytes) 
> >>pkts bytes target     prot opt in     out     source
> >>    
> >>
> >destination
> >  
> >
> >>Chain RH-Firewall-1-INPUT (2 references) 
> >>pkts bytes target     prot opt in     out     source
> >>    
> >>
> >destination
> >  
> >
> >>277 55759 ACCEPT     all  --  lo     *       0.0.0.0/0      
>       0.0.0.0/0
> >>    
> >>
> >
> >  
> >
> >>  0     0 ACCEPT     icmp --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>icmp type 255 
> >>  0     0 ACCEPT     esp  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>  0     0 ACCEPT     ah   --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>  0     0 ACCEPT     all  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>state RELATED,ESTABLISHED 
> >>  0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>state NEW tcp dpt:25 
> >>  0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>state NEW tcp dpt:80 
> >>  0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>state NEW tcp dpt:21 
> >>  0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>state NEW tcp dpt:22 
> >>2451  247K REJECT     all  --  *      *       0.0.0.0/0
> >>    
> >>
> >0.0.0.0/0
> >  
> >
> >>reject-with icmp-host-prohibited
> >>
> >>
> >>Thanks for the help, looking forward to the solution, Jeroen
> >>
> >>
> >>
> >>	
> >>	
> >>		
> >>___________________________________________________________
> >>WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail 
> >>Internet Cafe Awards  www.yahoo.co.uk/internetcafes
> >>
> >>
> >> 
> >>
> >>    
> >>
> >
> >
> >
> >--
> >fedora-list mailing list
> >fedora-list@xxxxxxxxxx
> >To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> >
> >
> >  
> >
> 
> 
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> 



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux