ivpn
No connectivity in case of IP addresses conflict
Bug report
No connectivity if user use same default gateway IP as WireGuard connection IVPN gateway (172.16.0.1) NOTE: same issue with OpenVPN (when VPN network mask conflicts with users)
The issue was observed on macOS. It has to be tested also on other platforms and VPN connections.
Describe your environment
- OS name and version: macOS
- IVPN app version: 3.3.20
Describe the problem
The IVPN WireGuard connection is using an internal default gateway to route all traffic IP: 172.16.0.1 But if users' network configuration using the same IP for the default gateway - the IVPN client is unable to set up routing correctly. Therefore traffic will not be routed through the WireGuard interface. If the IVPN Firewall is enabled - all traffic will be blocked in this case.
Steps to reproduce:
- Users default gateway configuration is 172.16.0.1
- Connect WireGuard
Observed Results:
If Firewall enabled: no connectivity If Firewall disabled: all traffic is routing through a user-default interface (not through VPN)
Expected Results:
All traffic is routing over VPN
User report: https://sentry.tamazaki.com/organizations/ivpn/issues/68338/events/ce8ed3eb0f82470681849d37e2a6139a/
I got both a VPN and Internet disconnection when I tried to add in the VPN's private/public IP address into the source/Internet firewall's configurations. It was obvious that both client and VPN are different machines with different designs, thus, IP address conflict has occurred to where it applies. Thankfully, a reboot of the system clears the app freeze and internet connection brick.
