-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Paulo,
sorry, but you don't provide enough useful information to figure out the reason :( Could you please give your ruleset to the list and if possible some meaningful captures of communication (if possible capture both interfaces) ?
Thanks,
Jörg
Paulo Andre schrieb:
| Basic drawing to explain problem. | | eth1 (192.168.192.1) | Linux FW | eth0 (172.17.0.1) | LAN A | | My firewall has a nat for 192.168.192.1:80 to 172.17.0.10:80 | | From a client I can not open a session to 192.168.192.1:80. Is this | because of the connection tracking or is there a way to sort this | out. |
- -- - ----------------------------------------------------------------------- mnemon Jörg Harmuth Marie-Curie.Str. 1 53359 Rheinbach
Tel.: (+49) 22 26 87 18 12 Fax: (+49) 22 26 87 18 19 mail: harmuth@xxxxxxxxx Web: http://www.mnemon.de PGP-Key: http://www.mnemon.de/keys/harmuth_mnemon.asc PGP-Fingerprint: 692E 4476 0838 60F8 99E2 7F5D B7D7 E48E 267B 204F - ----------------------------------------------------------------------- Diese Mail wurde vor dem Versenden auf Viren und andere schädliche Software untersucht. Es wurde keine maliziöse Software gefunden.
This Mail was checked for virusses and other malicious software before sending. No malicious software was detected. - -----------------------------------------------------------------------
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCOBZDt9fkjiZ7IE8RAjBFAKCd372wij0Xj981cEkc27G75OUJ5gCgkheD xeBAWASr1o87ib7Ad0Vm+dU= =JsZd -----END PGP SIGNATURE-----
