-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push routes to clients? #559
Comments
In that particular scenario, you shouldn't need to push a route to wireless clients, if the VPN tunnel is terminating on the router, and the router is the default gateway for wireless clients. |
I don't know if I have explained correctly. The VPN is not for private internet access, only point to point VPN connection. So if the login page is on 10.10.10.20 and the client device has an address of 192.168.200.20, the 2 cannot communicate. I think pushing the route to the client should solve the issue, but I find no particular way to do so. Do note the internet gateway address is not in the "10.10.10.x" range. It is, for example, 172.16.2.1. |
What I'm suggesting is that you need to deal with routing where the VPN tunnel terminates, I made the assumption that the VPN terminates on the internet gateway which for example is 172.16.2.1. The routing details do not need to be pushed to the wireless clients, they are handled on the default gateway they are pointing to. |
Ah, in that case it does not happen as you have suggested. I cannot access anything on the VPN side of this from a client device. Correct me if I'm wrong, I think coova by default does not allow this. |
The login page in my case is on a server connected to the router over a VPN. Coova-chilli is also on the same router. I would like the login page to be served over the VPN network.
Can coova push routes to connected clients?
The text was updated successfully, but these errors were encountered: