On 2002.12.09 22:31 Rick Stevens wrote:
ISP. So you ARE getting DNS servers from your ISP.
No actually, I am pretty sure my server is not getting them from the ISP. My modem knows my ISP dns address and it knows what its own internet address is but it offers a completly different set of private ip addresses to my pc.
Wait. Your DSL modem is doing the DHCP client job? If that's true, and you always get a 192.168 address, then set your machine up with that fixed IP address (192.168.1.2), your netmask to 255.255.255.0, set your gateway to 192.168.1.1, set your resolv.conf to point at your ISP's DNS servers and TURN OFF DHCP on your system. Your modem is acting like a router/NAT device.
That did it and exposed what I had been doing wrong this weekend when I had tried something similar. I disabled DHCP on the eth0 interface and set the ip address to 192.168.1.2, then set the gateway to 192.168.1.1 and restarted the network. Sure enough it seems to work fine. My mistake had been to set the gateway to the interface on my server instead of my modem, Arrg! Don't care to remember how long I had spent this last weekend trying to figure out why it did not work.
I have just looked at the modem DHCP status and it shows no lease and it is still working.
Good deal. Yes, it sounds like your modem is really a modem/router/NAT/ firewall/DHCP server/DHCP client. Glad we could help. ---------------------------------------------------------------------- - Rick Stevens, Senior Systems Engineer rstevens vitalstream com - - VitalStream, Inc. http://www.vitalstream.com - - - - This message printed using recycled bandwidth - ----------------------------------------------------------------------