LinuxSA Mailing list archives

Index: [thread] [date] [subject] [author]
  From: Adrian Butterworth <adrian@econ-outlook.com.au>
  To  : hawjd001 <hawjd001@lux.levels.unisa.edu.au>
  Date: Thu, 01 Apr 1999 22:26:28 +0930

Re: dhcpd and DNS

Hi
I use on all my DHCP servers, 
 route add -host 255.255.255.255 dev eth0
If the static route lapses (because say I take the ethernet interface
down)
clients spew until I add it back. Its caused enough probs in sites that
I run a cron script to check periodically to ensure if I lose the route
it will get added in.

For a full discussion see the README  that comes with dhcp
In part it reads:

...
>                               BROADCAST
> 
> In order for dhcpd to work correctly with picky DHCP clients (e.g.,
> Windows 95), it must be able to send packets with an IP destination
> address of 255.255.255.255.  Unfortunately, Linux insists on changing
> 255.255.255.255 into the local subnet broadcast address (here, that's
> 192.5.5.223).  This results in a DHCP protocol violation, and while
> many DHCP clients don't notice the problem, some (e.g., all Microsoft
> DHCP clients) do.  Clients that have this problem will appear not to
> see DHCPOFFER messages from the server.
> 
> It is possible to work around this problem on some versions of Linux
> by creating a host route from your network interface address to
> 255.255.255.255.   The command you need to use to do this on Linux
> varies from version to version.   The easiest version is:
> 
>         route add -host 255.255.255.255 dev eth0
> 
> On some older Linux systems ...

Regards
Adrian

-- 
Check out the LinuxSA web pages at http://www.linuxsa.org.au/
To unsubscribe from the LinuxSA list:
  mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject


Index: [thread] [date] [subject] [author]
Return to the LinuxSA Mailing List Information Page