Read the POD documentation:

    perldoc trans-proxy-tor
    perldoc dns-proxy-tor

Example configurations for pf and iptables are included in filter-examples.

1. OpenBSD notes - trans-proxy-tor

    Requiring net/pfvar.ph on i386 OpenBSD 3.8 and 3.9 fails without this patch:

        --- /usr/libdata/perl5/site_perl/i386-openbsd/sys/param.ph
        +++ /usr/libdata/perl5/site_perl/i386-openbsd/sys/param.ph
        @@ -124,6 +124,6 @@
          unless(defined(&NODEV)) {
        -    sub NODEV () {     ( &dev_t)(-1);}
        +    sub NODEV () {     &dev_t(-1);}
          }
          unless(defined(&NETDEV)) {
        -    sub NETDEV () {    ( &dev_t)(-2);}
        +    sub NETDEV () {    &dev_t(-2);}
          }

2. NetBSD notes - trans-proxy-tor

    NetBSD comes with an old version of libevent, so install libevent-1.1a from
    pkgsrc first. Then compile Event::Lib with the new version:

        perl Makefile.PL INC=-I/usr/pkg/include LIBS="-L/usr/pkg/lib -levent"
        make && make test && make install

    You'll also need to install p5-perl-headers from pkgsrc to get the headers
    required for trans-proxy-tor.

3. BSD notes - trans-proxy-tor

    If you want to redirect locally generated traffic into trans-proxy-tor with
    pf, you'll need to reroute outgoing traffic to a second loopback interface.
    rdr rules don't apply to locally generated traffic otherwise. This isn't a
    recommended procedure, so it may lead to kernel panics or other instability.
    I'd love to know if there's a better way.

4. Windows notes - dns-proxy-tor

    To install dns-proxy-tor as a Windows service, invoke it from the cmd.exe
    shell:

        dns-proxy-tor.exe -install

    Once it's installed as a service, it should start when Windows boots. To
    remove it, change -install to -uninstall:

        dns-proxy-tor.exe -uninstall

    Remember to set your DNS server to 127.0.0.1 and run Tor with ControlPort
    set to 9051 and SocksPort set to 9050.

    By default, the Windows service resolves names using Tor's SOCKS resolve
    extension. This way programs connecting without Tor will get routable
    addresses. However, this method is slower for names Tor hasn't already
    cached. It may also make it easier for programs to bypass Tor. If you
    want all programs to connect through Tor, and you don't mind non-Tor
    connections failing, change a registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dns-proxy-tor\ImagePath

    After removing '-s 127.0.0.1:9050' from the end of the key all resolves will
    go through the MAPADDRESS controller command.

    The Windows binary for dns-proxy-tor-windows-service was created with PAR,
    and can be redistributed without restriction under the Artistic License.
