inconsistent dhcp behaviour

Forum: Networking
Topic: inconsistent dhcp behaviour
started by: stoneskin

Posted by stoneskin on Nov. 27 2005,23:58

I'm having trouble with my DSL (2.0) box connecting to my LAN/router.

After booting up, it will sometimes find the LAN and get internet connection, although I do have to click on DHCP Client (DSL Control Panel) which is initially pressed down before I can use the net.

Other times it just doesn't find the LAN. My router is acting as a DHCP server, and my XP machine is connecting fine, so i know it is not a problem with the connection.

Firstly , I don't understand why it seems so inconsistent in its behaviour. Secondly, is there a simple way of ensuring it quickly looks and finds the DHCP broadcasts?

Posted by stoneskin on Nov. 29 2005,17:06

to clarify my problem:

on startup DSL takes quite a long time (say 15 mins) to actually find the LAN (and its connection).

why would this be? other distos (SUSE or zenwalk for example) don't take this long! once the connection is esablished it is fine.

as a second part of the problem, this behaviour isn't consistent. Sometimes, DSL doesn't find the LAN at all.

does any one have any suggestions?

Posted by AwPhuch on Nov. 29 2005,23:28

perhaps corrosion on old hardware ethernet..or bad cables

Once the pump -i eth0 command is issued it will immediately query a DHCP server!

Brian
AwPhuch

Posted by larkl on Nov. 30 2005,12:50

Well,

I get inconsistent dhcp behavior with my wireless connection. Most of the time, the iwconfig and pump commands in my bootlocal.sh file do NOT connect me to the LAN. I have a second script that I have to run, sometimes twice before I connect. (It's the same commands that are in the bootlocal)

I'm using DSL 1.5 and a Netgear MA311. I'm doing a card_reset in both scripts before I then do the pump. May just be my card or something. If yours is working quickly all of the time, great!

Posted by stoneskin on Dec. 02 2005,13:02

Thanks, It must have been corrosion on old hardware ethernet, especially I then lost all connection. I think the old card was just dying.

Posted by AwPhuch on Dec. 02 2005,18:49

Quote (stoneskin @ Dec. 02 2005,08:02)

Thanks, It must have been corrosion on old hardware ethernet, especially I then lost all connection. 狢 think the old card was just dying.

So it was the hardware that was causing the problems??

Brian
AwPhuch

Posted by stoneskin on Dec. 05 2005,13:47

yes.

new ethernet card is fine