OpenVPN Pi setup not listening

pipigo

I have setup pivpn on my local network. After launching the server and checking it is running I have tried to connect. No luck. I have checked port forwaring rules on my DG but think the issue is located on the actual server.

Troubleshooting so far:

* openvpn.service - OpenVPN service
Loaded: loaded (/lib/systemd/system/openvpn.service; enabled)
Active: active (exited) since Wed 2017-12-20 09:29:32 GMT; 3h 33min ago
Process: 303 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 303 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/openvpn.service
osmc@osmcfront:/etc$ systemctl status openvpn@server.service
* openvpn@server.service - OpenVPN connection to server
Loaded: loaded (/lib/systemd/system/openvpn@.service; disabled)
Active: active (running) since Wed 2017-12-20 09:29:34 GMT; 3h 33min ago
Process: 257 ExecStart=/usr/sbin/openvpn --daemon ovpn-%i --status /run/openvpn/%i.status 10 --cd /etc/openvpn --config /etc/openvpn/%i.conf (code=exited, status=0/SUCCESS)
Main PID: 418 (openvpn)
CGroup: /system.slice/system-openvpn.slice/openvpn@server.service
`-418 /usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10 --cd /etc/openvpn --config /etc/...

netstat -l

unix 2 [ ACC ] STREAM LISTENING 1816 /run/systemd/private
unix 2 [ ACC ] SEQPACKET LISTENING 1837 /run/udev/control
unix 2 [ ACC ] STREAM LISTENING 1841 /run/systemd/journal/stdout
unix 2 [ ACC ] STREAM LISTENING 30888 /run/user/1000/systemd/private
unix 2 [ ACC ] STREAM LISTENING 7594 /var/run/lirc/lircd
unix 2 [ ACC ] STREAM LISTENING 6829 /run/rpcbind.sock
unix 2 [ ACC ] STREAM LISTENING 7349 /var/run/avahi-daemon/socket
unix 2 [ ACC ] STREAM LISTENING 12320 /var/tmp/osmc.settings.update.sockfile
unix 2 [ ACC ] STREAM LISTENING 7352 /var/run/dbus/system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 11390 /var/tmp/osmc.settings.sockfile
unix 2 [ ACC ] STREAM LISTENING 6640 /var/run/dhcpcd.sock

nc 192.168.1.201 1194
cant connect to remote host: connection refused

ordex

for pivpn specific problems I'd suggest you to get in touch with the project community at https://github.com/pivpn
However consider that "nc" by default will use TCP, but I guess that your server is listening on UDP, therefore your test is not really meaningful.

pipigo

Hi - thanks for that ref nc. Regarding the pivpn comment though, is this not just a scripted way of installing OVPN server? I havent had any particular issues there and it seems that it is all running. The issues I have surely relate to something in the config file which I am sure I could get assistance with here?

pipigo

Is anyone able to give me an idea of next troubleshooting steps that would at least confirm if the server is actually listening or not, and of not what I must do to make it so and confirm it is. Then I can worry about routing from the WAN

TinCanTech

pipigo wrote next troubleshooting steps

See your log files.

See --log & --verb in The Manual v24x

pipigo wrote The issues I have surely relate to something in the config file which I am sure I could get assistance with here?

What config file ?

Please see:
HOWTO: Request Help !

pipigo

Hows this?

[oconf]

uname -a
Linux osmcfront 4.9.29-10-osmc #1 SMP PREEMPT Mon Oct 9 02:18:18 UTC 2017 armv7l GNU/Linux

osmc@osmcfront:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:ce:ba:89
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:7800 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7800 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:2274126 (2.1 MiB)  TX bytes:2274126 (2.1 MiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.8.0.1  P-t-P:10.8.0.1  Mask:255.255.255.0
          inet6 addr: fe80::c8c0:fda9:d086:58a8/64 Scope:Link
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 B)  TX bytes:1760 (1.7 KiB)

wlan0     Link encap:Ethernet  HWaddr 30:b5:c2:11:83:88
          inet addr:192.168.1.201  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:337459 errors:0 dropped:0 overruns:0 frame:0
          TX packets:139053 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:60017193 (57.2 MiB)  TX bytes:19056018 (18.1 MiB)

dev tun
proto udp
port 1194
ca /etc/openvpn/easy-rsa/pki/ca.crt
cert /etc/openvpn/easy-rsa/pki/issued/server_P86kA14gNX3ojAsT.crt
key /etc/openvpn/easy-rsa/pki/private/server_P86kA14gNX3ojAsT.key
dh /etc/openvpn/easy-rsa/pki/dh1024.pem
topology subnet
server 10.8.0.0 255.255.255.0
# server and remote endpoints
ifconfig 10.8.0.1 10.8.0.2
# Add route to Client routing table for the OpenVPN Server
push "route 10.8.0.1 255.255.255.255"
# Add route to Client routing table for the OPenVPN Subnet
push "route 10.8.0.0 255.255.255.0"
# your local subnet
push "route 192.168.1.0 255.255.255.0"
# Set your primary domain name server address for clients
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"
# Override the Client default gateway by using 0.0.0.0/1 and
# 128.0.0.0/1 rather than 0.0.0.0/0. This has the benefit of
# overriding but not wiping out the original default gateway.
push "redirect-gateway def1"
client-to-client
keepalive 10 120
remote-cert-tls client
tls-version-min 1.2
tls-auth /etc/openvpn/easy-rsa/pki/ta.key 0
cipher AES-256-CBC
auth SHA256
comp-lzo
user nobody
group nogroup
persist-key
persist-tun
crl-verify /etc/openvpn/crl.pem
status /var/log/openvpn-status.log 20
status-version 3
log /var/log/openvpn.log
verb 1

L)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 26 2017
Wed Dec 20 09:29:33 2017 library versions: OpenSSL 1.0.1t  3 May 2016, LZO 2.08
Wed Dec 20 09:29:34 2017 Control Channel Authentication: using '/etc/openvpn/easy-rsa/pki/ta.key' as a OpenVPN static key file
Wed Dec 20 09:29:34 2017 TUN/TAP device tun0 opened
Wed Dec 20 09:29:34 2017 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Dec 20 09:29:34 2017 /sbin/ip link set dev tun0 up mtu 1500
Wed Dec 20 09:29:34 2017 /sbin/ip addr add dev tun0 10.8.0.1/24 broadcast 10.8.0.255
Wed Dec 20 09:29:34 2017 GID set to nogroup
Wed Dec 20 09:29:34 2017 UID set to nobody
Wed Dec 20 09:29:34 2017 UDPv4 link local (bound): [undef]
Wed Dec 20 09:29:34 2017 UDPv4 link remote: [undef]
Wed Dec 20 09:29:34 2017 Initialization Sequence Completed

pipigo

PORT STATE SERVICE VERSION
1194/udp open|filtered openvpn

That is also from an online nmap scan, but https://www.yougetsignal.com/tools/open-ports/ suggests it is closed!

TinCanTech

Your log shows that openvpn server is ready and listening ..

pipigo

OK so for anyone who hits this thread....

UDP being stateless I should have known it doesnt show as listening in netstat, it just shows as there.

The reason it wasnt showing as listening online is that my router had decided to give the Pi a DHCP address instead of the static one so port forwarding through the router had failed.

I ended up generating a ovpn file and trying to connect through localhost and from another IP on the LAN, connection began to negotiate which was therefore proof of a listening server. Hit another issue from there. Think I am best starting it as a seperate thread.

pipigo

Thanks for those who answered by the way