From: Robby Workman <netfilter@rlworkman.net>
To: netfilter@lists.netfilter.org
Subject: Identd requests through firewall
Date: Sun, 13 Nov 2005 10:45:41 -0600 [thread overview]
Message-ID: <43776DB5.8050702@rlworkman.net> (raw)
Greetings...
IRC servers do an identd lookup when connecting to them, and although
most of them do not require a response, I'd like to at least have the
capability to return a response should I need to do so. I currently
have all incoming identd requests to the firewall rejected with TCP
RST, and this is adequate for the time being.
What I would like to do is forward the request to one of the boxes
behind the firewall (whichever one is attempting a connection with an
IRC server). I know how to forward them all to one of the individual
machines (say box 1), but this does not help if I'm using one of the
other boxes to connect.
In order for a connection to be considered "RELATED," an helper module
would have to exist. In the absence of such a module (the netfilter
IRC module does not do this iiuc), is there some other way to make
iptables "know" that box1 has initiated a connection to $IRCSERVER and
hence forward incoming identd requests from $IRCSERVER to box 1?
It shouldn't matter, but Firewall is Slackware 10.0 +patches, and most
boxes behind the firewall are Slackware -something...
Thanks in advance...
Network Diagram:
Dialup
Internet
|
|
------------
| (ppp0) |
| Firewall |
| (eth0) |
------------
|
|
------------
| |
| Switch |
| |
------------
|
|---------------------------
| | |
| | |
box 1 box 2 box 3
--
http://rlworkman.net
next reply other threads:[~2005-11-13 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 16:45 Robby Workman [this message]
2005-11-13 17:09 ` Identd requests through firewall /dev/rob0
2005-11-15 16:12 ` Robby Workman
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=43776DB5.8050702@rlworkman.net \
--to=netfilter@rlworkman.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox