Calling for Linux Testers for ProxyBridge (Pre-Release) #65

2026-02-03T09:46:07Z

InterceptSuite Admin
Feb 3, 2026

I am currently building ProxyBridge for Linux and looking for community members who are willing to help test the application before the official release.

🎯 Goal

The goal is to validate ProxyBridge across:

Different Linux distributions
Different use cases and workflows
Real-world environments before public release

🐧 Target Distributions

I am especially interested in testing on:

Debian-based distros (Ubuntu, Debian, Linux Mint, etc.)
Fedora / RHEL-based distros
Any other Linux distributions you actively use

🧪 Key Use Cases to Test

Testers are encouraged to validate ProxyBridge under different real-world scenarios, including:

Proxy rule testing
- Different rule combinations
- Per-app and global proxy rules
- Rule enable/disable behavior
Proxy configuration testing
- SOCKS5 proxy
- HTTP proxy
- Mixed proxy configurations
Protocol coverage
- TCP connections
- UDP connections
Performance & resource usage
- Internet/network speed impact with:
  - ProxyBridge running with no proxy rules
  - Proxy rules enabled
  - Browser traffic (Chrome / other browsers) routed through proxy
- Compare baseline vs proxied internet speed
System resource monitoring
- CPU usage during normal traffic
- Memory usage during normal traffic
- CPU and memory behavior under high or heavy traffic routed via proxy

The goal is to ensure that, similar to the Windows build, ProxyBridge does not introduce noticeable performance degradation in Linux environments.

No deep reverse engineering or development experience is required, just normal usage and honest feedback.

🤝 How to participate

If you’re interested, please comment below with:

Your Linux distribution and version
Desktop environment (optional)
Any specific use cases you’d like to test

Your help will directly improve the Linux release quality.
Thanks in advance to everyone who’s willing to contribute! 🙌

yangjinhe · 2026-02-04T01:20:34Z

yangjinhe
Feb 4, 2026

Hi, I'd be happy to help test ProxyBridge on Linux!

My setup:

Distribution: LMDE 7 (Linux Mint Debian Edition), based on Debian 13
Desktop environment: Cinnamon
Real-world use case: My daily workflow involves connecting to multiple customer VPNs simultaneously. To manage this, I run several virtual machines—each with a different customer’s VPN—and expose a SOCKS5 proxy from each VM. On my host (LMDE 7), I currently use redsocks combined with iptables rules to selectively route application traffic through the appropriate VM-based proxy.

This makes me a strong candidate for testing per-app proxy rules, SOCKS5 configuration, and real-world routing behavior under mixed network conditions. I’m especially interested in seeing if ProxyBridge can simplify or replace my current redsocks + iptables setup with a more user-friendly and reliable solution.

I’m ready to test:

Rule switching between different SOCKS5 proxies (matching my VM setup)
Application-level proxy routing accuracy
Performance impact during concurrent proxy usage
Stability under long-running sessions

Looking forward to trying out the build—thanks for your work on this!

0 replies

Anof-cyber · 2026-02-04T08:29:02Z

Anof-cyber
Feb 4, 2026
Maintainer Author

ProxyBridge Linux v4.0-Beta

Welcome to the ProxyBridge Linux beta testing program! This guide will help you install and test ProxyBridge on your Linux system.

System Requirements

Linux Distribution: Ubuntu, Debian, Fedora, RHEL, CentOS, Rocky Linux, AlmaLinux, Arch, Manjaro, openSUSE, or SLES
Privileges: Root/sudo access required
Architecture: x86_64 (64-bit)

Installation Steps

1. Download and Extract

ProxyBridge-Linux-v4.0-Beta.tar.gz

# Navigate to your download location
cd ~/Downloads

# Extract the archive
tar -xzf ProxyBridge-Linux-v4.0-Beta.tar.gz

# Enter the extracted directory
cd ProxyBridge-Linux-v4.0-Beta

You should now see three files:

ProxyBridge - Main executable
libproxybridge.so - Shared library
deploy.sh - Automated installation script

2. Install ProxyBridge System-Wide

Run the deployment script with sudo:

sudo ./deploy.sh

The script will automatically:

Detect your Linux distribution
Install required dependencies (libnetfilter-queue, libnfnetlink, iptables)
Install ProxyBridge to /usr/local/bin
Install library to /usr/local/lib
Update library cache with ldconfig
Verify the installation

Expected Output:

Dependencies installed
Files installed to /usr/local
Library cache updated
ProxyBridge executable is working
All checks passed

3. Verify Installation

After successful installation, you can run ProxyBridge from anywhere:

ProxyBridge --help

Basic Usage

Only CLI is supported in the Beta Version
CLI commands are the same as Windows CLI

Starting ProxyBridge

Example 1: Route Firefox through SOCKS5 proxy

