I have some trouble in my network setup, but I have very limited knowledge of networking. I recently purchased an ADSL modem, which also has a built-in router, DHCP and other stuff (as I discovered later). I already had a server/firewall/router pc that took care of IP masquerading, but I managed to put everything together ok except for one thing: I can not access my server with the external IP from inside my LAN (no problems from outside). This is my setup: Internet | | 98.81.118.53 (example) (ppp) Modem which forwards every connection to the server 10.0.0.138 (eth0) | | 10.0.0.39 (eth0) Server, provides IP Masq for LAN 192.168.0.1 (eth1) | | 192.168.0.2 Internal Masq'ed PC) So if I try to surf from the server itself or an internal PC or to 98.81.118.53 I get nothing, but access from outside works perfectly. If I try 10.0.0.39 it works fine. I figured it had something to do with my firewall, so I checked the server logs, where every attempt to access the server from the server itself brings up this: Aug 31 21:11:48 localhost kernel: martian source 10.0.0.39 from 10.0.0.39, on dev eth0 Aug 31 21:11:48 localhost kernel: ll header: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx It seems the modem, is incorrectly setting the return address when forwarding the packets back to the server. How can I fix this? Thank you!

Why not just get rid of the routing function on the server?

You cant access any computers/servers on the same LAN as you with the external IP address of your router ... thats just the way it is I found this out as well when trying to access an FTP server on my LAN with my routers external IP address but accessing the FTP with its LAN IP worked fine, as well as accessing the FTP with my external IP from a location outside of my LAN ... it took me several weeks to find out it cant be done, no matter how much you play with the settings