Redirect traffic to SOCKS proxy with pcap.
pcap2socks is a proxy which redirect traffic to a SOCKS proxy with pcap written in Rust.
You can use pcap2socks GUI for a front-end interface.
pcap2socks is designed to accelerate games in game consoles.
If you want to build pcap2socks in Windows, you must meet all the three requirements described in libpnet.
Or a more general one using proxy ARP (recommended)
pcap2socks -s-p -d
-h, --help: Prints help information.
-v, --verbose: Prints verbose information (
-V, --version: Prints version information.
--force-associate-bind-address: Force to associate with the destination/replied bind address. pcap2socks will associate with the destination instead of the replied bind address in UDP ASSOCIATE if the replied bind address is in the private network by default. If this flag is set, pcap2socks will force to associate with the destination/replied bind address. If both flags are set, the
--force-associate-destinationwill take effect.
-i, --interface: Interface for listening.
--mtu: MTU. Generally, pcap2socks will automatically obtain the MTU, but you can also override by setting this option. The MTU is set in the traffic from local to the source.
-P, --preset: Preset. You can use preset source and publish of game accelerators in the market. Available values are
tencentfor Tencent Online Game Accelerator and
uufor Netease UU Game Accelerator.
-s, --source: Source. The source can be a single IPv4 address like
192.168.1.2, or an IPv4 CIDR network like
-p, --publish: ARP publishing address. If this option is set, pcap2socks will reply ARP request as it owns the specified address which is not on the network, also called proxy ARP.
-d, --destination: Destination, default as
--username: Username. This value should be set only when the SOCKS5 server requires the username/password authentication.
--password: Password. This value should be set only when the SOCKS5 server requires the username/password authentication.
// Linux sysctl -w net.ipv4.ip_forward=0
// macOS sysctl -w net.inet.ip.forwarding=0
// Linux setcap cap_net_raw+ep path_to_pcap2socks
IPv6 is not supported yet.
Because only SOCKS5 can forward UDP traffic, pcap2socks only support SOCKS5 at this point. A version with SOCKS4 support without redirecting UDP traffic will release in the future.
Applications like VMWare Workstation on Windows may implement their own IP forwarding and forward packets which should be handled by pcap2socks, resulting in abnormal operations in pcap2socks.
The traffic flow control was not implemented in pcap2socks currently. On certain occasions, bandwidth may be heavily occupied by one side of a connection, causing the other side of the connection and other connections to be unable to transmit data normally.
pcap2socks is licensed under the MIT License.