Network/Internet is dodgy

Virtuality · 12-14-2007, 06:33 AM

Hi,

The first time I installed debian etch my network wasn't working, I had the drivers but hadn't managed to build the kernel source. So I could not install them.

I had tried enabling/disabling and changing settings (there are very few) in the network manager. As I worked on my system I noticed my DSL light showed it was connected and the internet worked - for no reason whatsoever.

Now I've formatted, re-installed and I can't get it working.

I did nothing that would affect it the last time. I never did install the driver.

This time it showed no connection, nothing, eventually it simply felt like turning on.

But this time I can not open websites, can't ping, can't do anything although it says DSL is connected. I'm using a siemens 4200 router, ethernet not USB.

When my system is starting up it says:

Code:

Listening/..something.. on LPF/eth0
Sending on socket/fallback (I think, bad memory, didn't manage to write this bit down)

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval <random number>

Sure took it's time too...

What do I do to make it so I can use the network properly again (I can't install the drivers UNTIL i have internet access).

When I try to ping the router it just says 'network is unreachable'.

gd2shoe · 12-16-2007, 09:06 PM

Your router is supposed to be a DHCP server. It sounds like your system is detecting the network card, but is unable to obtain a DHCP lease from the router.

Check to make sure the "link" light is on on your network card and on the router. This will tell you it's plugged in. Even if the light is on, you may have a bad cable.

It's possible the router isn't issueing the DHCP leases. You could try temporarily and manually setting an ip address. At the command line, and as root, type:

Code:

ifconfig eth0 up 192.168.0.10
route del default                     # usually not needed
route add default gw 192.168.0.1
ping 192.168.0.1

I am guessing here. There is no good way to tell what subnet your router wants to use if it doesn't auto detect. Furter, some routers will not return ICPM ping packets (even from the internal network on rare frustrating ocasions).

You can also try:

Code:

gateway:      IP address:
192.168.1.1   192.168.1.10
192.168.2.1   192.168.2.10
192.168.1.254 192.168.1.1
172.16.0.1    172.16.0.10
172.16.1.1    172.16.1.10
172.16.0.254  172.16.0.10
10.0.0.1      10.0.0.10

And similar iterations. I'm not actually suggesting you try all these, only if you're desparate. I would try the 172.16.0.1, though.

You should also consider pinging an external ip address, such as 64.233.167.99 (belongs to google). ping addresses instead of names until you get it working to that extent.

Virtuality · 12-17-2007, 04:54 PM

It was simply a problem with my NIC drivers and has been fixed, thanks