Hi there,
I want to configure a dedicated server with Samba and OpenVPN on it.
(I know, there is an easier way with ssh...)
The server has 192.0.2.1 (eth0) and 192.168.5.1 (tun0).
The only client gets 192.168.5.5 (tun0).
The configuration seems to be correct. If I don't use any security (certs and key-files), the connection works pretty good. I can Ping around and be able to access the samba-shares. Now, I think, I made a mistake while creating the certificates with tinyCA on Ubuntu.
The server is a OpenSuse 12.1 machine.
#OpenVPN-Server config
status /var/log/openvpn/status.log
log-append /var/log/openvpn/openvpn.log
verb 9
port 443
dev tun
proto udp
comp-lzo
tun-mtu 1500
mssfix 1212
ifconfig 192.168.5.1 192.168.5.5
#tls-server
#dh /etc/openvpn/dh2048.pem
#ca ca-cert.pem
#cert server-cert.pem
#key server-key.pem
The client is an Ubuntu 11.10 machine:
#OpenVPN-Client
status /var/log/openvpn/status.log
log-append /var/log/openvpn/openvpn.log
verb 9
remote 192.0.2.1
dev tun
port 443
proto udp
comp-lzo
ifconfig 192.168.5.5 192.168.5.1
tun-mtu 1500
mssfix 1212
#tls-client
#ca ca-cert.pem
#cert client-cert.pem
#key client-key.pem
You see, I commented out the lines with the security. There isn't any problem to ping and access the samba-shares.
(smb:\\192.168.5.1\foobar\)
Now, I delete the '#'. OpenVPN returns no errors while starting. (only asks for the password of the key-file)
I can't ping any hosts in 192.168.5.0/24. The shares aren't accessible.
Im able to capture tun0 with wireshark, but after a while wireshark says, that there isn't any interface called "tun0".
These are the things, i've done with tinyCA:
- requested root-cert, server-cert and client-cert
- exported the keys and the certs for client and server
Thanks for reading, hope somebody has got an useful tip for me.
difoltuser
