|
In one of your posts you mentioned that the web server is not directly
connected to the internet. That caused me to think about it's routing
configuration... Does this server (10.30.143.1) have a route to get
back to the NAT box (10.30.142.12)? If not then your packets may be
getting NATed to the web server, but the response may not be coming back. For starters, try accessing 'http://10.30.143.1' from 10.30.142.12. If that works, then it isn't a routing problem. If that doesn't work, then no amount of tweaking of your iptables rules will help. Another possible problem that you may be having is due to how you're accessing the NATed service. Are your trying to access it from a third computer on the other side of the NAT box, or from that box itself? I know it can be tricky to get a packet originating from the NAT server itself to be properly processed by the iptables rules. You should be running your test connection to 'http://10.30.142.12' from a client machine on the 10.30.142.x subnet, not from 10.30.143.x or from the router itself. dave p. itachi@cnt.uo.edu.cu wrote: done ruter-deb:~# iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination SNAT tcp -- 10.30.142.12 anywhere tcp dpt:www to:10.3 0.143.1 Chain OUTPUT (policy ACCEPT) target prot opt source destination but when from my computer i do http://10.30.142.12 nothing happends :( |