[EMAIL PROTECTED] wrote: > We have a big old Dell running RedHat, which does nothing (any more) but > serve DHCP for a number of labs around our campus. We thought it would > be an ideal candidate for replacement with a home-rolled GNAP machine > using dnsmasq's DHCP service. It seemed to work well in testing, but > when we dropped in the replacement system we found that machines on > remote VLANs could no longer get addresses. > > The campus network runs on Cisco switches, controlled by another group. > I'm pretty much Cisco-ignorant myself, but my undertanding is that the > VLANs which serve our DHCP clients have been configured to propagate > DHCP requests beyond the local segment and on to our centrally-located > DHCP server, and this works fine with the old machine.
This cisco equipment could be filtering based on MAC addresses. You could put one of the dhcp clients on the same LAN as the server and see if they work together. If they do, then your problem is your campus network security. If not, then get the two (DHCP server and DHCP client working on the same network segment; then move the client back to it's proper segment and debut the network. Use Ethereal to watch the new DHCP server and one of the DHCP clients on a quite test network. Get those 2 working first, then distribute/debug the new server's DHCP services... hth, James -- [email protected] mailing list
