Hello,
* Nix wrote on 10/22/03:
> On Wed, 22 Oct 2003, Thomas Preissler muttered drunkenly:
> > The box itself has correct routing entries. The gateway is the IP of
> > the TAP-dev. I have encountered, that the IP does not matter...
> > Before starting dhclient I do a "ifconfig eth0 down".
> > But when I start "dhclient" on my box, I can't see the
> > DHCP-Requests. Then I get "SIOCSIFFLAGS: Protocol driver not
> > attached", what is this?
>
> dhclient needs the packet filter and packet socket options
> (CONFIG_PACKET and CONFIG_FILTER) enabled.
[Just for the archive]
Ah great, folks, thank you. Now it works perfect.
My problem was, that the DHCP-server on the host receives
DHCPDISCOVER and sends DHCPOFFER. But the box itself receives no
DHCPOFFER.
Shortly, the DHCP server must be binded on my br0 (too), and now it
works - nearly.
This
Oct 23 00:56:17 [kernel] martian source 192.168.0.2 from 192.168.2.50, on dev
br0
was a faulty routing entry only.
Now it works - really(!).
Greets,
Tom
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
|
