Setup Problems Client OpenVPN / WRT54GL need Help

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
JohnPain
Posts: 4
Joined: Thu Aug 23, 2018 10:51 am

Setup Problems Client OpenVPN / WRT54GL need Help

Post by JohnPain » Sun Aug 26, 2018 12:47 pm

Hi,
got two Routers in a Row:

Mainnet is 192.168.0.x/24 with FritzBox Router with ISP Connection
Second Net is 192.168.1.x/24 with WRT54GL 1.1 , running dd-wrt-v24-vps-firmware
Connecting the net over WAN Port using dhcp worked fine, including internet access in 2nd network.

Now I wanted to connect to/through VPS/VPN running Softether using Services/VPN/OpenVPN.
- enabled Function in SoftEther
- generated dummy file via Server-Manager with ceritficates/key in it and put everything in the router config.

Now there are problems. Router tries to connect, no internet access in 2nd network.
Here is some log output (I put some xxx in for privacy reasons):

Clientlog:
20180826 14:32:12 W WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
20180826 14:32:12 W WARNING: file '/tmp/openvpncl/client.key' is group or others accessible
20180826 14:32:12 W WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
20180826 14:32:12 I OpenVPN 2.4.6 mipsel-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug 22 2018
20180826 14:32:12 I library versions: OpenSSL 1.1.0i 14 Aug 2018 LZO 2.09
20180826 14:32:12 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
20180826 14:32:12 W WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
20180826 14:32:12 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20180826 14:32:12 I TCP/UDP: Preserving recently used remote address: [AF_INET]185.22.174.xxx:1194
20180826 14:32:12 Socket Buffers: R=[32767->32767] S=[32767->32767]
20180826 14:32:12 I UDPv4 link local: (not bound)
20180826 14:32:12 I UDPv4 link remote: [AF_INET]185.22.174.xxx:1194
20180826 14:32:12 TLS: Initial packet from [AF_INET]185.22.174.xxx:1194 sid=fe83223d a3c3c42c
20180826 14:32:12 N TLS Error: reading acknowledgement record from packet
20180826 14:32:12 N TLS Error: reading acknowledgement record from packet
20180826 14:32:15 N TLS Error: reading acknowledgement record from packet
20180826 14:32:20 NOTE: --mute triggered...
20180826 14:32:26 1 variation(s) on previous 3 message(s) suppressed by --mute
20180826 14:32:26 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180826 14:32:26 D MANAGEMENT: CMD 'state'
20180826 14:32:26 MANAGEMENT: Client disconnected
20180826 14:32:26 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180826 14:32:26 D MANAGEMENT: CMD 'state'
20180826 14:32:26 MANAGEMENT: Client disconnected
20180826 14:32:27 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180826 14:32:27 D MANAGEMENT: CMD 'state'
20180826 14:32:27 MANAGEMENT: Client disconnected
20180826 14:32:27 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180826 14:32:27 D MANAGEMENT: CMD 'status 2'
20180826 14:32:27 MANAGEMENT: Client disconnected
20180826 14:32:27 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180826 14:32:27 D MANAGEMENT: CMD 'log 500'
19700101 01:00:00

Can please someone help to get it up and running.
Thanks,
JohnPain

JohnPain
Posts: 4
Joined: Thu Aug 23, 2018 10:51 am

Re: Setup Problems Client OpenVPN / WRT54GL need Help

Post by JohnPain » Wed Aug 29, 2018 5:22 pm

Hi,

I finally got it working.I forgot to put SHA1 for authentication.
First check showed, that everything is working now. But I still have some status messages that are not right I think.
As follows:

20180829 19:08:18 Outgoing Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key
20180829 19:08:18 Outgoing Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
20180829 19:08:18 Incoming Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key
20180829 19:08:18 NOTE: --mute triggered...
20180829 19:08:18 1 variation(s) on previous 3 message(s) suppressed by --mute
20180829 19:08:18 I TUN/TAP device tun1 opened
20180829 19:08:18 TUN/TAP TX queue length set to 100
20180829 19:08:18 D do_ifconfig tt->did_ifconfig_ipv6_setup=0
20180829 19:08:18 I /sbin/ifconfig tun1 192.168.30.13 pointopoint 192.168.30.14 mtu 1500
20180829 19:08:18 /sbin/route add -net 185.22.174.xxx netmask 255.255.255.255 gw 192.168.0.1
20180829 19:08:18 /sbin/route add -net 0.0.0.0 netmask 128.0.0.0 gw 192.168.30.14
20180829 19:08:18 /sbin/route add -net 128.0.0.0 netmask 128.0.0.0 gw 192.168.30.14
20180829 19:08:19 I Initialization Sequence Completed
20180829 19:08:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:08:29 D MANAGEMENT: CMD 'state'
20180829 19:08:29 MANAGEMENT: Client disconnected
20180829 19:08:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:08:29 D MANAGEMENT: CMD 'state'
20180829 19:08:29 MANAGEMENT: Client disconnected
20180829 19:08:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:08:29 D MANAGEMENT: CMD 'state'
20180829 19:08:29 MANAGEMENT: Client disconnected
20180829 19:08:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:08:29 D MANAGEMENT: CMD 'status 2'
20180829 19:08:29 MANAGEMENT: Client disconnected
20180829 19:08:30 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:08:30 D MANAGEMENT: CMD 'log 500'
20180829 19:08:30 MANAGEMENT: Client disconnected
20180829 19:14:27 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:14:27 D MANAGEMENT: CMD 'state'
20180829 19:14:27 MANAGEMENT: Client disconnected
20180829 19:14:27 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:14:27 D MANAGEMENT: CMD 'state'
20180829 19:14:27 MANAGEMENT: Client disconnected
20180829 19:14:27 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:14:27 D MANAGEMENT: CMD 'state'
20180829 19:14:27 MANAGEMENT: Client disconnected
20180829 19:14:27 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:14:27 D MANAGEMENT: CMD 'status 2'
20180829 19:14:27 MANAGEMENT: Client disconnected
20180829 19:14:28 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180829 19:14:28 D MANAGEMENT: CMD 'log 500'
-----------------------

Seems, that it disconnects a lot...

Should I put 1460 as mtu instead of 1500.
Any suggestions what I forgot or could optimize?

Thanks,
JohnPain

Post Reply