Client stopped directing traffic to router config page
Posted: Mon Jul 10, 2023 3:43 pm
Background:
Client vs 3.3.7 (2979)
Windows 11
I have an OpenVPN server setup in my office router (remote). I can connect to other device in the server side successfully. On the client side (local to me) I use to be able to access the router config page (192.168.1.1). After a recent power failure on the server side, my client stopped directing traffic to the server. Those may be unrelated, but it would be a strong coincidence.
On the local side my IP address are 172.XXX.X.XXX, so it weird that the client would get confused and think its a local address rather than a remote one.
I can connect successfully to other devices in the network, just not the router page (which I use to be able to do without issue).
Client vs 3.3.7 (2979)
Windows 11
I have an OpenVPN server setup in my office router (remote). I can connect to other device in the server side successfully. On the client side (local to me) I use to be able to access the router config page (192.168.1.1). After a recent power failure on the server side, my client stopped directing traffic to the server. Those may be unrelated, but it would be a strong coincidence.
On the local side my IP address are 172.XXX.X.XXX, so it weird that the client would get confused and think its a local address rather than a remote one.
I can connect successfully to other devices in the network, just not the router page (which I use to be able to do without issue).
Is there anything I can do form the client side to resolve this? I tried adding the force traffic config line to the client, but without access to the server it appear to have not worked.C:\Windows\System32>tracert -d 192.168.1.1
Tracing route to 192.168.1.1 over a maximum of 30 hops
1 78 ms 77 ms 75 ms 192.168.1.1
Trace complete.
C:\Windows\System32>tracert -d 192.168.1.157
Tracing route to 192.168.1.157 over a maximum of 30 hops
1 77 ms 75 ms 74 ms 10.8.0.1
2 81 ms 73 ms 85 ms 192.168.1.157
Trace complete.