| 1 |
On 02/13/2015 10:44 PM, Joseph wrote: |
| 2 |
> |
| 3 |
> Thank for replying. |
| 4 |
> |
| 5 |
> My eeepc VPN IP: 192.168.151.9 is the client connected over VPN to server VPN IP 192.168.151.1 |
| 6 |
> |
| 7 |
> So I inserted on eeepc (client) to /etc/openvpn/eeepc.conf |
| 8 |
> ... |
| 9 |
> push "route 192.168.151.0 255.255.255.0" |
| 10 |
|
| 11 |
This goes on the server, in whatever directory (ccd?) you're using for |
| 12 |
the client configs. It's specified by the client-config-dir parameter in |
| 13 |
openvpn.conf on the server. Add it to a file called "DEFAULT" so it |
| 14 |
applies to every VPN client. |
| 15 |
|
| 16 |
Once you have that set up (don't forget to restart OpenVPN!), connect to |
| 17 |
the VPN with your EeePC. You should see something in the logs like, |
| 18 |
|
| 19 |
Feb 14 10:40:40 [openvpn] SENT CONTROL [vpn1.example.com]: |
| 20 |
'PUSH_REQUEST' (status=1) |
| 21 |
|
| 22 |
Feb 14 10:40:40 [openvpn] PUSH: Received control message: |
| 23 |
'PUSH_REPLY,topology subnet,route-gateway... |
| 24 |
|
| 25 |
Feb 14 10:40:40 [openvpn] /bin/ip route add 10.1.1.0/24 via 192.168.151.1 |
| 26 |
|
| 27 |
... (more /bin/ip/route commands) |
| 28 |
|
| 29 |
At that point your EeePC should be able to ping things on the 10.1.1.x |
| 30 |
subnet. Make sure that works, and then start messing with the printer. |
| 31 |
|
| 32 |
You shouldn't need anything on the client except a minimal openvpn.conf |
| 33 |
and your keys. |
Archives