Graham Toal([EMAIL PROTECTED]) on 2005.10.26 23:52:28 +0000:
> They're not both connected to a DHCP server.  The DHCP server is
> only connected to one of the NICs.  Nevertheless I want both NICs
> to get an IP from that DHCP server.  I thought I could do it because
> they were bridged NICs.  I was wrong.

  man dhclient

     You must have the Berkeley Packet Filter (BPF) configured in your
     kernel.  dhclient requires at least one /dev/bpf* file for each
     broadcast network interface that is attached to your system.  See
     bpf(4) for more information.

  man 4 bpf

     The Berkeley Packet Filter provides a raw interface to data link layers
     in a protocol-independent fashion.  All packets on the network, even
     those destined for other hosts, are accessible through this mechanism.

As you found out, dhclient sends its DHCPDISCOVER-message out through the
interface on which it is run. This message wont get routed to some other
network. When dhclient starts there is no knowledge of "network" other than
your local link layer on the interface you tell dhclient to use.

Now, your "bridge" should bridge this dhcp-packet from one interface to the
other? That doesn't work: its sending this packet out through that
interface, it can't send it out on all other interfaces.

/Benno
--
Sebastian Benoit <[EMAIL PROTECTED]>
My mail is GnuPG signed -- Unsigned ones are bogus -- http://www.gnupg.org/
GnuPG 0xD777DBA7 2003-09-10 D02B D0E0 3790 1AA1 DA3A  B508 BF48 87BF D777
DBA7

"If we define a religion to be a system of thought that contains unprovable
statements, so it contains an element of faith, then Gvdel has taught us
that not only is mathematics a religion but it is the only religion able to
prove itself to be one." -- John Barrow, Pi in the Sky, 1992

[demime 1.01d removed an attachment of type application/pgp-signature]

Reply via email to