Thanks for the reply. I can ping the server but it isn't routing my normal internet traffic through the VPN. I assumed that this was related to the DTLS but perhaps not. Alex David Woodhouse <dwmw2 at infradead.org> writes: > On Tue, 2016-09-27 at 18:33 -0500, Alex Branham wrote: >> >> >> I'm attempting to connect to my school's vpn and it's not working >> quite as I imagined.I run "sudo openconnect vpn.utexas.edu" and >> enter in my username, password, and two-factor authentication. It >> then prints out: >> >> Got CONNECT response: HTTP/1.1 200 OK >> CSTP connected. DPD 0, Keepalive 20 >> Set up DTLS failed; using SSL instead >> Connected as 172.29.230.252, using SSL >> >> And this gets added to the output of "ip addr": >> >> 4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1406 qdisc fq_codel state UNKNOWN group default qlen 500 >> link/none >> inet 172.29.230.252/32 scope global tun0 >> valid_lft forever preferred_lft forever >> inet6 fe80::d2fa:6c92:c9ee:d6d/64 scope link flags 800 >> valid_lft forever preferred_lft forever >> >> I'm running Arch linux with openconnect v7.07. Any help is much appreciated! > > Can you elaborate on what it is that you didn't expect? > > Is it just the lack of DTLS? Is everything actually working apart from > that? > > Or do you not have routes to the VPN? Can you not ping machines on the > VPN by their IP address? > > Or do you not have DNS? > > Or did a pixie jump out from under the table at this point and run away > with your laptop...? -- J. Alexander Branham PhD Candidate Department of Government University of Texas at Austin www.jabranham.com
