Re: Determining IP information for eth0 failed

From: Alexander Dalloz (alexander.dalloz_at_uni-bielefeld.de)
Date: 03/31/04

  • Next message: Robert Boucneau: "RE: Fedora core 1 sendmail problems"
    Date: Wed, 31 Mar 2004 02:47:33 +0200
    To: For users of Fedora Core releases <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.

    > 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

    -- 
    Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
    Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2174.nptl
    Sirendipity 02:43:46 up 11 days, 10:25, load average: 0.06, 0.08, 0.09 
                       [ Γνωθι σ'αυτον - gnothi seauton ]
                 my life is a planetarium - and you are the stars
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Robert Boucneau: "RE: Fedora core 1 sendmail problems"

    Relevant Pages

    • Re: Networking over IEEE 1394 IMPOSSIBLE?
      ... The solution is to get an ethernet hub for the internet. ... share the internet connection and files between two machines. ... I want to make a network connection over firewire between 2 machines; ... The card is a TI IEEE 1394a. ...
      (microsoft.public.windowsxp.hardware)
    • Re: Problem with NON-Wireless network card
      ... Under previous kernel, which I still have installed, it finds this card and configures eth0 to use it. ... Since it is not in the hardware list in the network configuration utility, ... First as root in a terminal type lspci and from the list should be your Ethernet card. ...
      (Fedora)
    • Re: New NIC: Why Printers Connecting Under Old NIC?
      ... I switched around the hop counts as per a couple people. ... The new Ethernet hop count 1. ... Print to network printer still connects through old TR card, ...
      (comp.sys.hp.mpe)
    • RE: Cannot ping or be pinged no matter what...
      ... I have also had ethernet cards that tested fine and did not work, ... > I have a Windows XP machine on a workgroup network of 4 ... This one computer cannot ping anything else (including the ... > * Changing the network card, to one that's been known to work on the ...
      (microsoft.public.windowsxp.network_web)
    • sucess report 3.x cd
      ... using the rtl3189 pci network card. ... Partitioning took some fuss but was ok. ... Here's what I did to get the network going on that pci card. ...
      (comp.os.minix)