Re: Determining IP information for eth0 failed

From: Jeroen Van Goey (peak_freak_at_yahoo.com)
Date: 03/31/04

Next message: ems: "clean Open Office 1.1.1"

Previous message: Travis Fraser: "RE: About RULE for FC1, was: 486 install?"
Maybe in reply to: Jeroen Van Goey: "Determining IP information for eth0 failed"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Wed, 31 Mar 2004 15:22:45 +0100 (BST)
To: fedora-list@redhat.com

> Am Mi, den 31.03.2004 schrieb Jeroen Van Goey um 02:19:
>
> > I'm unable to make contact with the internet. I get an "Unable to find
> > IP
> > address for server name "localhost.localdomain" - Host name lookup
> > failure" error message. The step-by-step procedure I've followed so
> > far.
> >
> > I have a Fast Ethernet 10/100M PCI network card from Genius on a linux
> > PC running Fedora core 1, kernel 2.4.22-1.2115.nptl and GNOME. My
> > system recognizes the networkcard, because at bootup, I see (using the
> > command "dmesg | grep eth0"):
> > eth0: RealTek RTL8139 Fast Ethernet at 0xc48bd000, 00:40:f4:6f:b4:90,
> > IRQ 11
> > eth0: Identified 8139 chip type 'RTL-8100B/8139D'
> > divert: freeing divert_blk for eth0
> > divert: allocating divert_blk for eth0
> > eth0: RealTek RTL8139 Fast Ethernet at 0xc48d6000, 00:40:f4:6f:b4:90,
> > IRQ 11
> > eth0: Identified 8139 chip type 'RTL-8100B/8139D'
> > eth0: link up, 10Mbps, half-duplex, lpa 0x0000
>
> > So I presumed the driver is 8139too, which I loaded -I think-
> > succesfully (using "modprobe 8139too io=0e400 irq=11"), because
> > "lsmod" gives me:
>
> > [note: yes, I am aware about the recent discussion on this list that the 8139too is
> not a
> > good ethernet chipset, but I bought it because I originally had on my Windows-machine
> a
> > USB to Ethernet convertor (USB LAN 100 from Topcom), that didn't support Linux; and
> I'm
> > not very jumpy to run to the shops a third time.]
> >
> > I adapted /etc/modules.conf to:
> > alias usb-controller usb-uhci
> > alias eth0 8139too
> > options 8139too io=0xe400 irq=11
>
> The card is an ISA one? Only to ISA cards you have to and can pass
> resource information for IO and IRQ. PCI cards will detect that
> themselves.
>
> > I'm not sure if that was entirely correct. Are 2 aliasses allowed? Is
> > my choice for IRQ=11 correct? On "cat /proc/interrupts" both my
> > ethernetcard and my USB are listed on 11, both won't this give any
> > confusion?
> > CPU0
> > 0: 748046 XT-PIC timer
> > 1: 10625 XT-PIC keyboard
> > 2: 0 XT-PIC cascade
> > 8: 1 XT-PIC rtc
> > 11: 81790 XT-PIC usb-uhci, eth0 <---------
> > 12: 60518 XT-PIC PS/2 Mouse
> > 14: 154475 XT-PIC ide0
> > NMI: 0
> > ERR: 0
>
> So far all looks pretty.
>
> > I then went on to configure my network with the command
> > "redhat-config-network", which gives a GUI. In the tab "Devices" I
> > selected "New" > Ethernet connection > RTL-8139/8139C/8139C+ (eth0) >
> > automatically obtain IP adress settings with DHCP. When I then save
> > and select my eth0, there is the error message "Determining IP information for
> eth0....
> > Failed"
>
> > In /var/log/cups/error_log.1 I find this line:
> > E [27/Mar/2004:00:21:53 -0500] StartListening: Unable to find IP
> > address for server name "localhost.localdomain" - Host name lookup
> > failure
> >
> > The command "ifconfig -a" gives this output. I notice that the IPs for inet
> > addr, Bcast and Mask are missing.
> > 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)
>
> Weird that loopback (lo) has no assigned IP address. Please check the
> content of
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-lo
> 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
>
> Many services rely on a proper setup of the loopback device. I think the
> other errors are mainly follwing errors because loopback has no address.

