Have had Fedora Core 6 on this machine for a while working OK.
I connect to an ADSL modem via the onboard sis ethernet adapter.
Just installed 7.04 as well, and I can't get an internet connection.
I found some similar problems on the forum so I tried. "dhclient"

mike@ubuntu7:~$ sudo dhclient eth0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:85:f4:2d:3d
Sending on LPF/eth0/00:14:85:f4:2d:3d
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 10.1.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.1.1.1
SIOCADDRT: Network is unreachable
bound to 58.105.219.169 -- renewal in 59 seconds.
mike@ubuntu7:~$


Here's what core6 does.

[root@core6 ~]# dhclient eth1
Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:14:85:f4:2d:3d
Sending on LPF/eth1/00:14:85:f4:2d:3d
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 10.1.1.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 10.1.1.1
bound to 58.105.219.169 -- renewal in 51 seconds.
[root@core6 ~]#

I see 2 differences. Core6 calls the ethernet adapter eth1, ubuntu eth0. I think this is irrelevant.

The main difference is the SIOCADDRT entry.
Any body know what this means, and where to go from here???

I've tried pinging the modem but I get no returns.

what (if anything) is in your netfilter rules? (ref iptables(1)'s -L command) perhaps you have filtering rules which don't permit broadcast to the LAN (or something else) which the DHCP client on you system needs to interact with the DHCP server...
-c

Thanks cconstantine, I was looking for a firewall manager gui, thought ubuntu had one.
Guess I can copy my fedora iptables over, I'll give that a try and see what happens, (swapping eth0 and eth1).
I'll get back with any results.

Not as easy as I thought Fedora's set up differently, but I've done a iptables -L with this result.

mike@ubuntu7:~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root@core6 mike]#

Does this mean the firewall hasn't been set up, or does it mean there's no firewall??

Does it look as if it would stop eth0 connecting to the modem?

The firewall functionality (that is, the 'netfilter' portion of your kernel) is always "in there". But your netfilter rules are currently configured to allow everything, so it's effectively turned off. I wouldn't fiddle with your netfilter settings until you have your DHCP problem figured out.

Ok, so your netfilter rules aren't affecting your DHCP. We can cross that off the list of possible problems. Next, what's in your /etc/network/interfaces file?

-c

Thanks again -c

I suspected that the firewall was effectively off, but agree will leave that till later.

So here's the contents of /etc/network/interfaces.

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


I also tried a few more things, don't know if they'll help.
Seems to me dhcp is working, I'm assigned an ip address and can ping that address, (pinging myself I guess), but can't ping the modem.

mike@ubuntu7:~$ sudo dhclient eth0
There is already a pid file /var/run/dhclient.pid with pid 5586
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:85:f4:2d:3d
Sending on LPF/eth0/00:14:85:f4:2d:3d
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.1.1.1
SIOCADDRT: Network is unreachable
bound to 220.238.20.223 -- renewal in 52 seconds.
mike@ubuntu7:~$ sudo route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
220.238.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth1
mike@ubuntu7:~$ ping -c 2 220.238.20.223
PING 220.238.20.223 (220.238.20.223) 56(84) bytes of data.
64 bytes from 220.238.20.223: icmp_seq=1 ttl=64 time=0.066 ms
64 bytes from 220.238.20.223: icmp_seq=2 ttl=64 time=0.039 ms

--- 220.238.20.223 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.039/0.052/0.066/0.015 ms
mike@ubuntu7:~$ ping -c 2 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
From 169.254.6.100 icmp_seq=1 Destination Host Unreachable
From 169.254.6.100 icmp_seq=2 Destination Host Unreachable

--- 10.1.1.1 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1001ms

mike@ubuntu7:~$

...how about the output from "ifconfig -a"?

Your problem is the routing table.
As you can see, the default route is over eth1, not eth0.
When you try to ping 10.1.1.1, it can only go via eth1 (only possible route is the default route).

Try this:
Then try pinging your modem.

What I find a bit strange is the ip you recieve. Shouldn't you recieve a 10.1.1.0 address?
This might be a VPN thingy, but I have no experience with VPN...
But if you're able to boot up the Core6 distro again, I'd like to see your routing table on that one?
Anyways, you need to change the default route to connect to the internet (unless your internet access is on the other interface)
The above is only true if you are supposed to use 10.1.1.1 as a gateway (which is a bit strange considering the ip you recieve).

Thanks -c and Tyler,
I started with Tyler's code, hadn't noticed that eth1 was default, that's very strange, thought eth0 was normally default. When I installed ubuntu I noticed the "import daemon" running, could it have imported this from core6 or XP?
anyway I got very unexpected results.


mike@ubuntu7:~$ sudo route del default

mike@ubuntu7:~$ sudo route add default gw 10.1.1.1 eth0
SIOCADDRT: Network is unreachable
mike@ubuntu7:~$

mike@ubuntu7:~$ sudo route add default gw eth0
eth0: Unknown host

mike@ubuntu7:~$ sudo route add default eth0
SIOCADDRT: No such device
mike@ubuntu7:~$

Then I did the dhclient thing.

