When using the Internet, you are assigned a unique public IPv4 or IPv6 address such as 19.10.135.100
or 2000:de0d:12fa:ac2f:17a5:382c:129e:195
. You can verify this by visiting https://test-ipv6.com/. However, translating and communicating these addresses, as well as MAC addresses like da:7f:97:e0:ce:63
, can be complex for individuals without technical expertise. Moreover, it does not provide any historical data pertaining to previous issues.
When attempting to access a website such as https://nitzsche-streich.name, your computer first connects to a DNS server to convert the URL’s host (nitzsche-streich) and Top Level Domain (name) to an IP address, such as 185.244.27.145
. Additionally, your computer and browser send their specifications with each web request, for example:
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.36
The default gateway is typically an automatically configured address obtained through DHCP, such as 10.177.239.147
(commonly ending with .1 or .254 depending on the scope size). This is where your computer sends all its traffic for further routing. Insights on resolving IPv6
connectivity issues can be found in our detailed guide how-to-fix-ipv6-connectivity/. For Mac or Linux users, the default gateway can be checked using:
netstat -rn -f inet | egrep -i "default|0/1|128.0/1"
0/1 172.18.12.193 UGScg utun3 default 10.177.239.147 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.
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:5f9b:5765:f22:5691%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.
To get a look at the low level DHCP configuration (Mac/Linux):
ipconfig getpacket en0
... domain_name_server (ip_mult): {230.211.51.66, 74.110.80.19} 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 da:7f:97:e0:ce:63 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 10:08:5e:2e:e2:ea }
When it comes to transmitting data to your router, you may be using either a wired or wireless (Wi-Fi) medium at the physical and data layer.
Regardless of the version of OSX/macOS you are using, whether it’s 10.14.1
, 11.4.5
, or 12.3.9
, there are various tools available for troubleshooting. However, these manual actions and scripts do not provide a series of correlated values over time. This is where automated remote troubleshooting becomes valuable, especially for teams that embrace remote work and Work From Anywhere (WFA).
One valuable tool on OSX/macOS is the sudo wdutil info
, which provides a dump of current wireless settings to the CLI and can be configured to generate specific logs for troubleshooting. Additionally, the sysdiagnose
tool can be used to generate a wide range of logs, although many of them are only point-in-time data in relation to wireless, similar to wdutil.
To run the sysdiagnose tool in the background and write logs to /var/tmp/<blah>.tar.gz
, use the command sudo nohup /usr/bin/sysdiagnose -u &
. If you prefer to run it interactively, use the command sudo /usr/bin/sysdiagnose
, and it will give a privacy warning. When not run in the background, it should open Finder in the correct location, or you can navigate to /var/tmp
or use Finder with Cmd+Shift+G to locate the path. Keep in mind that the file sizes are approximately 300MB.
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 🏠🏝🛰.
2 x free macOS agents
No registration, immediate live demo!