Calling for Linux Testers for ProxyBridge (Pre-Release) #65
Replies: 4 comments 1 reply
-
|
Hi, I'd be happy to help test ProxyBridge on Linux! My setup:
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 I’m ready to test:
Looking forward to trying out the build—thanks for your work on this! |
Beta Was this translation helpful? Give feedback.
-
ProxyBridge Linux v4.0-BetaWelcome to the ProxyBridge Linux beta testing program! This guide will help you install and test ProxyBridge on your Linux system. System Requirements
Installation Steps1. Download and ExtractProxyBridge-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-BetaYou should now see three files:
2. Install ProxyBridge System-WideRun the deployment script with sudo: sudo ./deploy.shThe script will automatically:
Expected Output: 3. Verify InstallationAfter successful installation, you can run ProxyBridge from anywhere: ProxyBridge --helpBasic Usage
Starting ProxyBridgeExample 1: Route Firefox through SOCKS5 proxy sudo ProxyBridge \
--proxy socks5://192.168.1.100:1080 \
--rule "firefox:*:*:TCP:PROXY" \
--verbose 2Example 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 2Example 3: Block specific application sudo ProxyBridge \
--rule "malware:*:*:TCP:BLOCK" \
--verbose 2Example 4: Proxy with authentication and DNS routing sudo ProxyBridge \
--proxy socks5://username:[email protected]:1080 \
--rule "firefox:*:*:TCP:PROXY" \
--dns-via-proxy true \
--verbose 2Command-Line Options
Rule FormatRules follow this format:
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
Stopping ProxyBridgePress Alternatively, run cleanup manually: sudo ProxyBridge --cleanupKnown Limitations
UninstallationTo 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 ldconfigAdvanced UsageMultiple RulesYou can add multiple rules with multiple sudo ProxyBridge \
--proxy socks5://proxy:1080 \
--rule "firefox:*:443:TCP:PROXY" \
--rule "firefox:*:80:TCP:PROXY" \
--rule "chrome:*:*:TCP:DIRECT" \
--verbose 2Troubleshooting"Permission denied" ErrorSolution: Always run with "libproxybridge.so: cannot open shared object file"Solution: Run Thank you for beta testing ProxyBridge! Your feedback helps us improve the software for everyone. |
Beta Was this translation helpful? Give feedback.
-
|
I’ve been using ProxyBridge for about a day and have encountered a couple of issues I’d like to share. 1. Installation IssueMy system is LMDE 7, based on Debian 13. Following the prompt — “Please manually install: libnetfilter-queue, libnfnetlink, iptables” — I ran into incorrect package names:
After installing the correct packages manually, I was able to proceed with the setup. 2. Performance IssueI configured 10 proxy rules targeting internal IP ranges, plus one exclusion rule for 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 2My browsing setup:
Observed behavior:
This is unexpected because:
Relevant log snippet: 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! |
Beta Was this translation helpful? Give feedback.
-
|
ProxyBridge Linux 4.1.0 Beta is now available
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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:
🐧 Target Distributions
I am especially interested in testing on:
🧪 Key Use Cases to Test
Testers are encouraged to validate ProxyBridge under different real-world scenarios, including:
Proxy rule testing
Proxy configuration testing
Protocol coverage
Performance & resource usage
System resource monitoring
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 help will directly improve the Linux release quality.
Thanks in advance to everyone who’s willing to contribute! 🙌
Beta Was this translation helpful? Give feedback.
All reactions