[dhclient]force use of a well known dhcp server

Hi

Is it possible to force the dhclient to communicate only with a fixed
DHCP server

I think this will resolve the problem raised by a bad DHCP server
connecte to the LAN

Any comment is welcome

Regards

In message
<99409c10-f985-4ac1-8514-(E-Mail Removed)>, mbm
wrote:

> Hi
>
> Is it possible to force the dhclient to communicate only with a fixed
> DHCP server
>
> I think this will resolve the problem raised by a bad DHCP server
> connecte to the LAN
>
There's an option for dhclient.conf to force it to reject a particular
server, but I can't see one to force it to only communicate with a
particular one. That's not very fault-tolerant anyway.

--
Dave
mail da (E-Mail Removed) (without the space)
http://www.llondel.org
So many gadgets, so little time

On Apr 2, 7:36 am, mbm <mbmessa...@yahoo.com> wrote:

> Is it possible to force the dhclient to communicate only with a fixed
> DHCP server
>
> I think this will resolve the problem raised by a bad DHCP server
> connecte to the LAN
>
> Any comment is welcome

If you don't trust DHCP on the LAN for any reason, I'd recommend using
static configuration if at all possible. Otherwise, I suppose you can
add 'ipfilter' rules to block out DHCP packets from other MAC
addresses.

DS

Hello,

David Schwartz a écrit :
>
> If you don't trust DHCP on the LAN for any reason, I'd recommend using
> static configuration if at all possible. Otherwise, I suppose you can
> add 'ipfilter' rules to block out DHCP packets from other MAC
> addresses.

I'm afraid ipfilter is not the most common packet filter on Linux.
Anyway, this approach may fail because some DHCP clients such as
dhclient from the ISC DHCP package capture incoming packets at the
interface - just like packet sniffers - and not at the IP layer.