OpenVPN - Stuck (I believe) with Network Interface / Device /Firewall setup

I have a working VPN setup from a previous OpenWRT FW, now im trying to port to a recent build OpenWRT fw, but, some things shave changed...

I can no longer bridge a device from Interface, now its devices?

The logs with verb 11 disclose no meaningful info either just that it authenticates and then disconnects. Connection reset. So I suspect the firewall/bridging and my lack of understanding to deploy on the new fw correctly tlmay be where the issue is.

Is there an updated tutorial for recent OpenAwrt builds somewhere I can refer to that shows how to setup the interface / device and firewall portion of an openvpn server?

On previous outdated fw, it was quiet easy, just picked the interface of choice like VLAN 10 for example and bridge to Tap. Then open port in firewall to open port on device.

I see we're using proto=tcp-server/tcp-client and UDP now. My previous configuration are proto udp4 and tcp4

Update, Log states it is trying to connect via port 1194, this vpn server however is setup for a different port, so where is this port coming from?

OPENWRT logs:
Wed Sep 13 22:26:31 2023 daemon.notice openvpn(OpenVPNServ)[18142]: event_wait returned 0
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: event_wait returned 0
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 write_control_auth(): P_CONTROL_V1
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 WRITE [1160] to [AF_INET]192.168.1.1:1194: P_CONTROL_V1 kid=0 sid=a60e84fb 03735c7e tls_hmac=8670d05a 9ae3b315 ae5fe72a 1b007dc5 ac66e54b pid=[ #6 / time = (1694643990) 2023-09-13 22:26:30 ] pid=1 DATA 16030300 7a020000 76030346 221defd4 e595bcb9 fbdfb0a2 b399891a 25d6b35[more...]
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 write returned 1160
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 write_control_auth(): P_CONTROL_V1
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 WRITE [1160] to [AF_INET]192.168.1.1:1194: P_CONTROL_V1 kid=0 sid=a60e84fb 03735c7e tls_hmac=f3afb552 7d79bc2f 607478bc 1abd14c1 f98dba65 pid=[ #7 / time = (1694643990) 2023-09-13 22:26:30 ] pid=2 DATA bcba95e5 6a9bb993 5b2d581f 062f08e4 0bb7cb8d 4c02eed5 0dba1a87 09e344f[more...]
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 write returned 1160
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 write_control_auth(): P_CONTROL_V1
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 WRITE [1160] to [AF_INET]192.168.1.1:1194: P_CONTROL_V1 kid=0 sid=a60e84fb 03735c7e tls_hmac=a4543539 d86b72b7 e987f137 a8fef5fd 799ce69a pid=[ #8 / time = (1694643990) 2023-09-13 22:26:30 ] pid=3 DATA 1a80fc23 8853ed58 ed73f9d6 b7312fab 7cdc95c8 bea022ae 0bf41b3d c5ed0d1[more...]
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 write returned 1160
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 write_control_auth(): P_CONTROL_V1
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 WRITE [163] to [AF_INET]192.168.1.1:1194: P_CONTROL_V1 kid=0 sid=a60e84fb 03735c7e tls_hmac=d54f605f 244b074d baf9ab15 769a014e 4a937ab9 pid=[ #9 / time = (1694643990) 2023-09-13 22:26:30 ] pid=4 DATA c0e41f54 288152ec 702b81f1 2f4c0313 9b58e9f5 9154c999 ddf0e905 c0c82fc[more...]
Wed Sep 13 22:26:32 2023 daemon.notice openvpn(OpenVPNServ)[18142]: 192.168.1.1:1194 UDPv4 write returned 163

Client Logs;
TLS Error: Unroutable control packet received from...

Update: really bizzare, it seems to be ignoring my config to port other than 1194 despite me setting it in my config via luci

That sucks, I guess ... ?

1 Like

I was so tired last night when I posted this low effort post, sorry. Okay. Updating

I figured it out. The client software was the issue

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.