mike@ubuntu7:~$ sudo dhclient eth0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:85:f4:2d:3d
Sending on LPF/eth0/00:14:85:f4:2d:3d
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.1.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.1.1.1
SIOCADDRT: Network is unreachable
bound to 58.108.37.18 -- renewal in 53 seconds.

Then the route -n

mike@ubuntu7:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
58.108.37.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
mike@ubuntu7:~$

Then the ifconfig -a

mike@ubuntu7:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:14:85:F4:2D:3D
inet addr:58.108.37.18 Bcast:58.108.37.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:fef4:2d3d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16852 (16.4 KiB) TX bytes:8364 (8.1 KiB)
Interrupt:20 Base address:0xa800

eth1 Link encap:Ethernet HWaddr 00:E0:29:0E:A3:7F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:90 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:9975 (9.7 KiB)
Interrupt:22 Base address:0xc400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6176 (6.0 KiB) TX bytes:6176 (6.0 KiB)

mike@ubuntu7:~$


Now I've booted back into core6 and done the route -n

[root@core6 ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
211.31.137.132 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
58.108.37.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 211.31.137.132 0.0.0.0 UG 0 0 0 eth1
[root@core6 ~]#


Then I've done some whois checks for the above urls.
58.108.37.0 & 211.31.137.132 both belong to my internet provider 169.--- and 192. --- are IANA, but I guess you guys know that.

I think it's a double dhcp situation, the ADSL modem applies to my ISP for an address, then this computer applies to the modem, seems the modem just passes on what it's received rather than something in the 10.1.1.0 range.
I think in the past I have managed to set this computer in static mode using 10.1.1.3 as this address and gateway as 10.1.1.1

Just set up an old test version of core6 using a static address of 10.1.1.3 DNS search path and gateway of 10.1.1.1 Works fine, but still can't get ubuntu to connect.
Any more thought please.

OK making progress, can now ping the modem, but can't get any further, here's what I did.
Oh and previously I'd swapped eth1 with eth0, if anybody's wondering why we're now using eth1

mike@ubuntu7:~$ sudo route add -net 10.1.1.0 netmask 255.255.255.0 eth1
mike@ubuntu7:~$ ping -c 2 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_seq=1 ttl=64 time=0.251 ms
64 bytes from 10.1.1.1: icmp_seq=2 ttl=64 time=0.242 ms

--- 10.1.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.242/0.246/0.251/0.016 ms
mike@ubuntu7:~$ ping -c 2 192.168.122.0
PING 192.168.122.0 (192.168.122.0) 56(84) bytes of data.
From 10.1.1.3 icmp_seq=1 Destination Host Unreachable
From 10.1.1.3 icmp_seq=2 Destination Host Unreachable

Firefox will log onto the modem, but can't get any further, DNS ?????

Actually I've just installed my new cable modem with a new 10/10Mbit connection, and I noticed it "sort-of" looks like your setup:
My modem is accessible at ip 10.0.0.1, but I recieve an "official" IP on my external interface.
This suggests bridging is enabled in the modem. So the 10.0.0.1 IP is ONLY for administrative purposes.

This means the 10.1.1.0 route you add is optional, i.e. not neccessary for internet connections.

You should recieve an external IP on eth1 (when using DHCP), and the default route should adhere to that route.

But let's try something out first:
Try setting the default route like this:
Then fill in your DNS addresses in /etc/resolv.conf:
Where xxx... and yyy... is the ips for your primary and secondary DNS server.
After this you can try to ping www.google.com. If nothing happens, or you get an error, then we know you probably use the same setup as I mentioned above.

If the above is the case, you should try setting up eth1 for dhcp again.
You might want to try reinstalling the dhcp client program too, or even compile it from source, as DHCP should work without a problem.

Here's the debug procedure I would follow:
1. Check configuration files for dhcp-client/network interfaces etc...
2. Hardware problems? (modem/ethernet card/cables/router/switch etc...)
3. Library/kernel issues?.

If you have 2 different distros, one with internet and one without, you can probably drop item #2.

But I would go through the dhcp and network configuration files on the working distro, and check if I had done the same in the other distro.
If you have done the same things on both distros, I would check the kernel configuration on both distros to see if you are using the same drivers/modules in the network section.

Good Luck!

Thanks Tyler
I actually did manage to get it online for a few minutes today. Last night I'd forgotten about setting the default gateway, "sudo route add default gw 10.1.1.1 eth1"
When I went to do that today, found my static settings for eth1 had been swapped to eth0 mysteriously overnight. hoping that the MAC address had also changed I set the gateway for eth0. This didn't work, so I reset the static ip to eth1, set the gateway and it connected.
Then I fiddled around a bit, trying to figure out how to stop it reconfiguring itself on boot up, and low and behold it had stopped working again!!!

Tyler, thanks again for all your suggestions, I'm starting to get an idea of how this thing works now.
Read the manual for "route" it's a bit over my head but I get the idea, seems to say that it's mainly for static setups, that's why I tried going down the static path, the "route" commands didn't seem to work when using DHCP.

seems to be working now, I'm in the middle of an update.
I just unticked eth0 in the config gui, and it brings up eth1 during boot. So I think I'll leave it as it is in static mode.