Re: mport trouble

[Robert Vangel <vangelr@rfgt.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bastian Blank wrote:
> On Wed, Aug 03, 2005 at 06:16:24PM -0600, curby . wrote:
> 
> Get a name.
> 
> 
>>Ok, that makes perfect sense.  We haven't told it which port, but at
>>least our installation supports mport.
>>
>>$ iptables -A FORWARD -p tcp -m mport --dports 22 -j  ACCEPT
>>iptables: No chain/target/match by that name
>>$
> 
> 
> Where did you found the information that mport supports --dports? The
> iptables manpage specifies --destination-ports since many years.
> 
> Bastian
> 

Same message.

Plus, out of the manpage (sorry for wrapping)

   mport
       This module matches a set of source or destination ports.  Up to
15 ports can be specified.  It can only be used in conjunction with -p
       tcp or -p udp.

       --source-ports port[,port[,port...]]
              Match if the source port is one of the given ports.  The
flag --sports is a convenient alias for this option.

       --destination-ports port[,port[,port...]]
              Match if the destination port is one of the given ports.
The flag --dports is a convenient alias for this option.

       --ports port[,port[,port...]]
              Match if the both the source and destination ports are
equal to each other and to one of the given ports.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFC8b8KV63eDkW7v4cRApC5AJ0f1ZWgieMRi5j8INMeLbdeumDjTQCeJiuD
Zvq9ejnKSAA1rwx4oWP3OlA=
=2QfH
-----END PGP SIGNATURE-----