When using the Internet, you are assigned a Public IPv4 address, such as 238.110.21.27
, or an IPv6 address like 2000:63cb:7ca:1ff2:34fd:ba81:2740:93e9
. You can verify your address by visiting https://test-ipv6.com/. However, communicating these addresses, including MAC addresses like ab:3d:db:aa:69:2c
, can be challenging for those who are not tech-savvy and can become complicated quickly. Furthermore, this method does not provide any historical data, especially regarding previous issues.
When attempting to access a web page, such as https://kohler.net, the initial step involves reaching out to a DNS server to translate the host portion (kohler) and the Top Level Domain (net) of the URL into an IP address, such as 95.222.184.78
. Your computer and browser always communicate their type with each web request, for example:
Mozilla/5.0 (Windows; U; Win 9x 4.90; SG; rv:1.9.2.4) Gecko/20101104 Netscape/9.1.0285
By default, your gateway is assigned an automatically configured address through DHCP, such as 172.18.6.10
. In most cases, these addresses end in .1 or .254, depending on the scope size. This is the location where your computer sends all of its traffic to be routed onwards. For IPv6
, a detailed guide on how-to-fix-ipv6-connectivity/ is available, and you can check on Mac or Linux using the following command:
netstat -rn -f inet | egrep -i "default|0/1|128.0/1"
0/1 172.18.12.193 UGScg utun3 default 172.18.6.10 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:c8e2:90d:192d:919e%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): {140.48.247.246, 100.174.243.194} 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 ab:3d:db:aa:69:2c 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 04:65:42:fb:3f:ef }
When it comes to sending data at the physical and data layer, you have the option to use either a wired or wireless (Wi-Fi) medium to transmit the data to your router.
No matter which version of OSX/macOS you are currently using, whether it’s 10.11.9, 11.5.7, or 12.1.8, there are various troubleshooting tools available. Unfortunately, the manual actions and scripts may not provide a series of correlated values over time. This is where automated remote troubleshooting becomes invaluable, especially for teams that have embraced remote work and Work From Anywhere (WFA) practices.
One extremely useful tool on OSX/macOS is the sudo wdutil info
command, which provides a dump to the CLI of current wireless related settings. This can also be configured to generate specific logs for troubleshooting purposes. Additionally, the more comprehensive sysdiagnose
tool can be used to generate a wide range of logs, although much of the information is only relevant to wireless at a specific point in time, similar to wdutil.
Running sudo nohup /usr/bin/sysdiagnose -u &
in the background will produce logs in /var/tmp/<blah>.tar.gz
for you. If you prefer to run it interactively (although there is not much interaction), you can use the commandsudo /usr/bin/sysdiagnose
, which will prompt a privacy warning. When not run in the background, it should open Finder in the correct location, or you can navigate to /var/tmp
using Finder or use Cmd+Shift+G to point Finder to the path. Be cautious of the file sizes, which are typically 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!