Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: NAT overlaps with ports
Date: Wed, 23 Sep 2009 15:45:57 +0200	[thread overview]
Message-ID: <4ABA2695.3030804@plouf.fr.eu.org> (raw)
In-Reply-To: <4ABA0329.70102@edu.physics.uoc.gr>

Kapetanakis Giannis a écrit :
> 
> What I'm worried of is than a random connection could be created which uses
> the mapping of port 8080 of 192.168.1.1 and then the internal server 
> would not be available.
> But I guess this is not a problem since a connection has 4 parameters 
> src/dst ip/port.

Indeed, if some random outgoing connection to a remote host is mapped on
source port 8080 it is very unlikely to disrupt access to the internal
server, and it would only affect access from that remote host during a
short delay after the connection has been terminated (until the mapping
is deleted).

      reply	other threads:[~2009-09-23 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23  9:51 NAT overlaps with ports Kapetanakis Giannis
2009-09-23 10:46 ` Pascal Hambourg
2009-09-23 11:14   ` Kapetanakis Giannis
2009-09-23 13:45     ` Pascal Hambourg [this message]

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=4ABA2695.3030804@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox