ezbounce v2.0 DCC Proxying and Other Features
---------------------------------------------------------
Last Updated: $Date: 2008-04-09 23:06:07 -0500 (Wed, 09 Apr 2008) $


1. Introduction

In addition to basic IRC proxying, ezbounce supports more advanced features
such as DCC proxying and DCC filtering.  This document describes the setup and
operation of these features.


2. Features

This document will describe DCC proxying and a related feature, DCC filtering.


3. DCC Proxying

3.1 Description

ezbounce supports DCC proxying.  This is especially useful for people
behind firewalls or on a LAN -- but note that ezbounce must be running on 
a machine that has both global Internet access *and* local LAN access.

It's completely transparent, meaning the client can just use the regular
/DCC commands to send and receive DCC chats and file transfers.  No special
settings or commands are required on the client software.


3.2 Setup

Setting up DCC proxying is easy.  When defining users in the ezbounce
configuration file, you just need to set a couple options to allow them to use 
DCC proxying.

Two user configuration options control DCC proxying:

	user "james" {
		...
		# permit full DCC proxying
		set enable-outgoing-dcc-proxying 1
		set enable-incoming-dcc-proxying 1
	}

This allows this user to use the DCC proxying features.  Note that "outgoing" in
this case refers to DCCs originating from the ezbounce user, and "incoming" refers to 
DCCs originating from another user on IRC.


3.3 Usage

When a user is permitted to use DCC proxying, the default behavior is to not
proxy unless requested.  There are two ways of requesting that DCCs get
proxied.

The user can set the "proxy-dcc-in" or "proxy-dcc-out" preferences, which will
cause incoming or outgoing DCCs automatically get proxied.  Here is an
example:

	/ezb set proxy-dcc-in  on
	/ezb set proxy-dcc-out on

This enables automatic DCC proxying for both directions.

The other way of proxying DCCs is to use the DCC filtering feature.  It is
described in detail below, in the "DCC Filtering" section of this document.
This allows the user more control in selecting which DCCs to proxy and which 
ones to handle normally or ignore.


3.4 Notes

A few things to note about DCC proxying:

	- mIRC DCC Resume is not yet supported.
	- DCC VIDEO/VOICE connections as used by some Windows clients should work.  
	- All DCC sessions are handled separately from the user's IRC connection and 
	  ezbounce will keep them alive if the user disconnects from the proxy, until 
	  the user's end closes the DCC connection.
  
In addition, Those with restrictive network settings can restrict the ports used by 
ezbounce DCC proxying to a specific range.  The option for this is:
	
	set dcc-listen-port-range <ports>
	
where ports can be any number or series of numbers separated by
commas, and where ranges of numbers can be indicated by a dash. 
The value must also be enclosed in quotes.    

    Examples values:

       "7000,7005,8225,9000-9100"
       "2000-2300,4860"
       "6918"
       "5700-5710"


4 DCC Filtering

4.1 Description

With DCC Filtering, ezbounce can intercept DCC requests to and from your client 
and let you do useful things with them.

For example, say you want to receive a large file from someone but have a slow 
connection.  And say that you're connected through ezbounce and it has a much 
faster connection.

With a single command, you can have ezbounce receive the DCC for you
and store it in the Virtual File System (VFS), where you can access it later. 


4.2 Setup

TODO: expand this section


4.3 Usage

DCC filtering can be enabled by setting the user preference "filter-dccs":

	/ezb set filter-dccs on

Now, whenever an incoming or outgoing DCC offer goes through ezbounce, it will
intercept it and notify you.  You may then use the ezbounce "DCC" command to
list, accept, proxy, or ignore these DCC offers.  An example:

	/ezb dcc list

TODO: Expand this section


4.4 Notes

TODO: Expand this section


5. Other Notes