Another internet connection/dhclient/interfaces problem

This seems similar to the previous post:

Just, in my case, after compiling 2.6.20 kernel under lenny, suddenly two things started happening:
1) dhclient activates at boot. this wasn't the case in Sarge. is does what it does to the eth1 interface and the output seems ok. When i ping the network address it connected to this also seems right.
2) i can't ping anything else on the Internet, my browser can't connect to anything else on the Internet.

However, after I "telinit 1" (why did I do this, i don't know), internet connection starts to work normally.

I would like Internet working under a normal runlevel, so does anyone have a clue?

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Another internet

Go to /etc/rc1.d and check the order of networking scripts, then go to /etc/rc2.d and see if any scripts are missing or out of order.

It is also possible that the scripts are out of order in both rc1.d and rc2.d, but since one script was already run on boot to runlevel2, the second script is run again when you switch to runlevel1 and everything seems OK. You can test that by switching to runlevel3 instead of 1 - rc3.d in a default install is exactly the same as rc2.d.

The scripts (actually links) with the lower numbers are executed first - so 00 runs before 99

You also need to tell us a bit more about your network - do you use DHCP to assign addresses? If you do then there's usually nothing else to do because DHCP will also set the gateway and DNS lookup addresses (but you can check to make sure the gateway and DNS have been set up correctly).

Another internet

Hey, thanks pinniped!

1) rcS.d/
ifupdown-clean is S18
ifupdown is S39
networking is S40

rc1.d and rc2.d (as well as rc3.d) do not
have links to these scripts
2) i have K-ed S40networking script and now, after boot, I manually do "ifup eth1" and it works. So my idea is that there is something wrong with the /init.d/networking script, unless the order in rcS.d is wrong, as you said.
3) i use dhclient to connect to a university network

Another internet

Those are the default priorities; have you checked that 'udev' runs first? Have you looked through the logs shortly after boot to see if there are any messages giving you a clue as to what's going wrong?

Immediately after boot you can check your routing tables to see if dhclient had in fact set up routing correctly:
route -n

If the routing table looks OK, then try name resolution:
host www.google.com

Also check the actual network settings:
ifconfig eth0

Syndicate content