-
-
Notifications
You must be signed in to change notification settings - Fork 208
Description
Platform
Windows
ProxyBridge Version
3.2.0
OS and Version
Windows 11
Documentation
- I have read the Windows documentation
- I have read the macOS documentation
- I have read the Linux documentation
Code Review
- I have gone through the code page
Describe the Bug
Steps to reproduce:
0 - Make sure WIFI is disconnected
1 - Start ProxyBridge, "Run as administrator" or not does not change the outcome (current rules in additional context)
2 - Start WIFI Connection
Expected behavior:
WIFI Client receives IP from DHCP server
Actual behavior:
WIFI Client gets stuck on 169.254.x.x IP
Closing ProxyBridge fixes the issue immediately.
I have tested this on multiple different WiFis and even it interferes with company Pritunl VPN (Default gateway is disabled)
Additional Context
[
{
"processNames": "Code.exe",
"targetHosts": "",
"targetPorts": "",
"protocol": "BOTH",
"action": "PROXY",
"enabled": true
},
{
"processNames": "Discord.exe",
"targetHosts": "",
"targetPorts": "",
"protocol": "TCP",
"action": "PROXY",
"enabled": true
},
{
"processNames": "BraveUpdate.exe",
"targetHosts": "",
"targetPorts": "",
"protocol": "BOTH",
"action": "PROXY",
"enabled": true
},
{
"processNames": "Brave.exe",
"targetHosts": ".brave.com",
"targetPorts": "",
"protocol": "TCP",
"action": "PROXY",
"enabled": true
},
{
"processNames": "Telegram.exe",
"targetHosts": "",
"targetPorts": "",
"protocol": "BOTH",
"action": "PROXY",
"enabled": true
},
{
"processNames": "",
"targetHosts": "",
"targetPorts": "*",
"protocol": "BOTH",
"action": "DIRECT",
"enabled": true
}
]
Last rule is also used to fix random bugs.
