No subject

HOWTO.html#toc3)...

"There are still a few more steps. Next, edit 
the /etc/rc.d/init.d/dhcpd file and look for the following line: 


/sbin/route add -host 255.255.255.255 dev eth1
 

Windows DHCP clients require a particular broadcast address in DHCP 
responses, and this command forces the Linux TCP/IP stack to produce 
it. If you cannot find that line in the file, add it. If you do find a 
line like that one, make sure that the device it references is eth1. 

The next step is to alter the /etc/rc.d/init.d/dhcpd file to use eth1 
as the default device. Replace the line: 


daemon /usr/sbin/dhcpd
 

With: 


daemon /usr/sbin/dhcpd eth1"

Silly Windows.

BB


Brian Barber
Ottawa, ON   CANADA
brian.barber at mysun.com

----- Original Message -----
From: "Timothy Brier" <briert at cepu.ca>
Date: Sunday, June 9, 2002 6:22 pm
Subject: [oclug] DHCP Server

> I recently set up a DHCP server.  Everything is working fine, but 
> I have a
> question.
> 
> The only way I could get a windows machine aquire an address was 
> to assign
> an alias address to the network of the subnet.  An example is on 
> subnet192.168.0.0,  I had to create an alias for the ethernet 
> card, so the system
> had two addresses: 192.168.0.100 and 192.168.0.0
> 
> The question: Is there a way to not use the 192.168.0.0 address?
> 
> 
> Thanks,
> 
> Tim.
> 
> _______________________________________________
> oclug mailing list
> oclug at lists.oclug.on.ca
> http://www.oclug.on.ca/mailman/listinfo/oclug
>