How Can I Fix Apple No-access
Understanding IP Addressing
When accessing the internet, you are assigned with a Public IPv4 or IPv6 address. The IPv4 address appears like 112.122.51.61, while an IPv6 address is formatted as 2000:f07d:7df2:b77:80c4:8f70:2f17:3930. To verify your address, you can visit https://test-ipv6.com/. However, for those who are not technically inclined, sharing or memorizing these addresses, as well as MAC addresses like 68:6b:27:09:20:7a, can be prone to mistakes and can become complex. Moreover, no historical data is provided, particularly during past issues.
Navigating to Websites
When visiting a website, such as https://jacobi.org, your computer initially communicates with a DNS server to translate the URL’s host portion (jacobi) and its Top Level Domain (org) to an IP address, such as 134.191.249.208. Notably, your computer and browser send its type along with all web requests, for example:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.75.14 (KHTML, like Gecko) Version/7.0.3 Safari/7046A194A
Significance of Default Gateways
The default gateway, usually obtained through DHCP, is an automatically configured address. This gateway, like 192.168.169.21, serves as the routing destination for all traffic from your computer. In the case of IPv6, detailed instructions can be found at how-to-fix-ipv6-connectivity/, and you can perform checks on Mac or Linux using:
IPv4 Routes and the Host IPv4 Route Table (inc. VPN)
netstat -rn -f inet | egrep -i "default|0/1|128.0/1"
0/1 172.18.12.193 UGScg utun3 default 192.168.169.21 UGScg en0 128.0/1 172.18.12.193 UGSc utun3
Note: We are not just looking for the default but also for any VPN that overrides the public v4 address space.
IPv6 Routes and the Host IPv6 Route Table (inc. VPN)
netstat -rn -f inet6 | egrep -i "default|2000::/3"
If you have IPv6 active the above should return at least one route (as per below) via a known interface such as “en0 " on a Mac.
default fe80:be40:60e6:b53b:5498%en0 UGcg en0 default fe80::%utun0 UGcIg utun0 default fe80::%utun1 UGcIg utun1 default fe80::%utun2 UGcIg utun2 2000::/3 utun3 USc utun3
Note: We are not just looking for the default but also for any VPN that overrides the public v6 address space.
Debugging DHCP for both IPv4 and IPv6
To get a look at the low level DHCP configuration (Mac/Linux):
ipconfig getpacket en0
...
domain_name_server (ip_mult): {28.79.205.206, 182.162.241.23}
end (none):
...
So, in the above we are not getting IPv6 DNS servers from the DHCPv4 reply but…
ipconfig getv6packet en0
DHCPv6 REPLY (7) Transaction ID 0x80940b Length 76
Options[4] = {
CLIENTID (1) Length 14: DUID LLT HW 1 Time 668691856 Addr 68:6b:27:09:20:7a
DNS_SERVERS (23) Length 32: 2606:4700:4700::1111, 2001:4860:4860::8844
DOMAIN_LIST (24) Length 0: Invalid
SERVERID (2) Length 10: DUID LL HW 1 Addr e7:c3:3b:54:e9:e9
}
Resolving Connectivity Issues for Wired and Wireless Connections
When it comes to sending data to your router, you may be using either a wired or wireless (Wi-Fi) medium at the physical and data layer.
Troubleshooting Solutions for Apple macOS / OSX
Regardless of whether you are using OSX or macOS versions such as 10.14.3, 11.5.2, or 12.0.5, there are various tools available for troubleshooting connectivity issues. However, these manual actions and scripts do not provide a comprehensive set of correlated values over time, which is where automated remote troubleshooting becomes extremely beneficial, especially for teams that adopt remote work and the Work From Anywhere (WFA) approach.
Effective Built-in Tools for Troubleshooting
A useful tool on OSX/macOS is sudo wdutil info, which provides a dump of the current wireless settings to the command line interface and can be configured to generate specific logs for troubleshooting purposes. Additionally, the sysdiagnose tool can be used to generate a wide range of logs, although many of these are only point-in-time data, similar to wdutil.
To run sysdiagnose in the background and generate logs in /var/tmp/<blah>.tar.gz, you can use the command sudo nohup /usr/bin/sysdiagnose -u &. Alternatively, if you want to run it interactively, you can use sudo /usr/bin/sysdiagnose, which will open Finder in the correct location. However, be aware that the file sizes can be around 300MB.
Possibly Helpful Videos
P.S. Tips For Remote Network and Client Support
Digital work requires reliable connectivity. Whether for low latency or regular data streams, Wi-Fi, DNS, and network issues cause teams to lose time and productivity. Even worse is when support teams waste time trying to recreate and isolate issues! See how PanSift saves time, money, and frustration on all sides with instant remote troubleshooting 🏠🏝🛰.