sudo ProxyBridge \
  --proxy socks5://192.168.1.100:1080 \
  --rule "firefox:*:*:TCP:PROXY" \
  --verbose 2

Example 2: Route all Chrome traffic through HTTP proxy

sudo ProxyBridge \
  --proxy http://proxy.example.com:8080 \
  --rule "chrome:*:*:TCP:PROXY" \
  --rule "chrome:*:*:UDP:PROXY" \
  --verbose 2

Example 3: Block specific application

sudo ProxyBridge \
  --rule "malware:*:*:TCP:BLOCK" \
  --verbose 2

Example 4: Proxy with authentication and DNS routing

sudo ProxyBridge \
  --proxy socks5://username:[email protected]:1080 \
  --rule "firefox:*:*:TCP:PROXY" \
  --dns-via-proxy true \
  --verbose 2

Command-Line Options

Option	Description	Example
`--proxy <url>`	Proxy server URL	`socks5://host:port` or `http://host:port`
`--rule <rule>`	Add routing rule	`"process:host:port:protocol:action"`
`--dns-via-proxy <bool>`	Route DNS through proxy	`true` or `false` (default: true)
`--verbose <level>`	Logging verbosity	`0` (none), `1` (logs), `2` (connections), `3` (both)
`--cleanup`	Stop and cleanup iptables rules
`--help`	Show help message

Rule Format

Rules follow this format: "process:target_host:target_port:protocol:action"

process: Process name (e.g., firefox, chrome) or * for any
target_host: Destination IP/hostname or * for any
target_port: Destination port or * for any
protocol: TCP, UDP, or BOTH
action: PROXY, DIRECT, or BLOCK

Examples:

--rule "firefox:*:*:TCP:PROXY"              # All Firefox TCP traffic via proxy
--rule "chrome:*.google.com:443:TCP:PROXY"  # Chrome to Google on port 443 via proxy
--rule "*:192.168.1.*:*:TCP:DIRECT"         # All traffic to local network direct
--rule "malware:*:*:BOTH:BLOCK"             # Block all traffic from 'malware'

Verbose Levels

0: Silent mode (no output except errors)
1: Log messages only (errors, warnings)
2: Connection tracking only (shows which apps connect where)
3: Both logs and connections (full verbosity)

Stopping ProxyBridge

Press Ctrl+C to stop ProxyBridge. It will automatically clean up iptables rules.

Alternatively, run cleanup manually:

sudo ProxyBridge --cleanup

Known Limitations

Requires root/sudo privileges
Only supports IPv4 (IPv6 not yet implemented)
Process name matching is case-sensitive
UDP proxy only works with SOCKS5 (not HTTP proxies)

Uninstallation

To remove ProxyBridge:

sudo rm /usr/local/bin/ProxyBridge
sudo rm /usr/local/lib/libproxybridge.so
sudo rm /etc/ld.so.conf.d/proxybridge.conf
sudo ldconfig

Advanced Usage

Multiple Rules

You can add multiple rules with multiple --rule flags:

sudo ProxyBridge \
  --proxy socks5://proxy:1080 \
  --rule "firefox:*:443:TCP:PROXY" \
  --rule "firefox:*:80:TCP:PROXY" \
  --rule "chrome:*:*:TCP:DIRECT" \
  --verbose 2

Troubleshooting

"Permission denied" Error

Solution: Always run with sudo - ProxyBridge needs root access for iptables and netfilter.

"libproxybridge.so: cannot open shared object file"

Solution: Run sudo ldconfig to update library cache, or re-run ./deploy.sh.

Thank you for beta testing ProxyBridge! Your feedback helps us improve the software for everyone.

0 replies

yangjinhe · 2026-02-05T15:24:49Z

yangjinhe
Feb 5, 2026

I’ve been using ProxyBridge for about a day and have encountered a couple of issues I’d like to share.

1. Installation Issue

My system is LMDE 7, based on Debian 13.
The automatic installation script detected the OS as linuxmint and displayed the warning:
WARNING: Unknown distribution 'linuxmint'.

Following the prompt — “Please manually install: libnetfilter-queue, libnfnetlink, iptables” — I ran into incorrect package names:

libnetfilter-queue does not exist in the Debian repositories; the correct package name is libnetfilter-queue1.
Similarly, libnfnetlink is not available; the correct package is libnfnetlink0.

After installing the correct packages manually, I was able to proceed with the setup.

2. Performance Issue

I configured 10 proxy rules targeting internal IP ranges, plus one exclusion rule for wstunnel, as shown below:

