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.
News:
-
02. Dec tircproxy 0.4.2 released.
- 23. Oct tircproxy 0.4.1 released.
- 21. Oct tircproxy 0.4.0 released, this web
page created.
- I will probably be getting credit for tircproxy at school, as a C.S.
project. This means I can spend more time on it. Yay!
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:
- Flexibility
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.
- Control
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
/etc/hosts.deny.
- Ident
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 reason I created tircproxy, was 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
this problem.
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.x stuff
older versions
other stuff
Bjarni R. Einarsson -
bre@mmedia.is