In the redhat-config-network gui under the DNS tab (or in /etc/resolv.conf) you need to specify the DNS lookup servers. The IP addresses to use will depend on your provider. Here is my resolv.conf : search om.cox.net nameserver 68.13.16.25 nameserver 68.13.16.30 nameserver 68.12.16.30 On Tue, 2004-03-30 at 18:19, Jeroen Van Goey wrote: > 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 > > The output of "cat /proc/ioports" is: > 0000-001f : dma1 > 0020-003f : pic1 > 0040-005f : timer > 0060-006f : keyboard > 0070-007f : rtc > 0080-008f : dma page reg > 00a0-00bf : pic2 > 00c0-00df : dma2 > 00f0-00ff : fpu > 01f0-01f7 : ide0 > 0213-0213 : isapnp read > 02f8-02ff : serial(auto) > 0378-037a : parport0 > 037b-037f : parport0 > 03c0-03df : vga+ > 03f6-03f6 : ide0 > 03f8-03ff : serial(auto) > 0a79-0a79 : isapnp write > 0cf8-0cff : PCI conf1 > 4000-403f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI > 5000-501f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI > d000-dfff : PCI Bus #01 > e000-e01f : Intel Corp. 82371AB/EB/MB PIIX4 USB > e000-e01f : usb-uhci > e400-e4ff : Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ <----- > e400-e4ff : 8139too <----- > f000-f00f : Intel Corp. 82371AB/EB/MB PIIX4 IDE > f000-f007 : ide0 > > > So I presumed the driver is 8139too, which I loaded -I think- > succesfully (using "modprobe 8139too io=0e400 irq=11"), because > "lsmod" gives me: > Module Size Used by Not tainted > soundcore 6468 0 (autoclean) > ide-cd 35776 0 (autoclean) > cdrom 33728 0 (autoclean) [ide-cd] > parport_pc 19076 1 (autoclean) > lp 9060 0 (autoclean) > parport 37056 1 (autoclean) [parport_pc lp] > autofs 13364 0 (autoclean) (unused) > 8139too 16808 1 <--------- > mii 3992 0 [8139too] <--------- > ipt_REJECT 4344 1 (autoclean) > ipt_state 1080 5 (autoclean) > ip_conntrack 29256 1 (autoclean) [ipt_state] > iptable_filter 2444 1 (autoclean) > ip_tables 15776 3 [ipt_REJECT ipt_state > iptable_filter] > floppy 58012 0 (autoclean) > sg 36492 0 (autoclean) (unused) > scsi_mod 108168 1 (autoclean) [sg] > microcode 4700 0 (autoclean) > keybdev 2976 0 (unused) > hid 24708 0 (unused) > usb-uhci 26380 0 (unused) > usbcore 79168 1 [hid usb-uhci] > mousedev 5556 1 (autoclean) > input 5888 0 (autoclean) [keybdev hid mousedev] > ext3 71300 2 > jbd 52084 2 [ext3] > > [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 > > 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 > > > 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" > > 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 lo to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 > DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 15 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 21 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 > 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. > > 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) > > I don't understand much of DHCP yet, but on > http://users.pandora.be/bdr/DHCP/dhcp.html the command "tcpdump -n -i > eth0 -l -s 500 -x udp port 67 | tee dhcp_dump" was recommended to analyse problems. That > gave me some output like this: > > 22:49:31.034343 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x9c874c12 > vend-rfc1048 DHCP:DISCOVER PR:SM+BR+TZ+DG+DN+NS+HN+YD+YS+NTP [tos 0x10] > 4510 0148 0000 0000 1011 a996 0000 0000 > ffff ffff 0044 0043 0134 f4bf 0101 0600 > 9c87 4c12 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0040 f46f b490 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 6382 5363 3501 0137 > 0a01 1c02 030f 060c 2829 2aff 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 > > 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 > > > > > > ___________________________________________________________ > WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe Awards www.yahoo.co.uk/internetcafes >
