Skip to content
Tool for port forward & intranet proxy, just like lcx/ew, but better
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.
netio do a little change Mar 20, 2020
option Upgrade to v0.2.1; do some improvements, see CHANGELOG Mar 3, 2020
.editorconfig add editorconfig Feb 22, 2020
.gitignore Add auto releaser Feb 26, 2020
CHANGELOG Upgrade to v0.2.1; do some improvements, see CHANGELOG Mar 3, 2020
LICENSE Initial commit Feb 22, 2020
go.mod init commit Feb 22, 2020
main.go do a little change Mar 20, 2020


English | 中文

Tool for port forward & intranet proxy, just like lcx/ew, but better

Why write?

lcx and ew are awesome, but can be improved.

when I first used them, I can't remember these complicated parameters for a long time, such as tran, slave, rcsocks, sssocks.... The work mode is clear, why do they design parameters like this(especially ew's -l -d -e -f -g -h)

Besides, I think the net programming logic could be optimized.

For example, while running lcx -listen 8888 9999 command, client must connect to :8888 first, then :9999, in iox, there's no limit to the order in two ports. And while running lcx -slave 8888 9999 command, lcx will connect two hosts serially, but it's more efficient to connect in concurrent, as iox does.

What's more, iox provides traffic encryption feature. Actually, you can use iox as a simple ShadowSocks.

And iox also provides UDP traffic forward.

Of course, because iox is written in Go, the static-link-program is a little large, raw program is 2.2MB (800KB after UPX compression)


  • traffic encryption (optional)
  • humanized CLI option
  • logic optimization
  • UDP traffic forward


You can see, all params are uniform. -l/--local means listen on a local port; -r/--remote means connect to remote host

Two mode


Listen on and, forward traffic between 2 connections

./iox fwd -l 8888 -l 9999

for lcx:
./lcx -listen 8888 9999

Listen on, forward traffic to

./iox fwd -l 8888 -r

for lcx:
./lcx -tran 8888 9999

Connect and, forward between 2 connection

./iox fwd -r -r

for lcx:
./lcx -slave 8888 9999


Start Socks5 server on

./iox proxy -l 1080

for ew:
./ew -s ssocksd -l 1080

Start Socks5 server on be-controlled host, then forward to internet VPS

VPS forward to

You must use in pair, because it contains a simple protocol to control connecting back

./iox proxy -r
./iox proxy -l 9999 -l 1080       // notice, the two port are in order

for ew:
./ew -s rcsocks -l 1080 -e 9999
./ew -s rssocks -d -e 9999

Then connect intranet host

# proxychains.conf
# socks5://

$ proxychains rdesktop

enable encryption

For example, we forward 3389 port in intranet to our VPS

// be-controller host
./iox fwd -r -r * -k 656565

// our VPS
./iox fwd -l *8888 -l 33890 -k 656565

It's easy to understand: traffic between be-controlled host and our VPS:8888 will be encrypted, the pre-shared secret key is 'AAA', iox will use it to generate seed key and IV, then encrypt with AES-CTR

So, the * should be used in pairs

./iox fwd -l 1000 -r * -k 000102
./iox fwd -l *1001 -r * -k 000102
./iox fwd -l *1002 -r * -k 000102
./iox proxy -l *1003 -k 000102

$ curl -x socks5://

Using iox as a simple ShadowSocks

// ssserver
./iox proxy -l *9999 -k 000102

// sslocal
./iox fwd -l 1080 -r *VPS:9999 -k 000102

UDP forward

Only need to add CLI option -u

./iox fwd -l 53 -r * -k 000102 -u
./iox fwd -l *8888 -l *9999 -k 000102 -u
./iox fwd -r * -r -k 000102 -u

NOTICE: When you make a multistage connection, the Remote2Remote-UDP-mode must be started last, which is the No.3 command in above example

UDP forwarding may have behavior that is not as you expected. Actually, on GitHub now, there are only examples of forwarding a local listener to a remote host, so I can only implement them with my understanding

You can find why in the source code. If you have any ideas, PR / issue are welcomed


The MIT license

You can’t perform that action at this time.