When it comes to Internet, you may be assigned a Public IPv4 address such as 230.195.239.223
or an IPv6 address like 2000:918f:1237:37d0:273:db24:82f8:3610
. You can verify this at https://test-ipv6.com/. However, for individuals who are not well-versed with technology, conveying these addresses can be error-prone and quickly becomes complex. Moreover, this method does not provide any historical data, especially when analyzing previous problems.
When accessing a website like https://harber-dooley.com, you first reach out to a DNS server to convert the host part (harber-dooley) in combination with the Top Level Domain (com) of the URL to an IP address, such as 110.239.137.129
. Every web request from your computer and browser includes the type of request, for example: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; AS; rv:11.0) like Gecko
The default gateway is typically an automatically configured address through DHCP. You receive a default gateway like 192.0.0.196
(although they usually end in .1 or .254 depending on the scope size), and this is where your computer sends all its traffic to be directed further. To check on Mac or Linux for IPv6
, there is a detailed guide available at how-to-fix-ipv6-connectivity/ but it can also be checked 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.196 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:af22:bdf2:91be:5f91%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): {156.230.50.117, 131.216.24.142} 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 b9:d0:e7:1c:e5:95 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 29:79:d1:fa:d8:a5 }
In the realm of physical and data layer connectivity, users may encounter problems with wired or wireless (Wi-Fi) mediums when trying to transmit data to their router.
Regardless of the version of OSX/macOS being used, whether it’s 10.14.5
, 11.2.9
, or 12.2.7
, there are various tools available for troubleshooting connectivity issues. However, these manual actions and scripts do not provide a continuous set of correlated values over time. In such cases, automated remote troubleshooting becomes essential, especially for teams that rely on remote work and the Work From Anywhere (WFA) concept.
A highly useful tool on OSX/macOS is sudo wdutil info
, which provides a dump of current wireless settings to the command line interface (CLI) and can be configured to generate specific logs for troubleshooting purposes. Moreover, the sysdiagnose
tool can be utilized to create a comprehensive range of logs, although much of it is only applicable at a specific moment in relation to wireless, similar to wdutil.
The command sudo nohup /usr/bin/sysdiagnose -u &
can be used to run the sysdiagnose tool in the background, writing logs to /var/tmp/<blah>.tar.gz
. If an interactive approach is preferred, the command sudo /usr/bin/sysdiagnose
can be executed, which will prompt a privacy warning. When not run in the background, it should open Finder in the correct location, allowing users to navigate to /var/tmp
or use Finder with Cmd+Shift+G to locate the path. Users should be mindful of the file sizes, generally around 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!