Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Sascha Reissner" <sascha.reissner@toxicnet.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>,
	netfilter mailing list <netfilter@lists.netfilter.org>
Subject: Re: curious about address specification and port specification
Date: Thu, 10 Oct 2002 06:20:18 +0200	[thread overview]
Message-ID: <000401c27014$5783fdc0$026410ac@honor> (raw)
In-Reply-To: Pine.LNX.4.44.0210091755001.17555-100000@localhost.localdomain

From: "Robert P. J. Day" <rpjday@mindspring.com>

> just the other day, i was at a local LUG meeting and a guy was giving a
> quick tutorial on iptables and displayed a sample rule file that contained
> the rule:
>
>   iptables -A FORWARD --destination 172.16.0.2 --destination-port 25  \
> --jump ACCEPT
>
>   doesn't this represent an example of what i was asking about?  a
> reference to a port with no reference to protocol.

well, a flipchart, whiteboard or video beamer presentation wont spit out any
error messages...

a real computer will do, and it will tell you that --destination-port is an
invalid parameter in that case..

because you dont specify any protocol ;)

iptables v1.2.6a: Unknown arg `--destination-port'
Try `iptables -h' or 'iptables --help' for more information.




  reply	other threads:[~2002-10-10  4:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 11:14 curious about address specification and port specification Robert P. J. Day
2002-10-09 21:13 ` Antony Stone
2002-10-09 21:57   ` Robert P. J. Day
2002-10-10  4:20     ` Sascha Reissner [this message]
2002-10-10  9:16       ` Robert P. J. Day
2002-10-10  6:30     ` Antony Stone

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='000401c27014$5783fdc0$026410ac@honor' \
    --to=sascha.reissner@toxicnet.de \
    --cc=netfilter@lists.netfilter.org \
    --cc=rpjday@mindspring.com \
    /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