The contents of /etc/sysconfig/network-scripts/ifcfg-lo are exactly as stated above.

Some more info that may be helpfull: I can ping localhost, but no other adress (network
unreachable).
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=1 ttl=64 time=0.139 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=0.137 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=0.126 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=4 ttl=64 time=0.136 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

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"
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

Sorry for making the mail so long, but I hope that it can shed some light on the problem.
>
> > I can't get much out of this, but sometimes I recognized something, like in:
> >
> > 52:21.988678 81.83.160.1.bootps > 255.255.255.255.bootpc: xid:0x3abb2391
> > flags:0x8000 Y:81.83.160.26 G:81.83.160.1 ether 0:0:39:bb:23:91 vend-rfc1048
> > DHCP:OFFER SID:195.130.132.97 LT:7200 SM:255.255.240.0
> > NS:195.130.131.4,195.130.130.4 DN:"pandora.be" RSZ:576 TTL:64
> > BR:255.255.255.255 RN:3600 RB:3601 HN:"toshiba" DG:81.83.160.1
> > 4500 0160 f72c 0000 ff11 d20b 5153 a001
> > Where "pandora.be" is the name of the ISP which provides me with dynamic
> > IPs.
> >
> > Some more info that I was able to squeeze out of my machine:
> > The contents of my /etc/sysconfig/networking/devices/ifcfg-eth0 file:
> > USERCTL=yes
> > PEERDNS=yes
> > TYPE=Ethernet
> > DEVICE=eth0
> > HWADDR=00:40:f4:6f:b4:90
> > BOOTPROTO=dhcp
> >
> > The following came from a log file. A lot of things are not yet filled in.
> > Should I change and add them in in ifcfg-eth0 manually, or should dhclient
> > (or some other program) do that for me?
> > Mon Mar 29 10:10:31 2004: -+ //etc/sysconfig/networking/devices/ifcfg-eth0
> > NETMASK=''
> > DOMAIN=''
> > BOOTPROTO='dhcp'
> > HWADDR='00:40:f4:6f:b4:90'
> > DEVICE='eth0'
> > IPADDR=''
> > DHCP_HOSTNAME=''
> > TYPE='Ethernet'
> > GATEWAY=''
> > PEERDNS='yes'
> > USERCTL='no'
> > ONBOOT='yes'
> > NETWORK
> > BROADCAST
> > DOMAIN
> > DHCP_HOSTNAME
> > IPADDR
> > NETMASK
> > GATEWAY
> >
> > That's about as much information as I can give you.
> > Where did I go wrong, or what did I forget?
> > Thanks for the help.
> >
> > Jeroen
>
> Alexander
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@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

Next message: ems: "clean Open Office 1.1.1"

Previous message: Travis Fraser: "RE: About RULE for FC1, was: 486 install?"
Maybe in reply to: Jeroen Van Goey: "Determining IP information for eth0 failed"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

Re: Glancing blow.
... relaibly be able to draw a long enough chain of cards to do 12 damage ... tolerable rush deck is "can reliably nuke a full 11 cap that has ... cards. ... It's your opinion, I can see the realities of ...
(rec.games.trading-cards.jyhad)
Re: Unintentionally Sympathetic Villains
... unknown characters polluting a crime scene and flashing ... of cops, and then let's just not trust the ID of anyone! ... I used to carry an ID card back when ID cards were rare; ... lieutenant's order since he's not in chain of command, ...
(rec.arts.sf.written)
Re: Glancing blow.
... So you need a third card - the rush. ... Frontal Assault (much, much more powerful for a weenie deck), or even ... key vampires you're going to need multiple cards to take them down. ... You need a 4 chain combo to get off the rush, the IG, the Torn Signpost, ...
(rec.games.trading-cards.jyhad)
Re: View ISA IRQ assignments in XP?
... While Windows can be made to do things it wasn't really designed for, eventually it just becomes too much trouble to make it work that way. ... old ISA cards. ... Ted Zieglar wrote: ... cards are not listed. ...
(microsoft.public.windowsxp.hardware)
Re: View ISA IRQ assignments in XP?
... old ISA cards. ... PCs they want with ISA slots. ... Ted Zieglar wrote: ... cards are not listed. ...
(microsoft.public.windowsxp.hardware)