I changed this article to no longer use 192.168.1.0 192.168.2.0 and 192.168.3.0 for my subnets. I did this because it is important for people to not use common subnets such as 192.168.1/0.x when pushing routes to clients. It does not matter if you know where every client connects from, but once you add a single road warrior to the VPN you will run in to a problem. If the road warrior is connecting from a LAN where he has 192.168.0.X and he gets pushed a route to 192.168.0.0/24 to flow over the vpn, he will lose all connectivity to the internet until he kills the vpn. This is because the client loses his route to his gateway... he tries to contact the gateway over the VPN, but he has no route to the VPN because he needs to access his gateway to reach it. In short, if your lan that you want to access using openvpn uses a common subnet such as 192.168.0.x or 192.168.1.x, CHANGE IT. "
Is this true for 192.168.10.0/24 as well? This is the local network I use and would like to route over the VPN. It has been made to not be a common one but now I'm not entirely sure. Commonly I find 192.168.0.0/24 and 192.168.1.0/24 in local networks with default configurations. On Android I know that it uses 192.168.43.0/24 for its hotspots (which I might use while on the road). It is an entirely personal VPN so I'm its only expected user. However I might connect back from public networks. Do you know of any router that might be using 192.168.10.0/24? Could it possibly be accounted for as an issue arises? The Android hotspots would always be available anyway.
Why not use 10.x.y.z?
Обсуждают сегодня