allows you to use services provided by IPv6 hosts with IPv4-only
applications and vice-versa. It can bind to any of your IPv4 (default) or
IPv6 addresses and forward all data to IPv4 or IPv6 (default) host. For
will be enough to connect to IPv6 irc server with
If you don't wish to run
every time you want to show your :c001: or :dead: IPv6 address on IRC,
you can use
parameter, which makes
ask your client for specified password. Just run
and then type
If your IRC server requires you to send password, specify it with
parameter -- after successful proxy authentication
will send it to the server.
can also be used as a tunnel for all other combinations of IPv4 and IPv6
endpoints. If remote host doesn't have any IPv6 addresses,
will use the IPv4 one. In other cases, use
parameter which makes IPv4 address the preffered one. For IPv6-to-any tunnels
bind to IPv6 address.
Exit after first connection.
Preffer IPv4 endpoint if the machine has both address types.
Listen on IPv6 address (IPv4 is default).
Force tunneling even if remote host is not resolvable at the execution time.
Print hex dump of every packet received or sent (hu-huh, Beavis, he said
Change UID and GID after bind().
Act as an IRC proxy and require user to authenticate.
If you are using
as an IRC proxy and the IRC server requires you to send password, place
it right here.
Listen on specified address (IPv4, or IPv6 if
Limit simultaneous connections.
Write down pid to specified file.
Connect to the remote host using specified source address.
Binds to specified IPv6 addresses on basis of source IPv4 address. The file
contains one mapping per line with IPv4 source address and corresponding IPv6
address. Only listed hosts are allowed to connect. If you want to allow any
host, add mapping for
Terrible man page. Hex dump doesn't include IRC proxy authentication.
IRC proxy requires your client to send password first (don't worry ircii,
EPIC, BitchX, mIRC and many more will work). No logging except debug output.