eJPT help

Hi,

I know quite a few of you guys have taken this and I was really keen to do this one too however Im struggling with this one and wondered if a couple of you might be so kind as to help? Unfortunatley elearnsecurity does not have the best support when you are struggling

First off Im not too familiar with Linux/Kali but can find-ish my way around. Once I actually get into the labs I should be fine.

Have installed a brand new version of kali linux to a HDD
Have turned off router firewall ( so should be no blocking of traffic and I know the ISP should allow traffic anyway as we use openvpn at work and I dont have to reconfigure any of my remote users routers ) SHOULDNT HAVE TO DO THIS AND ALSO HAD FIREWALL ON AND 1194 upd/tcp ALLOWED

I have installed as far as I know openvpn by following several different webpages as elearnsecuritys instructions are vague ( to say the least )

I have the lab running

I have saved the VPN key into the root directory , I have renamed the file to Traffic_Sniffing_613.ovpn

I am typing from a terminal openvpn Traffic_Sniffing_613.ovpn it is asking for my credentials

I am then faced with the below
oot@desktopkali:~# ls
Desktop Music Traffic_Sniffing_613.ovpn
Documents Pictures Videos
Downloads Public
'HTTP(S)_Traffic_Sniffing_613.ovpn' Templates
root@desktopkali:~# openvpn Traffic_Sniffing_613.ovpn
Tue May 22 10:31:33 2018 OpenVPN 2.4.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 4 2018
Tue May 22 10:31:33 2018 library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.08
Enter Auth Username: triplea
Enter Auth Password: ********
Tue May 22 10:31:44 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:31:44 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:31:44 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:32:44 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:32:44 2018 TLS Error: TLS handshake failed
Tue May 22 10:32:44 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:32:49 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:32:49 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:32:49 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:33:49 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:33:49 2018 TLS Error: TLS handshake failed
Tue May 22 10:33:49 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:33:54 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:33:54 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:33:54 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:34:54 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:34:54 2018 TLS Error: TLS handshake failed
Tue May 22 10:34:54 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:34:59 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:34:59 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:34:59 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:35:59 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:35:59 2018 TLS Error: TLS handshake failed
Tue May 22 10:35:59 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:36:04 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:36:04 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:36:04 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:37:05 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:37:05 2018 TLS Error: TLS handshake failed
Tue May 22 10:37:05 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:37:15 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:37:15 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:37:15 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:38:15 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:38:15 2018 TLS Error: TLS handshake failed
Tue May 22 10:38:15 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:38:35 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:38:35 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:38:35 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:39:35 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:39:35 2018 TLS Error: TLS handshake failed
Tue May 22 10:39:35 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:40:15 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:40:15 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:40:15 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:41:15 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:41:15 2018 TLS Error: TLS handshake failed
Tue May 22 10:41:15 2018 SIGUSR1[soft,tls-error] received, process restarting
Tue May 22 10:42:35 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]162.254.149.248:33651
Tue May 22 10:42:35 2018 UDP link local (bound): [AF_INET][undef]:1194
Tue May 22 10:42:35 2018 UDP link remote: [AF_INET]162.254.149.248:33651
Tue May 22 10:43:36 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue May 22 10:43:36 2018 TLS Error: TLS handshake failed
Tue May 22 10:43:36 2018 SIGUSR1[soft,tls-error] received, process restarting

If anyone can assist or suggest what to test I would be very grateful.

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

Danielm7

I know I had similar behavior when I tried to connect from work and we were blocking OpenVPN, it was being recognized as "proxy avoidance" by the firewall.

triplea

we use openvpn in work as far as I know along with UTM9 and I've never heard any users need a change in their ISPs router ( as I said Ive tried both the ISP router firewall off completly and tried it with 1194 up and tcp as allowed

dont think there is any blocking by default on a new kali linux install

so cant see where the block would be?

for ref Im just at home with a single PC and standard ISP router - no complicated setup

tedjames

I always logged into the lab from home and never had a problem. It wouldn't have flown at work.

ansionnachcliste

https://openvpn.net/index.php/open-source/faq/79-client/253-tls-error-tls-key-negotiation-failed-to-occur-within-60-seconds-check-your-network-connectivity.html

Most likely one of the first two.

Just to be clear, you're not virtualising Kali? It's booted from a HDD?

Any proxies in between your network and the internet?

triplea

Tried to do kali on a virtualbox originally but apparently theres alot of issues.

What I did find out in the end is you need a new VPN key EVERY time you run a lab, even if its the same one. Just wasnt clear at all in the guides.

Problem seems fixed now and even though it was a waste of 10 odd man hours with every thing I tried to tick off got to look at it as a positive and say well at least I remember what my linux intro course taught me even if Ive not been on linux for 6 months.

Cheers all

tedjames

triplea wrote: »

What I did find out in the end is you need a new VPN key EVERY time you run a lab, even if its the same one. Just wasnt clear at all in the guides.

Odd. While I didn't need a new key every time, it seemed that at random times, I would need new keys. It wasn't consistent for me. Really weird flaw.