Antinat description
A flexible SOCKS server and client library for writing proxy-based applications

Antinat supports SOCKS 4, SOCKS 5, SOCKS 4a, authentication, XML firewalling, CHAP, sWin32, server chaining, and UDP. Antinat also contains very experimental IPv6 support.

SOCKS can be used to overcome some limitations of NAT, including facilites for allowing connectbacks and server-side DNS.

Antinat aims to be fully standards compliant, feature rich, and have a solid API for writing standards-compliant client applications.

Connections are filtered by applying XML rules, which allow for very fine-grained control.

You can filter out on the basis of addresses, ports, users, socks version, the operation requested, how the user was authenticated, and where user credentials came from.

Here are some key features of "Antinat":

· XML firewalling language; filter based on:
· Authentication scheme
· Authentication source
· Source and/or destination address type
· Source and/or destination address
· Source and/or destination port
· Operation requested (connect, bind, udp)
· Username
· Socks version
· Ability to chain to upstream servers, including changing versions and credentials
· Client or server-side hostname resolution, in both SOCKS4 and SOCKS5
· CONNECT, BIND and UDP support (UDP SOCKS5 only.)
· Authentication via Username-Password and CHAP (SOCKS5 only.)
· Authenticate to configuration files, or the local machine's credentials
· Log connections, and generate summaries for hosts and/or users
· Client library for developing proxy-aware applications.