Thanks All
it works now.
I extended the range to :
"range 10.0.0.0 10.0.0.253;"
And rebooted
& it works. .......
using
" /etc/init.d/dhcpd stop" & " /etc/init.d/dhcpd start" didn't work
Also only on reboot dhcpd complains in /var/log/messages :
"Mar 25 17:18:48 front dhcpd: Not configured to listen on any interfaces!"
But thereafter it doesn't complain with:
dhcpd -d or " /etc/init.d/dhcpd stop" & " /etc/init.d/dhcpd start" combo
interesting !!
Thanks again
Roger
http://lists.slug.org.au/archives/slug/2004/03/msg00613.html Title: Re: [SLUG] Masquerding not compatible with DHCPD (dynamicipgeneration
[ Thread Index | Date Index | More slug Archives | SLUG Lists | SLUG Website ]
Roger Salisbury wrote: > > > thanks peter , kevin & phil > > my first mod > > was to correct /etc/dhcpd.conf with > > "option routers 10.0.0.1;" > > > & the error message to the ping command changed > to > > "....... 100% packet loss ....." > > > I don't know where to add the following. > > "default via 10.0.0.1 dev eth0;" > > Thanks for your help > > Roger > > Guessing here as I'm not sure if i've filtered/guessed the correct info: ping'ing outside world from internal machine behind a gateway machine which is serving dhcp to internal clients receives 100% packet loss. Do logs say anything? Either a. the gateway is refusing to forward the packets, or b. NAT is not enabled, or c. the gateway does not "know" (have a route) how to get back to the client. In all 3 cases the pong packet will not return to the client. Has the IP address range changed when going from static to dhcp? Fil
|
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
