This is a bit of a newbie question; I'm new to linux networking, so
please take pity. :)
I've been trying unsuccessfully to get dhcpcd to work under 2.1.129 and
.130, with BCtel's ADSL service in Vancouver, Canada. It looks as if the
dhcp request is going out, and an answer is coming back, but dhcpcd
times out not seeing it. If I run tcpdump on the interface, I see the
outgoing packets, but no incoming packets are ever reported, including
the occasional routing traffic coming down the line.
Under 2.0.36, dhcpcd 0.70 works fine, and tcpdump shows both the dhcp
server's response and the routing traffic. The blinkies on the ADSL
modem show incoming traffic (and what looks a lot like a server
response) under both kernels. I'm using dhcpcd 1.3.16 under the 2.1
kernels.
I guess I'm stumped. The author claims he's used dhcpcd successfully
under 2.1.129, so presumedly it's talking to the kernel correctly. The
question in the title came up before I'd spoken with him--some of the
client documentation mentions enabling ip_bootp_agent under
/proc/sys/net/ipv4. While this option was documented in 2.1.129, it
didn't seem to be implemented, and has vanished entirely under 130. So
my first question was "Where did it go?" along with "Is it necessary?
What's the workaround"
Any other ideas would be much appreciated.
FWIW, I tried the new bootp kernel autoconfig, and it times out
similarly. Didn't expect it to work, but thought I might see a refusal
from the server at least, since bootp and dhcp use the same ports.
Thanks for reading this far. :)
-ralph
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
