When using the Internet, you might be assigned a Public IPv4 address such as 4.46.81.233
or an IPv6 address like 2000:7f43:5b7f:85e8:ab30:4729:afd3:ac95
. This can be verified at https://test-ipv6.com/. However, explaining and conveying these addresses, or even referring to MAC addresses like a5:63:16:a2:62:42
, can be prone to errors and becomes complex. Moreover, this method does not provide historical information (especially when past issues occurred).
In order to access a webpage such as https://mraz.name, a DNS server is first contacted to convert the host portion (mraz) combined with the Top Level Domain (name) of the URL, to an IP address like 84.232.228.126
. Your computer and browser actually sends its type with all web requests e.g. Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.75.14 (KHTML, like Gecko) Version/7.0.3 Safari/7046A194A
Typically, your default gateway is an automatically assigned address via DHCP. A common default gateway is 192.0.0.245
(although they usually end in .1 or .254 depending on the scope size) and this is where your computer directs all its traffic to be routed onwards. For IPv6
we offer an in-depth guide on how-to-fix-ipv6-connectivity/ but you can verify on Mac or Linux with:
netstat -rn -f inet | egrep -i "default|0/1|128.0/1"
0/1 172.18.12.193 UGScg utun3 default 192.0.0.245 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:1b4a:17cc:ede0:33e6%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): {221.203.32.156, 6.230.251.248} 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 a5:63:16:a2:62:42 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 41:61:c3:0a:37:0c }
When it comes to transmitting data to your router, you might be using a wired connection or a wireless (Wi-Fi) medium at the physical and data layer.
Regardless of whether you are operating on OSX/macOS version 10.11.8
, 11.2.1
, or 12.1.5
, there are various troubleshooting tools available. However, these manual actions and scripts do not provide a consistent set of correlated values over time. This is where automated remote troubleshooting becomes invaluable, particularly for teams that are accustomed to remote work and the concept of Work From Anywhere (WFA).
One extremely useful tool on OSX/macOS is the sudo wdutil info
command, which provides a dump of current wireless settings to the CLI and can also be configured to generate specific logs for troubleshooting purposes. Furthermore, the sysdiagnose
tool can be used to generate a wide range of logs, although much of it is time-specific in relation to wireless settings, similar to wdutil.
Running sudo nohup /usr/bin/sysdiagnose -u &
in the background will produce logs that are saved to /var/tmp/<blah>.tar.gz
. If you prefer to run it interactively (even though there isn’t much interaction), you can executesudo /usr/bin/sysdiagnose
, which will trigger a privacy warning. When not run in the background, it should open Finder in the appropriate location, or you can manually navigate to /var/tmp
or use Finder with Cmd+Shift+G to locate the path. Just be mindful of the file sizes, which are approximately 300MB give or take.
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!