Hi
In Windows works well, but with MacOS Catalina connects well to the VPN but the DNS doesn't resolves the webpages in the browsers, and the DNS doesnt's responds to ping. The Pulse Secure version is the last 9.1.4 (1761).
I've revised in Windows thought cmd and it reports the same data as in mac os: ip, gateway, dns and ip and dhcp is configured automatically in both systems, but in Mac OS can't browse in internet. If i put the google's ip in the address bar, so can avoid the DNS, webpage loads correctly.
Here i'm connected to the VPN and have external connection to the net:
% ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=54.598 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=54.505 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 54.505/54.552/54.598/0.046 ms
The first DNS are the right ones of my VPN's work:
scutil --dns | more
DNS configuration
resolver #1
nameserver[0] : 10.228.103.4
nameserver[1] : 10.228.103.27
flags : Request A records
reach : 0x00000002 (Reachable)
resolver #2
nameserver[0] : 8.8.8.8
nameserver[1] : 8.8.4.4
flags : Supplemental, Request A records
reach : 0x00000002 (Reachable)
order : 101600
Still well connected to the VPN, but the DNS doesn't respond to ping. In Windows the respond well.
% ping 10.228.103.4
PING 10.228.103.4 (10.228.103.4): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- 10.228.103.4 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
This is my ethernet and the ip address:
iMac ~ % ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 0c:4d:e9:d4:55:8d
inet6 fe80::145d:a167:bff4:3fe6%en0 prefixlen 64 secured scopeid 0x4
inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (100baseTX <full-duplex,energy-efficient-ethernet>)
status: active
These are the routing tables:
% netstat -nr
Routing tables
Internet:
Destination Gateway Flags Netif Expire
default 192.168.1.1 UGSc en0
10.7.40.71 10.254.27.26 UGHS utun3
10.7.40.72 10.254.27.26 UGHS utun3
10.7.40.73 10.254.27.26 UGHS utun3
10.228.230.250 10.254.27.26 UGHS utun3
10.254.26.252 10.254.27.26 UGHS utun3
10.254.26.253 10.254.27.26 UGHS utun3
10.254.27.26 10.254.27.26 UH utun3
93.191.138.95 10.254.27.26 UGHS utun3
93.191.138.96 10.254.27.26 UGHS utun3
93.191.138.97 10.254.27.26 UGHS utun3
93.191.138.184/29 10.254.27.26 UGSc utun3
93.191.142.138 192.168.1.1 UGHS en0
127 127.0.0.1 UCS lo0
127.0.0.1 127.0.0.1 UH lo0
169.254 link#4 UCS en0 !
192.168.1 link#4 UCS en0 !
192.168.1.1 link#4 UHCS en0 !
192.168.1.1/32 link#4 UCS en0 !
192.168.1.1 34:e8:94:b0:88:5e UHLWIir en0 782
192.168.1.100/32 link#4 UCS en0 !
224.0.0/4 link#4 UmCS en0 !
224.0.0.251 1:0:5e:0:0:fb UHmLWI en0
255.255.255.255/32 link#4 UCS en0 !
Any help would be aprecciated. Thank you !!
Do DNS servers need to be explictly added to split tunnel rules and ACL? This does not sound usual.
Is this a temp work around for some bug that Pulse is working on or is this permanent?
If I have to add the DNS servers IP under the VPN tuneling split tunneling policies and access control i'm not the system admin, i suposse that i have to tell him, as i can't change this from the client side.
I don't understand that in windows 10 it works well, and there is no DNS servers in the routing table.
This is the windows 10 routing table:
===========================================================================
ILista de interfaces
14...02 05 85 7f eb 80 ......Juniper Networks Virtual Adapter
11...08 00 27 b6 5e 2f ......Adaptador de escritorio Intel(R) PRO/1000 MT
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Adaptador ISATAP de Microsoft
16...00 00 00 00 00 00 00 e0 Adaptador ISATAP de Microsoft #3
===========================================================================
IPv4 Tabla de enrutamiento
===========================================================================
Rutas activas:
Destino de red M scara de red Puerta de enlace Interfaz M‚trica
0.0.0.0 0.0.0.0 10.0.2.2 10.0.2.15 10
10.0.2.0 255.255.255.0 En v¡nculo 10.0.2.15 266
10.0.2.15 255.255.255.255 En v¡nculo 10.0.2.15 266
10.0.2.255 255.255.255.255 En v¡nculo 10.0.2.15 266
10.7.40.71 255.255.255.255 En v¡nculo 10.254.27.27 1
10.7.40.72 255.255.255.255 En v¡nculo 10.254.27.27 1
10.7.40.73 255.255.255.255 En v¡nculo 10.254.27.27 1
10.228.230.250 255.255.255.255 En v¡nculo 10.254.27.27 1
10.254.26.252 255.255.255.255 En v¡nculo 10.254.27.27 1
10.254.26.253 255.255.255.255 En v¡nculo 10.254.27.27 1
10.254.27.27 255.255.255.255 En v¡nculo 10.254.27.27 256
93.191.138.95 255.255.255.255 En v¡nculo 10.254.27.27 1
93.191.138.96 255.255.255.255 En v¡nculo 10.254.27.27 1
93.191.138.97 255.255.255.255 En v¡nculo 10.254.27.27 1
93.191.138.184 255.255.255.248 En v¡nculo 10.254.27.27 1
93.191.142.138 255.255.255.255 10.0.2.2 10.0.2.15 10
127.0.0.0 255.0.0.0 En v¡nculo 127.0.0.1 306
127.0.0.1 255.255.255.255 En v¡nculo 127.0.0.1 306
127.255.255.255 255.255.255.255 En v¡nculo 127.0.0.1 306
224.0.0.0 240.0.0.0 En v¡nculo 127.0.0.1 306
224.0.0.0 240.0.0.0 En v¡nculo 10.0.2.15 266
224.0.0.0 240.0.0.0 En v¡nculo 10.254.27.27 256
255.255.255.255 255.255.255.255 En v¡nculo 127.0.0.1 306
255.255.255.255 255.255.255.255 En v¡nculo 10.0.2.15 266
255.255.255.255 255.255.255.255 En v¡nculo 10.254.27.27 256
===========================================================================
Rutas persistentes:
Ninguno
IPv6 Tabla de enrutamiento
===========================================================================
Rutas activas:
Cuando destino de red m‚trica Puerta de enlace
1 306 ::1/128 En v¡nculo
11 266 fe80::/64 En v¡nculo
14 261 fe80::/64 En v¡nculo
11 266 fe80::3d29:9aec:ef2e:7c9a/128
En v¡nculo
14 261 fe80::e0b7:df9c:7d80:a73d/128
En v¡nculo
1 306 ff00::/8 En v¡nculo
11 266 ff00::/8 En v¡nculo
14 261 ff00::/8 En v¡nculo
===========================================================================
Rutas persistentes:
Ninguno
@identityaws: That's the expected setting to be applied on the VPN server. DNS servers has to be added to the ST rules, however implicit ACLs can be enabled by selected the "Allow allow DNS settings" under the connection profiles.
@Gery : Based on the routing table, it seems that the tunnel mode is Split tunnel with the bunch of allow rules, so are you able to access both Internet and Intranet sites using FQDN from Windows but not on macOS?
Hi Ray
Using FQDN with those rules I'm able to acces both Internet and Intranet in Windows, but in macOS I only access the Intranet, can't access the Internet by the DNS resolution problem.
I've donde many tests but i can't found a solution. If I install a windows virtual machine in MacOS, to experiment with another Windows and it works well too.
My main computer is an iMac, and I would like to solve this problem, because I have to use two computer now to work at home.
Can you capture the packets on both physical and virtual interface and confirm how the DNS packets are being sent or are you receiving the DNS response for the DNS queries which are being sent out from the macOS workstations?
I've the logs in the Whireshark's format. Following the rules to not post links with the logs, i put some extract from them. I loaded in every try a wepage in the browser http//www.elpais.com.
I don't know if my enterprise has some GPO's to browse internet, and only can be applied to Windows machines, can be a problem with the FQDN (i've put the hostname as in windows, but I think MacOS could be adding .local behind the hostname) or where is the problem.
Logs Windows Physical Interface
MacOS Physical Interface