From: Patrick Turley <pturley@rocksteady.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Port forwarding/translation control
Date: Mon, 03 May 2004 21:19:16 +0000 [thread overview]
Message-ID: <4096B754.3030708@rocksteady.com> (raw)
My Linux system is acting as a NAT'ing firewall, and I have some rules
for doing port forwarding/translation.
I was thinking about this the other day and I realized that there are
other parts of the system that consume ports. Specifically, NAT and
ephemeral port allocation.
It occurs to me that I could potentially have a conflict. If I set up a
rule to forward/translate a port, and the NAT'ing code picks the same
port for what it's doing, then there would be a big problem.
Eventually, I'll need to dynamically allocate ports of my own for
transitory port forwarding/translation. I need a way to set aside some
ports that I can use sure the NAT'ing code and the ephemeral port
allocation code won't try to use.
If anyone has anything illuminating to say on this point, I'd be very
grateful.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2004-05-03 21:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4096B754.3030708@rocksteady.com \
--to=pturley@rocksteady.com \
--cc=lartc@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