From: "Radosław Łoboda" <p0wer@tl.krakow.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Detecting NAT
Date: Tue, 09 Apr 2002 06:21:25 +0000 [thread overview]
Message-ID: <marc-lartc-101833311210194@msgid-missing> (raw)
Hi.
Is 2.4 NAT easy to detect? I need to find which of my users redistribute
the link. Can default port range of NAT be changed? In 2.2 it seemed that
masquerade used higher ports (50000+ or something), but I read that in 2.4
this is lower.
--
##########################################
# | p0wer | #
# __ | GG#1877248 | #
# (oo) | p0wer@bojko.eu.org | #
# / \/ \ Go away or I will replace you #
# `V__V' with a very small shell script. #
##########################################
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-04-09 6:21 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=marc-lartc-101833311210194@msgid-missing \
--to=p0wer@tl.krakow.pl \
--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 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.