Paul Schwartz wrote:Problem solved. Recompiling with CONFIG_FILTER set lets dhcp work. I think they ought to change the recommendation in menuconfig; it kind of says it's not important and to set it to N if you're not sure. Doesn't seem like a good choice; it oughtto at least mention its need for dhcp.
Paul Schwartz wrote:
Thanks for your patience. This is really a response the way you requested. I understand the
On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote:
>Try dhclient(8) manually from the command line. If that doesn't work,
>try spying on the connection using tcpdump(8). Punch your firewall
>properly. That's what I'd do. And please post the useful bits verbatim
>(e.g. that interfaces entry--who says it's not malformed?).
>
>The error messages are dmesg(8), ip(8)/ifconfig(8), tcpdump(8).
>
I tried executing dhclient; it just returns a prompt. This is what tcpdump collects from eth0 when I execute dhclient
Great! Now we know there is no DHCP traffic going out your box. Only some 802.1d bridge stuff. Bingo.
The configs look fine.
I'll be glad to to try other suggestions.
Go through the thread, and apply the suggestions already made :-) E.g.:
% ifconfig a % ip l % ip a % ip r
And: what was the dhclient's commandline? (Read: Was it correct?) And
tcpdump's. Post _with_ invocations. So again:
# dhclient -d eth0 # tcpdump -i eth0
--
Jan Minar "Please don't CC me, I'm subscribed." x 6
Oops. I meant NOT.
that is, NOT the way you requested ;-)
value of that and was preparing it, when I found a message in the daemon.log with a dhclient complaint. [I can't quote it here because I'm on another machine]. It pointed out the need for CONFIG_PACKET and CONFIG_FILTER in the kernel compilation. My kernel has the first but not the second. I'm off to fix that before proceeding with the rest.
I'll be back!
Paul
Thanks to all for the help.
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]