Sorry if that's not the right place, but I'm just looking for couple explanations on why this setup works.
Because yeah, it works without any issues, but I don't know "exactly" why and I'd like to expand my knowledge on this, in case I want to build a more complex network in the future.
So right know, this is just a "basic" setup with 1 server (W7 x86) and 1 client (W7 x64).
I used to fool around with Hamachi, but as time goes, the free version gets more & more restricted and not permanently available on peak hours (for the free users).
So I went the OpenVPN way, which seems way more reliable.
I spent quite some time finding how to write a working file under Windows, here it is :
port 1194
proto tcp
dev tap
ca ca.crt
cert server.crt
key server.key
dh dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 192.168.1.0 255.255.255.0"
push "dhcp-option WINS 192.168.1.64"
push "dhcp-option DNS 192.168.1.64"
keepalive 10 120
comp-lzo
max-clients 1
persist-key
persist-tun
status openvpn-status.log
verb 3
So there are couple things that annoy me.
First, the
server line.
At first I thought I'd have to launch a server and then my own client.
But in the end the server is just a client that accepts incoming connexions and forward IPs. At least that's how that seems to work.
As for this line,
10.8.0.0 looks to be an internal IP used by the server, as I get
10.8.0.1 when I connect.
And the mask just tells me that the server will only change the last section :
10.8.0.xxx, meaning I'll only have access to 255 IPs right ?
Then, the
push "route one.
In every tutorial I checked, it was always a VPN IP (
10.xxx.xxx.xxx) that was used, not the usual
192.168.xxx.xxx.
Except on the Windows tutorial that I used to build this config.
What's the best option in my case ? Should I use a
10.xxx.xxx.xxx IP, or should I keep the
192.168.xxx.xxx ones ?
