All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Piszcz, Justin" <jpiszcz@servervault.com>
To: /dev/rob0 <rob0@gmx.co.uk>, Alexander Salmin <security.member@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: RE: IRC and ident with iptables
Date: Mon, 6 Jun 2005 07:00:14 -0400	[thread overview]
Message-ID: <F8B974E70BDE1745ABB27AF04788FA005BFE3A@mail1.dulles.sv.int> (raw)

Yes, oidentd.

-----Original Message-----
From: netfilter-bounces@lists.netfilter.org
[mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of /dev/rob0
Sent: Sunday, June 05, 2005 10:46 AM
To: Alexander Salmin
Cc: netfilter@lists.netfilter.org
Subject: Re: IRC and ident with iptables

Alexander Salmin wrote:
> diffrent ident. So, what I would like to know is if there is a way to
> make iptables recognize to whom it should portforward to, based of
> what internal ip that is connecting. Can it be done? If not, is there

That would be tricky, but perhaps possible using some extension of 
connection tracking ... whoever makes a new connection to an ircd is 
going to get the next ident query from that IP.

> any identd-server for Linux 2.6 that you know could do this?

This is how I'd go about it. I've seen numerous identd's listed on 
freshmeat which claim to be able to do this. It wouldn't be that 
complicated, I think: look up the connection in ip_conntrack, query the 
appropriate internal identd, give that reply to the external client.
-- 
     mail to this address is discarded unless "/dev/rob0"
     or "not-spam" is in Subject: header



             reply	other threads:[~2005-06-06 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 11:00 Piszcz, Justin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-05 14:23 IRC and ident with iptables Alexander Salmin
2005-06-05 14:46 ` /dev/rob0

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=F8B974E70BDE1745ABB27AF04788FA005BFE3A@mail1.dulles.sv.int \
    --to=jpiszcz@servervault.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=rob0@gmx.co.uk \
    --cc=security.member@gmail.com \
    /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.