From: Arnt Karlsen <arnt@c2i.net>
To: netfilter_user <netfilter_user@o2.pl>
Cc: netfilter@lists.netfilter.org
Subject: Re: Re[2]: access to server
Date: Wed, 30 Apr 2003 04:47:45 +0200 [thread overview]
Message-ID: <20030430044745.621e715a.arnt@c2i.net> (raw)
In-Reply-To: <1246491441.20030430033812@o2.pl>
On Wed, 30 Apr 2003 03:38:12 +0200,
netfilter_user <netfilter_user@o2.pl> wrote in message
<1246491441.20030430033812@o2.pl>:
> Hello Arnt,
>
> Wednesday, April 30, 2003, 3:10:30 AM, you wrote:
>
> AK> On Wed, 30 Apr 2003 00:49:31 +0200,
> AK> netfilter_user <netfilter_user@o2.pl> wrote in message
> AK> <5436369716.20030430004931@o2.pl>:
>
> >> Rule: "iptables -A FORWARD -i eth1 -p udp -m --multioport --dport
> AK> /\
> AK> ..is " -m --multioport " a valid match in iptables, or a correct
> AK> quote of your attempt to write ' -m --multiport ' ?
>
> damn my wrong...it should looks like this:
> iptables -A FORWARD -i eth1 -p udp -m --multioport --dport 23073,23083
> -j ACCEPT /\
||
..lets try again: I don't find "-m --multioport" _anywhere_
in the docs, so, if you _actually_ try '-m --multioport' in
your rule set, it _should_ fail, then you'll wanna try
'-m --multiport', without your extra "o". ;-)
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next prev parent reply other threads:[~2003-04-30 2:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 22:49 access to server netfilter_user
2003-04-30 1:10 ` Arnt Karlsen
2003-04-30 1:38 ` Re[2]: " netfilter_user
2003-04-30 2:47 ` Arnt Karlsen [this message]
2003-04-30 13:32 ` Re[4]: " netfilter_user
2003-04-30 14:59 ` Alistair Tonner
2003-04-30 17:00 ` Re[6]: " netfilter_user
2003-04-30 17:48 ` Alistair Tonner
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=20030430044745.621e715a.arnt@c2i.net \
--to=arnt@c2i.net \
--cc=netfilter@lists.netfilter.org \
--cc=netfilter_user@o2.pl \
/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