- DHCPD Woes
- Posted by Trouble@Mill on August 16th, 2003
Thanks for all the hints. I've now solved it.
It was the IPTABLESS firewall I use. It doesn't allow a DHCP Server
unless you specifically tell it. Once I put that option in the
script, everything worked fine.
Now all I have to do is report that it still allowed one device to
talk to the DHCP server, but not others. Strange.
The "ddns-update-style ad-hoc;" line isn't needed because this is a
Slack 8.0 system with an older version of DHCP.
Cheers,
Eddie
- Posted by Tauno Voipio on August 17th, 2003
"Trouble@Mill" <Trouble@Mill.> wrote in message
news:4gatjvsub060cv1be3o2a4q66gphi4vphb@4ax.com...
Your hole in the firewall is probably too tight for all clients.
Please check that the firewall scripts log all discarded or rejected packets
and check the log for the DHCP (UDP ports 67 and 68) traffic of the rejected
clients.
HTH
Tauno Voipio
tauno voipio @ iki fi
- DHCPD behind a CCS. (Routers) by AM
- DHCPD behind a CSS. (Routers) by AM
- pix, dhcpd . ip reservation's (Routers) by jarcar
- Pix 501 dhcpd (Routers) by Sorin Platon
- DHCPD Woes (Linux / Variants) by Menno Duursma

