From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Identd requests through firewall
Date: Sun, 13 Nov 2005 11:09:05 -0600 [thread overview]
Message-ID: <200511131109.06283.rob0@gmx.co.uk> (raw)
In-Reply-To: <43776DB5.8050702@rlworkman.net>
On Sunday 2005-November-13 10:45, Robby Workman wrote:
> 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.
Perhaps an easier solution than a patch of the IRC helper driver to
handle auth requests: run midentd on your firewall machine.
http://freshmeat.net/projects/midentd/
Haven't tried it, myself. You would need to ACCEPT auth at the firewall
(INPUT chain). Probably the only way around that is the aforementioned
patch.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-11-13 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 16:45 Identd requests through firewall Robby Workman
2005-11-13 17:09 ` /dev/rob0 [this message]
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=200511131109.06283.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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