ProxyBridge --proxy socks5://172.16.243.128:33080 \
--rule "*:10.251.72.*:*:TCP:PROXY" \
--rule "*:10.251.101.*:*:TCP:PROXY" \
--rule "*:10.128.22.*:*:TCP:PROXY" \
--rule "*:10.143.26.*:*:TCP:PROXY" \
--rule "*:10.251.110.*:*:TCP:PROXY" \
--rule "*:10.158.231.10:*:TCP:PROXY" \
--rule "*:10.238.9.65:*:TCP:PROXY" \
--rule "*:10.251.66.*:*:TCP:PROXY" \
--rule "*:10.251.85.*:*:TCP:PROXY" \
--rule "*:10.251.112.*:*:TCP:PROXY" \
--rule "wstunnel:*:*:BOTH:DIRECT" \
--verbose 2

My browsing setup:

I use Firefox with the ZeroOmega extension to access GFW-blocked sites (e.g., GitHub).
ZeroOmega routes traffic through a local SOCKS5 proxy provided by wstunnel running on 127.0.0.1:8800.

Observed behavior:

When ProxyBridge is running with the above rules, accessing GFW-blocked sites (like GitHub) becomes very slow.
Accessing sites within the defined internal IP ranges or non-blocked sites remains unaffected and fast.
As soon as I stop ProxyBridge, GitHub loads quickly again.

This is unexpected because:

The wstunnel process is explicitly excluded via the rule wstunnel:*:*:BOTH:DIRECT.
Firefox connects to 127.0.0.1:8800 (local), which should not match any of the proxy rules (all target remote 10.x.x.x IPs).
Logs confirm that wstunnel and Firefox’s connection to 127.0.0.1:8800 are handled via direct routing.

Relevant log snippet:

[CONN] firefox-bin (PID:38412) -> 127.0.0.1:8800 via direct tcp
[CONN] wstunnel (PID:41418) -> 172.67.221.246:443 via direct tcp

Despite this, there appears to be a noticeable performance impact on proxied (GFW-bypassed) traffic when ProxyBridge is active—even though that traffic shouldn’t be intercepted.

I’ll continue testing and will report any additional findings. Thanks for your work on this tool!

1 reply

Anof-cyber Feb 7, 2026
Maintainer Author

There have been multiple performance optimisations in the latest beta version.

Can you help me with more details about this part?

Firefox connects to 127.0.0.1:8800 (local), which should not match any of the proxy rules (all target remote 10.x.x.x IPs).
Logs confirm that wstunnel and Firefox’s connection to 127.0.0.1:8800 are handled via direct routing.

Is it supposed to go through a proxy, or is it blocked? ProxyBridge do not touch any 127...* IP range traffic. If there are no rule means it its direct connection and even if there is a rule for proxy for certain IP addres like 127 it will be ignored as 127 and other IP are always marked as direct connections.

Anof-cyber · 2026-02-07T21:10:58Z

Anof-cyber
Feb 7, 2026
Maintainer Author

ProxyBridge Linux 4.1.0 Beta is now available

Added a GUI using GTK3
Performance improvements
Fixed installation and setup issues
Fixed network speed issues
Fixed SOCKS5 authentication timeout handling
Fixed SOCKS5 UDP any-IP validation as per RFC
Improved high memory usage handling

ProxyBridge_Linux_v4.1.0-beta.tar.gz

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Calling for Linux Testers for ProxyBridge (Pre-Release) #65

Uh oh!

{{title}}

Uh oh!

Replies: 4 comments 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Calling for Linux Testers for ProxyBridge (Pre-Release) #65

Uh oh!

InterceptSuite Admin Feb 3, 2026

🎯 Goal

🐧 Target Distributions

🧪 Key Use Cases to Test

🤝 How to participate

Replies: 4 comments · 1 reply

Uh oh!

Uh oh!

yangjinhe Feb 4, 2026

Uh oh!

Anof-cyber Feb 4, 2026 Maintainer Author

ProxyBridge Linux v4.0-Beta

System Requirements

Installation Steps

1. Download and Extract

2. Install ProxyBridge System-Wide

3. Verify Installation

Basic Usage

Starting ProxyBridge

Command-Line Options

Rule Format

Verbose Levels

Stopping ProxyBridge

Known Limitations

Uninstallation

Advanced Usage

Multiple Rules

Troubleshooting

"Permission denied" Error

"libproxybridge.so: cannot open shared object file"

Uh oh!

Uh oh!

yangjinhe Feb 5, 2026

1. Installation Issue

2. Performance Issue

Uh oh!

Anof-cyber Feb 7, 2026 Maintainer Author

Uh oh!

Anof-cyber Feb 7, 2026 Maintainer Author

InterceptSuite Admin
Feb 3, 2026

Replies: 4 comments 1 reply

yangjinhe
Feb 4, 2026

Anof-cyber
Feb 4, 2026
Maintainer Author

yangjinhe
Feb 5, 2026

Anof-cyber Feb 7, 2026
Maintainer Author

Anof-cyber
Feb 7, 2026
Maintainer Author