Closed MamaMia14SS88 closed 8 months ago
I haven't encountered such issues on my side. Local addresses, such as 192.168.0.0/16, are accessible when 'Allow LAN traffic ...' is enabled. @gorkapernas, could you please check it on your side?
@MamaMia14SS88 Can you check if these addresses are accessible using the ping tool? (ping 192.168.1.1
)
ping 192.168.1.1
No I got 4 errors
@MamaMia14SS88 Was the VPN connected while you were trying to access this IP?
Could you please perform the following additional tests:
1) Disconnect the VPN (if connected).
2) Disable the IVPN firewall.
3) Run tracert 192.168.1.1
4) Activate 'Allow LAN traffic ...' and enable the IVPN Firewall.
5) Run tracert 192.168.1.1
Was the VPN connected while you were trying to access this IP?
Yes it was
Could you please perform the following additional tests:
- Disconnect the VPN (if connected).
- Disable the IVPN firewall.
- Run
tracert 192.168.1.1
- Activate 'Allow LAN traffic ...' and enable the IVPN Firewall.
- Run
tracert 192.168.1.1
The first tracert works fine, but the second gives a general failure
@MamaMia14SS88 Just in case, please ensure that you do not use the WiFi control functionality (option 'WiFi control -> Trusted/Untrusted WiFi network control'). The 'Block LAN traffic' action will override the default behavior of the Firewall when you are connected to an Untrusted network.
Bug report
Describe your environment
Describe the problem
Steps to reproduce:
192.168.1.1
do not work in the browserObserved Results:
Can't access local addresses
Expected Results:
The browser should open local addresses like
192.168.1.1
to configure the router. Although everything works fine with the firewall turned off.Relevant Code: