All of lore.kernel.org
 help / color / mirror / Atom feed
From: mike bramm <mike.bramm@bomberjacketproductions.com>
To: netfilter@lists.netfilter.org
Subject: SNAT & Squence Numbers
Date: Mon, 11 Nov 2002 11:23:56 -0600	[thread overview]
Message-ID: <3DCFE7AC.9867DF43@bomberjacketproductions.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hi,
    I'm a Router/PIX guy that is just getting into the Linux/IPTables
scene. I've read the man pages and searched the web for information on
IPTables. And I'm not able to find answers to some of my questions.
Maybe you can help?

   * If SNAT is configured for many to one (PAT), then I would presume
     that the connections are tracked by sequence numbers. Are the
     sequence numbers picked randomly, like the PIX? And is there a
     range in with they are picked from? What mod does this?

   * A syntax question. I've looked at alot of syntax examples and I've
     noticed one character that I can't seem to match up with any of the
     tutorials or man
     pages.
     $IPTABLES -A INPUT $WAN_IFACE \ -j DROP   What the heck is "\"? It
     looks like it would be used to separate the match and the target,
     but is not really necessary. Is this just a personal preference or
     is it needed?

Thanks for your time. I wish I had heard about IPTables a year ago.
Anthony Stone does have cool sayings.
mike


[-- Attachment #2: Type: text/html, Size: 1752 bytes --]

             reply	other threads:[~2002-11-11 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 17:23 mike bramm [this message]
2002-11-12  8:22 ` SNAT & Squence Numbers Dax Kelson
     [not found] <FD8F124A387AD6119F7900A0D218B321487DB8@hslex01.hsl-brabantzuid.nl>
2002-11-12  8:51 ` Rob Sterenborg

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=3DCFE7AC.9867DF43@bomberjacketproductions.com \
    --to=mike.bramm@bomberjacketproductions.com \
    --cc=netfilter@lists.netfilter.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.