Releases: dndx/phantun
v0.6.0
v0.5.0
New option --handshake-packet
that allows additional packet to be sent to the other end after TCP connection establishment. Please run Phantun binary with -h
to see detailed usage.
v0.4.2
This release adds full IPv6 support to Phantun and fake-tcp
. Plantun is not officially end-to-end IPv6 compatible!
Configuration for IPv6 requires additional sysctl
and nftables
change, please check the updated README.md
.
For existing IPv4 users, nothing is expected to break.
Note for users upgrading from v0.4.1
and has IPv6 enabled, the link local address used by Phantun by default has changed and is now RFC compliant. Please see README.md
or run with the -h
option to see the new address. You may need to change the firewall DNAT address accordingly. IPv4 users can ignore this.
v0.4.1
Note: this version contains a slight problem where site-local address used by Phantun by default has been deprecated. Use v0.4.1 instead for IPv6 usage (no issue with IPv4)
This release adds full IPv6 support to Phantun and fake-tcp
. Plantun is not officially end-to-end IPv6 compatible!
Configuration for IPv6 requires additional sysctl
and nftables
change, please check the updated README.md
.
For existing IPv4 users, nothing is expected to break.
v0.3.2
v0.3.1
This release includes fixes to RST
packet generation to avoid nf_contrack
reporting invalid packets.
See https://github.com/dndx/phantun/releases/tag/v0.3.0 for performance improvements in the v0.3.x
series.
v0.3.0
- Bumped the dependency to the latest.
- Contains an optimization #41 which utilizes
SO_REUSEPORT
to create multiple UDP sockets for the same connection and spawns Tokio tasks for each available CPU core.- According to my benchmark, this improved throughput on multi-core systems such as Raspberry Pi by 20%-30%.
v0.2.5
Bumped dependencies clap
to v3.0.0
which contains a visually more appealing usage and bumped tokio
to v1.15.0
.
v0.2.4
Bumped dependencies clap
to v2.34.0
and tokio
to v1.14.0
.
v0.2.3
This release adds support for using host name in --remote
argument for both server and client. It also improved the efficiency of forwarding path by not cloning syncing primitives for each packet.