From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peggy Kam Subject: Re: iptables rules Date: Thu, 15 Sep 2005 11:37:09 -0400 Message-ID: <1126798629.4790.26.camel@ndspc131.p.n-dsi.com> References: <1123184190.21749.34.camel@ndspc131.p.n-dsi.com> <1123704837.3708.1.camel@ndspc131.p.n-dsi.com> <1126649450.4790.5.camel@ndspc131.p.n-dsi.com> <1126797736.4790.24.camel@ndspc131.p.n-dsi.com> <432992C0.2000404@mnemon.de> Reply-To: ppkam@n-dsi.com Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <432992C0.2000404@mnemon.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="iso-8859-1" To: =?ISO-8859-1?Q?J=F6rg?= Harmuth Cc: netfilter@lists.netfilter.org did the manpage gets changed recently? the iptables manpage that I see states that: --port [port[,port]] Match if the both the source and destination ports are equal to each other and to one of the given ports. On Thu, 2005-09-15 at 17:26 +0200, J=F6rg Harmuth wrote: > Peggy Kam wrote: > > Hi, > >=20 > > I have defined the following firewall rule in iptables: > >=20 > > iptables -I FORWARD -s 192.168.22.102 -d 192.168.1.112 -p tcp -m tcp = -m > > multiport --ports 22,23,24,25 -j ACCEPT > >=20 > > why were the packets able to get to 192.168.1.112 on port 22 when the > > packets does not even come from ports 22,23,24 or 25? >=20 > man iptables: >=20 > --ports [!] port[,port[,port:port...]] > Match if either the source or destination > ports are equal to one > of the given ports. >=20 > So, this is expected behaviour, provided that there are no other rules=20 > in the way. >=20 > HTH, >=20 > Joerg >=20 >=20