From: whiplash <whiplash@bofhland.org>
To: Fabio De Paolis <fabiodepaolis@naxe.it>
Cc: netfilter@vger.kernel.org
Subject: Re: NAT Port Forward problem in a not so simple network
Date: Tue, 15 Apr 2008 14:15:25 +0200 [thread overview]
Message-ID: <48049C5D.8040104@bofhland.org> (raw)
In-Reply-To: <480479E8.3040904@naxe.it>
Fabio De Paolis ha scritto:
> Packet 4 Cisco1 reset the communication, perhaps because he wait a reply
> from HPpro1 and not Cisco2?
Of course.
A possible solution is to SNAT packets exiting from 192.168.0.11
with destination 192.168.0.2.
next prev parent reply other threads:[~2008-04-15 12:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 9:48 NAT Port Forward problem in a not so simple network Fabio De Paolis
2008-04-15 12:15 ` whiplash [this message]
2008-04-15 15:01 ` Grant Taylor
2008-04-17 14:49 ` Pascal Hambourg
2008-04-17 14:56 ` Grant Taylor
2008-04-15 14:57 ` Grant Taylor
2008-04-15 16:22 ` Fabio De Paolis
2008-04-15 16:45 ` Grant Taylor
2008-04-16 13:54 ` Fabio De Paolis
2008-04-16 14:34 ` Grant Taylor
2008-04-18 13:43 ` Fabio De Paolis
2008-04-18 14:46 ` Grant Taylor
-- strict thread matches above, loose matches on Subject: below --
2009-01-27 19:10 Fabio De Paolis
2009-01-27 20:34 ` Marek Kierdelewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48049C5D.8040104@bofhland.org \
--to=whiplash@bofhland.org \
--cc=fabiodepaolis@naxe.it \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.