When using the Internet, you are assigned a Public IPv4 or an IPv6 address. You can verify this using test-ipv6.com. However, conveying these addresses to non-technical individuals or sharing MAC addresses can be challenging and error-prone. Furthermore, it doesn’t provide any historical data.
Accessing a website such as https://kozey.net involves contacting a DNS server to translate the URL into an IP address. Additionally, your computer and browser include information about themselves in every web request.
The default gateway is an automatically configured address obtained through DHCP. It serves as the destination for all your computer’s outgoing traffic. For IPv6, detailed instructions can be found on how-to-fix-ipv6-connectivity/, and can be checked on Mac or Linux with the following command:
netstat -rn -f inet | egrep -i "default|0/1|128.0/1"
0/1 172.18.12.193 UGScg utun3 default 192.0.0.160 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:d2c0:4c61:7ae6:c1c8%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): {194.157.97.237, 23.235.28.99} 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 54:ac:ce:32:64:a9 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:2e:95:96:ac:47 }
When it comes to transmitting data to your router, you might be using either a wired or wireless (Wi-Fi) medium at the physical and data layer.
Regardless of whether you are using OSX/macOS version 10.13.5
, 11.6.5
, or 12.1.7
, there are various troubleshooting tools available. However, these manual actions and scripts do not provide a series of correlated values over time. This is where automated remote troubleshooting becomes particularly useful, especially for teams that are embracing remote work and Work From Anywhere (WFA).
One 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. Additionally, the sysdiagnose
tool can generate a wide range of logs, although much of it is only point-in-time information in relation to wireless, similar to wdutil.
To run it in the background and write logs to /var/tmp/<blah>.tar.gz
, use the command sudo nohup /usr/bin/sysdiagnose -u &
. For interactive use, you can run sudo /usr/bin/sysdiagnose
and it will display a privacy warning. If not run in the background, it should open Finder in the correct location, or you can navigate to /var/tmp
using Finder with Cmd+Shift+G. 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!