Re: ip_masq_irc and ircii-EPIC4

Bjarni R. Einarsson (bre@margmidlun.is)
Fri, 9 Oct 1998 11:26:15 +0000

> From: Matthias Andree <mandree@dosis.uni-dortmund.de>
> Date: Fri, 9 Oct 1998 02:01:11 +0200
> Subject:
>
> On Sun, Oct 04, 1998 at 05:52:13PM -0400, Ben Winslow wrote:
> > ip_masq_irc and ircii-EPIC4 don't get along with each other
> > the reason for this is that EPIC sends a file checksum in the DCC SEND
> > request as the last parm. Its an 8 digit hex number after the port. I
> > looked at the ip_masq_irc source, and frankly, it scared me.. I don't know
> > where to add it, so I'm posting here.
>
> Oliver Wagner has made available IP Masquerading patches for AmIRC
> somewhere in the AmFTP path. I'm not sure if this patch addresses your
> problem, but you can check ftp://ftp.vapor.com/pub/amirc/, relevant
> files are ip_masq.readme and ip_masq_irc.c.gz

[shameless plug]

This (the whole DCC-through-firewalls problem) has been solved in
user-space, by my transparent IRC proxy. The proxy takes advantage of the
kernels transparent proxy feature (or the IPF capability to do the same
thing on other platforms). DCC with EPIC should work, as the proxy merely
drops the last parameter, so the recipient thinks he is recieving a
perfectly normal DCC from a "standard" client.

Check http://www.mmedia.is/~bre/tircproxy/ if you are interested.

I am also quite interested in feedback from people using weird clients with
weird DCC "addons"..

-- 
Bjarni R. Einarsson
 bre@margmidlun.is               [ THIS SPACE INTENTIONALLY LEFT BLANK ]
 http://www.mmedia.is/~bre
 Juggler@IRCnet               NSA tease #4: Fusion. Uranium. Fnord.  Bomb.
 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/