-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This time the iptable applied, but I still have the same problem; cannot verify that 443 is reachable.
- -- People just like you lose untold millions in personal wealth due to frivolous lawsuits and unfair government seizures. Are you protected? Read the Asset Protection Crash Course at http://www.keepyourassets.net?andrew to find out how to protect your hard-earned assets. Olaf Selke wrote: > Andrew Del Vecchio wrote: >> I got nothing: >> >> Chain PREROUTING (policy ACCEPT) >> target prot opt source destination >> >> Chain POSTROUTING (policy ACCEPT) >> target prot opt source destination >> >> Chain OUTPUT (policy ACCEPT) >> target prot opt source destination > > sorry dude, no idea! On my box it does work: > > iptables -t nat -A PREROUTING -p tcp -d 195.71.90.10 --dport 443 -j DNAT > --to-destination 195.71.90.10:9080 > iptables -t nat -A PREROUTING -p tcp -d 195.71.90.10 --dport 80 -j DNAT > --to-destination 195.71.90.10:9090 > > gives > > anonymizer:~# iptables -L -t nat > Chain PREROUTING (policy ACCEPT) > target prot opt source destination > DNAT tcp -- anywhere anonymizer.blutmagie.de tcp > dpt:https to:195.71.90.10:9080 > DNAT tcp -- anywhere anonymizer.blutmagie.de tcp > dpt:www to:195.71.90.10:9090 > > Chain POSTROUTING (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > > regards, Olaf > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHeVWngwZR2XMkZmQRAlkxAJsG0hkxqFxuYhTkdX0VQ9Y9nUR2IACfa/Gv ZU2/HZqYyvifDfIP9JH94dk= =3Y+0 -----END PGP SIGNATURE-----