Custom query (816 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 816)

Ticket Resolution Summary Owner Reporter
#1156 pending OpenVPN doesn't work on NAT64 panda@… warren@…
Description

OpenVPN Connect 2.1.3.120 connecting to an OpenVPN server with only an IPv4 address (vpn.snozzages.com) fails on NAT64 network.

#1155 worksforme ietf-hotel fails in Swissotel Clemens Schrimpe brian.e.carpenter@…
Description

I get a connection to ietf-hotel and it gives me v4 and v6 addresses, but it doesn't actually appear to forward packets anywhere - no DNS, I think, and no ping. Last night it was a bit different, it did resolve AAAAs but still no ping. The Swissotel WiFi? works OK, v4 only of course.

I was 2001:67c:1232:144:28cc:dc4c:9703:6781 and 169.254.103.129 on ietf-hotel

#1154 pending ietf-nat64 and Pulse Secure VPN panda@… tale@…
Description
When using ietf-nat64 with the Pulse Secure VPN I can't access network
resources from the other side of the VPN.  This is apparently because
Pulse is not updating the system nameservers so they still point to
the IETF v6 nameservers instead of the V4-only ones inside my company,
and thus I only get the externally-visible resolution (or lack
thereof).

Attempting to resolve this by updating the nameservers in System
Preferences -> Network -> Wi-Fi -> Advanced... did not fix the
problem, even after DNS cache flush, nor did updating
/etc/resolv.conf.  This honestly kind of surprised me; I really
thought updating them in System Preferences, though annoying, would
work.

I'm using Pulse Secure version 5.2.5 (build 869) on OS X 10.12.6 (Sierra).
Note: See TracQuery for help on using queries.