Re: Some more info... "Determining IP information for eth0 failed"

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


Date: 1 Apr 2004 02:45:49 -0800


"Jan Geertsma" <jan@islief.com> wrote in message news:<c4f3v8$7o7$1@phys-
> * your io-address is 0x6000 and not 0xe400....

I deleted "options 8139too io=0xe400 irq=11" completley, because my
PCI card should be able to detetect that herself. My etc/modules.conf
file looks as follows:
alias usb-controller usb-uhci
alias eth0 8139too

/etc/hosts is:
127.0.0.1 localhost.localdomain localhost

> * are you sure that you don't have a very strict firewall setup (iptables or
> something like that) that also blocks incoming dhcp offers.
I was also beginning to think that it maybe could be a firewall issue.
The output from "iptables -L -n -v" is:
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

And the output of "route -n" is:
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

Are there any other commands that you need to determine if it's a
firewall issue? I will be happy to post them.

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 another tought was that I should search the
solution into masquarading, gateways, etc.

> * your interfacecard actually has lots of traffic while it was up. (13Mb
> received ???)
> * you actually get an dhcp-offer by the looks of your tcpdump trace. so the
> response looks ok

Ah, soma good news as well. The light at the end of the tunnel is in
sight. (Just hoping itīs not another freight train comming my
direction ;)

Thanks for the support, looking forward to the feedback.
Jeroen

> * netconfig is part of linuxconf, which is a nice tool, but there should be
> other nice gui's as well (setup?)
>
> goodluck. Jan
>
> "Jeroen Van Goey" <peak_freak@yahoo.com> wrote in message
> news:c8619276.0403301518.3ebfcf17@posting.google.com...
> > > * use "ifconfig" and "ifconfig -a" to see the current status and the
> status
> > > of all the devices.
> > This is my output. If I compare it to yours, I see missing IPs for inet
> > addr, Bcast and Mask.
> > 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)
> >
> > > * "ifup eth0" brings up the networkcard via nice scripts,
> > Gave the same error as before. BTW, I use a dutch interface, so I roughly
> > translated my error message into "Checking for IP information for eth0...
> > Failed", but the actual errormessage that is shown in english is
> > "Determining IP information for eth0.... Failed" (should help those who
> are
> > googling for this phrase).
> >
> > > * if this all fails start looking at the dchp server ... does it need
> extra
> > > parameters, does it expect a certain mac-address from your network card.
> and
> > > is your broadcasts working (which you can check with tcpdump)
> > I don't understand much of this, but on
> > http://users.pandora.be/bdr/DHCP/dhcp.html the command "tcpdump -n -i
> > eth0 -l -s 500 -x udp port 67 or port 68 | tee dhcp_dump" was recommended.
> > 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
> >
> > >* personally I use netconf to set my network.
> > This command was not on my computer, but I will try to find it online, and
> > compile it on my computer. Thanks for the help, and any other pointers in
> > the good direction are appreciated.
> > Jeroen