From: "Dharmendra.T" <dharmu@nsecure.net>
To: Atsushi Nakagawa <atnak@chejz.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Liaise with port forwarding proxies?
Date: 08 Sep 2003 11:38:41 +0530 [thread overview]
Message-ID: <1063001331.831.35.camel@india.nsecure.net> (raw)
In-Reply-To: <20030906003513.A37B.ATNAK@chejz.com>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
On Fri, 2003-09-05 at 20:35, Atsushi Nakagawa wrote:
"Dharmendra.T" <dharmu@nsecure.net> wrote:
> Can you say more clearly what you are trying?
I have a linux server with services and an iptables configuration set to
discard any NEW incoming packets that aren't for these services. I do
this based on protocol and port. (e.g. Accept: TCP/80, TCP/21)
I want to add a SOCKS5 server (Dante) to the list of services. The
problem with this is that this server can listen to any arbitary port
above 1024 for port tunneling, but I don't want to automatically allow
all ports > 1024 in iptables.
I'm wondering if there is a way for iptables to determine which ports
are in use by the SOCKS5 server and selectively allow those.
You can allow related packets.
Regards,
--
Atsushi Nakagawa
<atnak@chejz.com>
Changes are made when there is inconvenience.
--
Regards
Dharmendra.T
dharmu@nsecure.net
This message is intended for the addressee only. It may contain
privileged or Confidential information. If you have received this
message in error,please notify the sender and destroy the message
immediately.Unauthorised use or reproduction of this message is strictly
prohibited.
[-- Attachment #2: Type: text/html, Size: 3067 bytes --]
prev parent reply other threads:[~2003-09-08 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 10:13 Liaise with port forwarding proxies? Atsushi Nakagawa
2003-09-05 11:52 ` Dharmendra.T
2003-09-05 15:05 ` Atsushi Nakagawa
2003-09-08 6:08 ` Dharmendra.T [this message]
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=1063001331.831.35.camel@india.nsecure.net \
--to=dharmu@nsecure.net \
--cc=atnak@chejz.com \
--cc=netfilter@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.