Quote Originally Posted by marshalx
yes im looking at that now gnarvaja,
but i dont see anything about "request broadcast response"

i have Cable Modem into Wireless Router then out to the mobo
ABIT kv8pro onboard ethernet via rj45 (wLan not being used).

so as far as linux looking at eth0 is concerned,
does it think that is just dhcp ppp from doesnt_matter_where ?

[dont have to tell it Cable Modem nor Adsl nor anything
other than it auto-detects ppp on eth0 ?]
Ok, I'm not a guru on this issue, but the request broadcast response is usually associated with wLan/DHCP, and I understand you're not using wireless. I would guess that your problem is between the Router and you eth card configurations. I use a wireless router with 3 PCs connected to it: 2 over cable, 1 over WiFi with no problems, so it should work fine.

Usually pump takes care of the DHCP interface automatically. First make sure that pump is running
Code:
ps -ef | grep pump
If it is not, you'll have to figure out why. If it is, play with the configuration parameters to see if the problem goes away. The man pages are not very helpful for your particular problem, so you (or any other curious soul) may need to dig into the source code for clues. You may also want to look into the router's documentation for clues in the way it handles the DHCP protocol. Before modifying any configuration file, you may try using ifconfig and pump interactively as root.

Googling with the following string (include the "s) "request broadcast response" brings a lot of different messages in different forums on the subject. I didn't have time to browse all of them. It seems to me that this behaviour is tied to Windows DHCP clients and many Linux distributions have a hard time dealing with it by automatically. Googling with the string "DHCP protocol handshake" (do not include quotes this time) I found more technical information, but I'm not sure if you want to get your hands dirty with bits and bytes.

I hope this narrows the search,

--GN