SS-NAT(1)
π SS-NAT(1) β the glow-up β¨
okay so real talk, this is a page from the Shadowsocks-libev Manual, and bestie, it's about to make so much sense π«Ά
πΈ NAME πΈ
ss-nat β the little helper script that sets up your NAT rules for transparent proxy. she's the backstage crew making the whole show work, no cap π
π SYNOPSIS π
ss-nat [-ouUfh] [-s <server_ip>] [-S <server_ip>] [-l <local_port>] [-L
<local_port>] [-i <ip_list_file>] [-a <lan_ips>] [-b <wan_ips>] [-w
<wan_ips>] [-e <extra_options>]
π¦ DESCRIPTION π¦
So. Shadowsocks-libev is a lightweight and secure socks5 proxy β icon behavior only π. It's a port of the original shadowsocks created by clowwindy, and yes we stan the origin story. Shadowsocks-libev is written in pure C and takes advantage of libev to achieve both high performance and low resource consumption. literally the "works hard, barely eats" main character energy π₯
ss-nat(1) sets up NAT rules for ss-redir(1) to provide traffic redirection. that's the whole job, and she does it slayfully π
β οΈ heads up bestie: she requires netfilter's NAT module and iptables(8). no iptables, no vibes.
for more info, check out shadowsocks-libev(8) and the EXAMPLE section down below β¬οΈ
β¨ OPTIONS β¨
-s<server_ip>β the IP address of your shadowsocks remote server π-l<local_port>β the port number of your shadowsocks local server π-S<server_ip>β the IP address of your shadowsocks remote UDP server π°οΈ-L<local_port>β the port number of your shadowsocks local UDP server π‘-i<ip_list_file>β a file whose content is the bypassed ip list (basically the VIP guest list that skips the proxy π)-a<lan_ips>β LAN IP of access control; heads up, she needs a prefix to define the access control mode π-b<wan_ips>β WAN IP that will be bypassed π«-w<wan_ips>β WAN IP that will be forwarded β‘οΈ-e<extra_options>β extra options foriptablesπ§ͺ-oβ apply the rules to the OUTPUT chain π€-uβ enable udprelay mode; TPROXY is required β οΈ (fr fr, don't skip that part)-Uβ enable udprelay mode, using different IP and ports for TCP and UDP π-fβ flush the rules π§Ή-hβ show this help message and exit π
π EXAMPLE π
ss-nat requires iptables(8). here's the moment you've been waiting for, bestie:
# Enable NAT rules for shadowsocks,
# with both TCP and UDP redirection enabled,
# and applied for both PREROUTING and OUTPUT chains
root@Wrt:~# ss-nat -s 192.168.1.100 -l 1080 -u -o
# Disable and flush all NAT rules for shadowsocks
root@Wrt:~# ss-nat -f
first one? she's serving π₯ second one? the clean-up era π§Όβ¨
π SEE ALSO π
ss-local(1), ss-server(1), ss-tunnel(1), ss-manager(1), shadowsocks-libev(8), iptables(8), /etc/shadowsocks-libev/config.json
go read the whole fam, iykyk ππ
okay that's the whole page!! π this was Shadowsocks-libev 3.3.6, dated 10/11/2026 β so go set up those NAT rules and be the main character of your own network, periodt ππ¦β¨
π¦ where this page comes from
- opensuse-leap 16.0: shadowsocks-libev 3.3.6-bp160.3.1 Β· GPL-3.0-or-later
- opensuse-leap 16.0: shadowsocks-libev 3.3.6-bp160.3.1 Β· GPL-3.0-or-later
- opensuse-leap 16.0: shadowsocks-libev 3.3.6-bp160.3.1 Β· GPL-3.0-or-later
- opensuse-leap 16.0: shadowsocks-libev 3.3.6-bp160.3.1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms