All of lore.kernel.org
 help / color / mirror / Atom feed
From: samba <samba@embeddedinfotech.com>
To: netfilter-devel@lists.netfilter.org
Subject: port Triggering.
Date: Mon, 19 Dec 2005 14:17:54 +0530	[thread overview]
Message-ID: <43A673BA.5000009@embeddedinfotech.com> (raw)

Hi all,
I have been trying to configure port triggering using iptables. Port 
triggering allows opening  of  inbound port for some interval of time 
based on some outbound traffic that originated from internal LAN. This 
is similar to how ftp is handled by ip_conntrack_ftp module. With port 
triggering, there will be no need to parse the control packet for data 
ports that needs to be opened, since the user already specifies the 
ports on which the ftp server will open connection for data.

Is such a feature supported by iptables and the netfilter framework, 
which enables/triggers some user defined  incomming ports based on the 
traffic going through some outgoing ports(user defined) ?

I have seen some discussion regarding this in the archives (June 2003). 
But could not get any conclusions. Please help.

Thanks in advance for any help
-samba

             reply	other threads:[~2005-12-19  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19  8:47 samba [this message]
2005-12-24 10:57 Port Triggering samba
2005-12-26  1:48 ` ludi
     [not found] <CAFs+hh5aHv_Xy2H2g9Bgsa-BYNY-uvE442Ws37vYtF484nZanQ@mail.gmail.com>
     [not found] ` <20180309120324.GB19924@breakpoint.cc>
     [not found]   ` <CAFs+hh42HuoQh4Js7yyopVqofD-6YXkOVvrx=XjYm43igaaRLg@mail.gmail.com>
     [not found]     ` <20180312112547.GA8844@breakpoint.cc>
     [not found]       ` <CAFs+hh61B0+qx3uyr2TwKWCNKqPn5YgN33RjmOMafTESYsmyjQ@mail.gmail.com>
     [not found]         ` <20180312155357.GC8844@breakpoint.cc>
2019-05-02  6:44           ` Port triggering Stéphane Veyret
2019-05-02  7:44             ` Florian Westphal

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=43A673BA.5000009@embeddedinfotech.com \
    --to=samba@embeddedinfotech.com \
    --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.