arti/wrapsix
1
0
Fork 0
mirror of https://code.semirocket.science/wrapsix synced 2024-09-19 15:01:06 +03:00
Code

Mentioned common configuration pitfalls in README

Browse Source
This commit is contained in:
xHire 2017-10-28 09:34:05 +02:00
parent e6ea4a27d9
commit cb286e7ae7
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README
View File

@ -18,10 +18,25 @@ custom configuration file in runtime -- just pass its path as an argument:
# wrapsix ./wrapsix.conf # 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 Running
------- -------
It can be run by `wrapsix` command as root. 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 Contact
------- -------
Author: xHire Author: xHire