All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Kirk Reiser <kirk@braille.uwo.ca>
Cc: lartc@mailman.ds9a.nl,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [LARTC] Possible bug with multiport?
Date: Wed, 15 Mar 2006 17:12:26 +0000	[thread overview]
Message-ID: <44184AFA.5020109@trash.net> (raw)
In-Reply-To: <x7d5go53rf.fsf@speech.braille.uwo.ca>

CCed netfilter-devel.

Kirk Reiser wrote:
> Hi Folks:  I am either using the multiport of the -m or --match option
> of iptables in correctly or there is a bug with it.  Is anyone else
> using it with no problem?  This is the way I am trying to use it:
> 
> my_ports!,25,80 
> iptables -t nat -A PREROUTING -i $wan_addr -p tcp -m multiport
> --dports $my_ports -j DNAT --to $my_internal_address
> 
> I have used this in the past successfully but that was a few years
> ago.  I get no errors or warnings it just ignors the ports.  The
> multiport invokation shows up in an iptables -t nat -L -v however.
> The packet and byte counts never get incremented either from zero.
> 
> Any pointers would sure be helpful, having to include a line for every
> port check seems wasteful.

Please post your kernel version, your iptables version and the
output of iptables -vxnL.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Kirk Reiser <kirk@braille.uwo.ca>
Cc: lartc@mailman.ds9a.nl,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: Possible bug with multiport?
Date: Wed, 15 Mar 2006 18:12:26 +0100	[thread overview]
Message-ID: <44184AFA.5020109@trash.net> (raw)
In-Reply-To: <x7d5go53rf.fsf@speech.braille.uwo.ca>

CCed netfilter-devel.

Kirk Reiser wrote:
> Hi Folks:  I am either using the multiport of the -m or --match option
> of iptables in correctly or there is a bug with it.  Is anyone else
> using it with no problem?  This is the way I am trying to use it:
> 
> my_ports=21,25,80 
> iptables -t nat -A PREROUTING -i $wan_addr -p tcp -m multiport
> --dports $my_ports -j DNAT --to $my_internal_address
> 
> I have used this in the past successfully but that was a few years
> ago.  I get no errors or warnings it just ignors the ports.  The
> multiport invokation shows up in an iptables -t nat -L -v however.
> The packet and byte counts never get incremented either from zero.
> 
> Any pointers would sure be helpful, having to include a line for every
> port check seems wasteful.

Please post your kernel version, your iptables version and the
output of iptables -vxnL.

  reply	other threads:[~2006-03-15 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 11:47 [LARTC] Possible bug with multiport? Kirk Reiser
2006-03-15 17:12 ` Patrick McHardy [this message]
2006-03-15 17:12   ` Patrick McHardy
2006-03-15 19:03   ` [LARTC] " Kirk Reiser
2006-03-15 19:03     ` Kirk Reiser
2006-03-15 23:41     ` [LARTC] " Patrick McHardy
2006-03-15 23:41       ` Patrick McHardy
2006-03-16 12:24       ` [LARTC] " Kirk Reiser
2006-03-16 12:24         ` Kirk Reiser
2006-03-15 17:32 ` [LARTC] " William L. Thomson Jr.

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=44184AFA.5020109@trash.net \
    --to=kaber@trash.net \
    --cc=kirk@braille.uwo.ca \
    --cc=lartc@mailman.ds9a.nl \
    --cc=netfilter-devel@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.