Sorry for the off posts .. I have 2 clients w/ 2 configs.
What I think you need to do is the following... Check the DHCP range that your router is serving: 192.168.1.100 - 192.168.1.254 (on my Router/Accesspoint also linksys) This info can be found on the DHCP tab of the routers web interface. This means you can safely assign address 2-99 statically on your LAN. Assuming you have not changed the internal ip of the router which is 192.168.1.1. If you assigned your server 192.168.1.1 you would have an address conflict. Give the other box with the service you want to expose on of these free address 192.168.1.10 will due. Then check the status page on the router to determine the external DNS servers and add those to /etc/resolve.conf Im not sure of you distribution but somewhere you need to set the default gateway for the server. On my wireless net the gw is 192.168.1.1 again its a linksys and should be the same. If you want to make sure run the route command. It will list your default gateway. Finally update your forwarding rules to reflect your clients new static ip. DONE! Note you should be able to access your current verizon DNS servers no mater what ip they give you. I had version and a similar config worked for me. If for some reason you cannot access those DNS servers you could run a caching name server on you LAN to provide DNS. That could be a cool Linux project to. On Fri, 2003-08-01 at 22:20, Charles R. Anderson wrote:
If you statically configure your client, can you not use the Linksys as the DNS address? Maybe the Linksys can act as a DNS Forwarder, forwarding all requests to your ISP's DNS servers.
On Fri, Aug 01, 2003 at 06:31:14PM -0400, Michael Long wrote: mlong> rules. I would prefer to use static IP's but I am depending on my isp mlong> (verizon dsl) provider for their dns servers and they serve me with a mlong> dynamic address which changes reqularly.