The tircproxy home page
Welcome to the tircproxy home page. On this page you can find links to the
most recent versions of tircproxy, as well as other related stuff. The
- 2004 Nothing Has Happened... I don't think Lars is active?
- 20. Feb, 2001 The project has a new
maintainer: Lars Erik Jordet (lejorded (at) online.no).
- 01. Feb, 2001 Uploaded work-in-progress
for new maintainer.
04. May, 2000 tircproxy 0.4.5 released.
- 09. Apr, 2000 Created a
mailing list. I'm preparing 0.4.5 for release,
watch this space!
- 01. Mar, 2000 Moving and updating web site.
- 13. Jan, 1999 tircproxy 0.4.3 released.
- 02. Dec, 1998 tircproxy 0.4.2 released.
- 23. Oct, 1998 tircproxy 0.4.1 released.
- 21. Oct, 1998 tircproxy 0.4.0 released,
this web page created.
What is tircproxy?
Tircproxy is a program designed to help IRC users who are not directly
connected to the internet, but are behind a firewall based on Linux or some
other Unix variant.
For small firewall installations, tircproxy essentially solves the same
problems as the "ip_masq_irc" modules for Linux, it makes DCC CHAT and DCC
SEND work as if the firewall wasn't there. But if you have alot of users
behind your firewall, don't want to use IP masquerading for some reason, or
just want more control and better logging of IRC traffic, then the following
features could come in handy:
Tircproxy can run in standalone mode, or from inetd. It can
cooperate with the Linux kernel or the IPF package for transparent
proxying, or it can run in dedicated mode, directing all users to
the same IRC server.
The sysadmin can easily allow DCC CHAT, but ban DCC SEND. The admin
can also selectively ban transmission of certain files, such as the
script.ini trojan. Access to the proxy can be controlled on a
user, network or domain basis from /etc/hosts.allow and
Tircproxy can cooperate with the ident daemon to correctly identify
masqueraded users, even if the ident daemon has no support for IP
masquerading. Even better, if you are running a compatible version
of oidentd, then you can achieve the same results without
running the proxy with root permissions.
The original reasons I created tircproxy, were problems I had at work using
Linux and IP masquerading to firewall a large number of dial-in users. The
Linux IP masquerading code supports IRC and DCC - up to a point. I soon
discovered that users behind the same firewall couldn't communicate with
each other via DCC. The first versions of tircproxy were written to solve
Perhaps this problem will also be solved by the new firewalling code (ip
chains) in Linux 2.2, but I didn't want to wait - and neither did my users.
tircproxy 0.4.5 stuff
Check the UDB page to find the stuff you'll need to
use the current shared-memory based ident support. You'll need at least the
UDB library itself, and a compatible ident daemon.
I've created a mailing list for discussions amongst users and/or developers
of tircproxy. To join, send an empty message to firstname.lastname@example.org
. The list software
is one of my other
projects, please bear with me as it evolves.
Check out the list's archives.
Depraciated filesystem based ident support: