Configuring OpenVPN for internet passthough
Solved/Closed
loosescrews
Posts
2
Registration date
Tuesday August 16, 2011
Status
Member
Last seen
August 17, 2011
-
Aug 16, 2011 at 04:42 AM
Anonymous User - Aug 17, 2011 at 12:24 PM
Anonymous User - Aug 17, 2011 at 12:24 PM
Related:
- Configuring OpenVPN for internet passthough
- Fenix internet llc - Guide
- Internet explorer 11 for windows 10 64-bit - Download - Browsers
- Internet cafe simulator 2 pc download - Download - Simulation
- Internet cafe simulator pc download - Download - Simulation
- Internet booster for pc - Download - Other
2 responses
Anonymous User
Aug 17, 2011 at 08:58 AM
Aug 17, 2011 at 08:58 AM
Greetings,
Is OpenVPN configured for client can only access the server, or at the whole LAN server side?
If it provides access to the LAN server side, so at the time of connection, the server sends the client a route to the subnet 192.168.1.x This road passes all client access to 192.168.1.x from the VPN tunnel.
Therefore, the client can not access the 192.168.1.x IP's own local network, the livebox. More Internet, then.
However, the OpenVPN connection is not impacted as it had been established before the client receives the new route to 192.168.1.x So you must always be able to ping the VPN server from the client.
To connect two subnets through a VPN tunnel, it is better that these subnets are different.
If you just need to establish a connection between the server and the client, without involving the other two machines LAN, you must edit the configuration files to the server no longer sends a route to the client (the comment line push "route 192.168.1.0 255.255.255.0" in the config file server).
Thus, if you need to interconnect the LAN, it would be best to change the addressing scheme of the two sites.
Post the config files and should be fixed. Do not forget to hide the public IP or domain name.
PS: I use an arbitrary ip adress.
Is OpenVPN configured for client can only access the server, or at the whole LAN server side?
If it provides access to the LAN server side, so at the time of connection, the server sends the client a route to the subnet 192.168.1.x This road passes all client access to 192.168.1.x from the VPN tunnel.
Therefore, the client can not access the 192.168.1.x IP's own local network, the livebox. More Internet, then.
However, the OpenVPN connection is not impacted as it had been established before the client receives the new route to 192.168.1.x So you must always be able to ping the VPN server from the client.
To connect two subnets through a VPN tunnel, it is better that these subnets are different.
If you just need to establish a connection between the server and the client, without involving the other two machines LAN, you must edit the configuration files to the server no longer sends a route to the client (the comment line push "route 192.168.1.0 255.255.255.0" in the config file server).
Thus, if you need to interconnect the LAN, it would be best to change the addressing scheme of the two sites.
Post the config files and should be fixed. Do not forget to hide the public IP or domain name.
PS: I use an arbitrary ip adress.
loosescrews
Posts
2
Registration date
Tuesday August 16, 2011
Status
Member
Last seen
August 17, 2011
Aug 17, 2011 at 12:07 PM
Aug 17, 2011 at 12:07 PM
Hello,
Thanks for your response. I already tried adding push "route 192.168.1.0 255.255.255.0" to the OpenVPN config file, but it didn't fix the problem.
Setting up IP Tables did fix the problem. I found out how to do it here: http://serverflux.com/networking/how-to-install-openvpn-on-debian-with-iptables/
I hope this helps someone in the future.
Ian
Thanks for your response. I already tried adding push "route 192.168.1.0 255.255.255.0" to the OpenVPN config file, but it didn't fix the problem.
Setting up IP Tables did fix the problem. I found out how to do it here: http://serverflux.com/networking/how-to-install-openvpn-on-debian-with-iptables/
I hope this helps someone in the future.
Ian
