eFive25 - inaccessible

Ewon Support eFive
#1

I just spent a great amount of time trying to get a eWon Flexy 205 to talk to an eFive 25 on my network.

My eWon is a Flexy205 with a Wifi communication card FLB3271.

Altough i wasn’t able to open a VPN Tunnel with my actual eFive,
i have been able to open a VPN Tunnel pretty easily using Talk2M with eCatcher

When i was trying to connect to my eFive, thw eWon Flexy 205 web configurator disgnostic log didn’t have much detail about what was going wrong.

I then uploaded eGrabit and tried a one to one connection with the eFive and got the following log:

2022-05-24 14:28:13 WARNING: No server certificate verification method has been enabled. See How To Guide: Set Up & Configure OpenVPN Client/server VPN | OpenVPN for more info.
2022-05-24 14:28:13 LZO compression initialized
2022-05-24 14:28:13 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
2022-05-24 14:28:13 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
2022-05-24 14:28:13 Local Options String: ‘V4,dev-type tap,link-mtu 1574,tun-mtu 1532,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-client’
2022-05-24 14:28:13 Expected Remote Options String: ‘V4,dev-type tap,link-mtu 1574,tun-mtu 1532,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-server’
2022-05-24 14:28:13 Local Options hash (VER=V4): ‘d79ca330’
2022-05-24 14:28:13 Expected Remote Options hash (VER=V4): ‘f7df56b8’
2022-05-24 14:28:13 Socket Buffers: R=[65536->65536] S=[65536->65536]
2022-05-24 14:28:13 UDPv4 link local: [undef]
2022-05-24 14:28:13 UDPv4 link remote: 70.80.102.248:1194
2022-05-24 14:28:13 MANAGEMENT: >STATE:1653416893,WAIT,
2022-05-24 14:28:13 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:13 UDPv4 READ [-1] from [undef]: DATA UNDEF len=-1
2022-05-24 14:28:15 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:17 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:19 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:21 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:23 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:25 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:27 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:29 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:31 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:33 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:35 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:38 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:40 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:42 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:44 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:46 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:48 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:50 UDPv4 WRITE [14] to 70.80.102.248:1194: P_CONTROL_HARD_RESET_CLIENT_V2 kid=0 [ ] pid=0 DATA len=0
2022-05-24 14:28:52 NOTE: --mute triggered…
2022-05-24 14:29:12 10 variation(s) on previous 20 message(s) suppressed by --mute
2022-05-24 14:29:12 TCP/UDP: Closing socket
2022-05-24 14:29:12 SIGTERM[hard,] received, process exiting
2022-05-24 14:29:12 MANAGEMENT: >STATE:1653416952,EXITING,SIGTERM,

Do you have any idea what is going on and what is P_CONTROL_HARD_RESET_CLIENT_V2?
Regards!

#2

Did you follow the complete eFive setup guide? You may want to reset the device if you had it configured to connect to Talk2M because it will have an entirely different VPN configuration for that.

#3

It seem that i"m having hard time opening an OpenVPN session with my eFive
Can ou help me with the following log?
2022-05-25 09:13:20 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: /C=CA/O=TownName/CN=TownName_CA
2022-05-25 09:13:20 TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
2022-05-25 09:13:20 TLS Error: TLS object → incoming plaintext read error
2022-05-25 09:13:20 TLS Error: TLS handshake failed

#4

You can try setting ‘VPNDiag’ to 8 (High) in comcfg.txt to get more verbose VPN logs too. If you want to do that and share the backup (with support files), I can take a look at it.

#5

Hi Kyle,

Thanks for your followup.

Attached to this message the logs you requested with ‘VPNDiag’ to 8 (High) in comcfg.txt

Regards!

MOVED TO STAFF NOTE (52 KB)
#7

Can you please verify that the time and date are correct on the Ewon? It looks like you have NTP enabled, which will not work without an internet connection. Please set the time/date manually in the system wizard.