1
0
mirror of https://code.semirocket.science/wrapsix synced 2024-12-05 20:21:03 +02:00
Go to file
2023-04-14 19:44:53 +03:00
m4 Fixed autoheader.h.in 2017-10-28 09:08:45 +02:00
src Fix calling perror too late 2018-06-24 10:03:46 +02:00
.gitignore Reordered .gitignore 2017-10-28 09:13:22 +02:00
AUTHORS Updated README, ChangeLog and AUTHORS 2013-06-17 16:29:21 +02:00
ChangeLog Updated README, ChangeLog and AUTHORS 2013-06-17 16:29:21 +02:00
configure.ac Bump version to 0.2.1.99 2017-11-06 11:12:59 +01:00
COPYING Forgot to change attached licence file 2013-07-19 15:05:16 +02:00
Doxyfile Basic skeleton -- autotools, readmes and doxygen 2009-12-01 18:44:26 +01:00
Makefile.am Properly distribute the example configuration file 2017-05-20 08:38:53 +02:00
NEWS NEWS for 0.2.1 2017-11-06 10:36:10 +01:00
README Update contact in README 2023-04-14 19:44:53 +03:00
wrapsix.conf Typos in config file 2017-10-21 10:27:43 +02:00

WrapSix
=======

About
-----
WrapSix is a fast NAT64 implementation. You also need a DNS64 server (e.g., BIND
or knot-resolver).

Installation
------------
For installation use standard ./configure && make && make install commands.

Configuration
-------------
WrapSix uses configuration file wrapsix.conf from configuration directory set in
"./configure" phase, which is by default /usr/local/etc. You can also specify
custom configuration file in runtime -- just pass its path as an argument:

# wrapsix ./wrapsix.conf

Pay attention to the IPv4 address. If you assign IP address that is already
controlled by your OS, TCP won't work (OS will terminate all connection
attempts).

Also, IPv4 is a little bit tricky. To ease both configuration and implementation
as much as possible, WrapSix leverages configuration for IPv4 already present in
the operating system. Therefore to work, IPv4 needs to be functional on the OS
level.

Running
-------
It can be run by `wrapsix` command as root.

Please note that traffic originating from the host WrapSix runs on cannot be
translated since WrapSix listens for incoming packets on the interface itself.
Therefore, you need some other host for testing it. If WrapSix doesn't seem to
be working, ensure (e.g., with tcpdump) that you have correctly configured
routing in your network.

Contact
-------
Author:   xHire
E-mail:   ~{^_^}~/ -at- semirocket.science
IRC:      channel #wrapsix on irc.libera.chat
Homepage: https://www.semirocket.science/projects/wrapsix/