Initialization Sequence Completed

edited November 2018 in VPN Connection

When attempting to connect to HackTheBox's network via openvpn, the connection is established but it hangs in terminal. On my Access tab, it says I am connected from my IP, but obviously something is going wrong. Additionally, when I Ctrl+C the program HackTheBox still shows me as connected. I've tried stopping/restarting the openvpn, networking, and network-manager daemons and HackTheBox still shows me as connected. Only a full restart of my computer severs the connection as per HackTheBox (which means I'm probably missing a process somewhere). After a restart though, I still hang at "Initialization Sequence Completed".

Does anyone know what I need to do to fix this? Here are my logs. This is my first exposure to using openvpn so I'm not sure what I'm looking for. I don't see any errors though. If you need me to run any commands for more info I can do that as well.

OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 30 2018
library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
TCP/UDP: Preserving recently used remote address: [AF_INET]88.198.233.171:1337
Socket Buffers: R=[212992->212992] S=[212992->212992]
UDP link local: (not bound)
UDP link remote: [AF_INET]88.198.233.171:1337
TLS: Initial packet from [AF_INET]88.198.233.171:1337, sid=698ef724 6eb8d952
VERIFY OK: depth=1, C=UK, ST=City, L=London, O=HackTheBox, CN=HackTheBox CA, name=htb, [email protected]
VERIFY KU OK
Validating certificate extended key usage
++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
VERIFY EKU OK
VERIFY OK: depth=0, C=UK, ST=City, L=London, O=HackTheBox, CN=htb, name=htb, [email protected]
Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
[htb] Peer Connection Initiated with [AF_INET]88.198.233.171:1337
SENT CONTROL [htb]: 'PUSH_REQUEST' (status=1)
PUSH: Received control message: 'PUSH_REPLY,route 10.10.10.0 255.255.255.0,route-ipv6 dead:beef::/64,tun-ipv6,route-gateway 10.10.12.1,topology subnet,ping 10,ping-restart 120,ifconfig-ipv6 dead:beef:2::129a/64 dead:beef:2::1,ifconfig 10.10.14.156 255.255.252.0,peer-id 318,cipher AES-256-GCM'
OPTIONS IMPORT: timers and/or timeouts modified
OPTIONS IMPORT: --ifconfig/up options modified
OPTIONS IMPORT: route options modified
OPTIONS IMPORT: route-related options modified
OPTIONS IMPORT: peer-id set
OPTIONS IMPORT: adjusting link_mtu to 1625
OPTIONS IMPORT: data channel crypto options modified
Data Channel: using negotiated cipher 'AES-256-GCM'
Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
ROUTE_GATEWAY 10.7.47.254/255.255.252.0 IFACE=wlp1s0 HWADDR=30:10:b3:00:0b:f5
GDG6: remote_host_ipv6=n/a
ROUTE6: default_gateway=UNDEF
TUN/TAP device tun0 opened
TUN/TAP TX queue length set to 100
do_ifconfig, tt->did_ifconfig_ipv6_setup=1
/sbin/ip link set dev tun0 up mtu 1500
/sbin/ip addr add dev tun0 10.10.14.156/22 broadcast 10.10.15.255
/sbin/ip -6 addr add dead:beef:2::129a/64 dev tun0
/sbin/ip route add 10.10.10.0/24 via 10.10.12.1
add_route_ipv6(dead:beef::/64 -> dead:beef:2::1 metric -1) dev tun0
/sbin/ip -6 route add dead:beef::/64 dev tun0
WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Initialization Sequence Completed


openvpn --version
OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 30 2018
library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10

Hack The Box

Comments

Sign In to comment.