Why is ip Command Not Found?
On macOS, the ip command is not available by default. Instead, you should use macOS networking tools.
Here’s how to run the same checks on macOS:
🛠 Step 1: Check Your VPN-Assigned IP Address
Since ip a doesn’t work on macOS, use:
ifconfig
• Look for an interface named utunX (e.g., utun0, utun1, etc.).
• It should have an IP in the OpenVPN Cloud subnet (e.g., 10.10.0.X).
utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet 100.96.1.35 --> 100.96.1.33 netmask 0xfffffff0
inet6 fe80::4094:6ecf:6884:8142%utun4 prefixlen 64 scopeid 0x1f
inet6 fd:0:0:8102::3 prefixlen 64
nd6 options=201<PERFORMNUD,DAD>
mbam2@MBAM2 ~ %
✅ If you see an OpenVPN Cloud IP, continue to Step 2. YES
❌ If not, OpenVPN Cloud isn’t assigning an IP correctly.
🛠 Step 2: Check If You Can Reach UniFi Ultra
Since ping works the same on macOS, test:
ping -c 4 10.10.0.1
• If it works, OpenVPN Cloud is routing traffic to UniFi Ultra.
• If it fails, OpenVPN Cloud isn’t forwarding your connection properly.
PING 10.10.0.1 (10.10.0.1): 56 data bytes
64 bytes from 10.10.0.1: icmpseq=0 ttl=64 time=2.413 ms
— 10.10.0.1 ping statistics —
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.285/2.364/2.413/0.048 ms
mbam2@MBAM2 %
✅ If this works, continue to Step 3. IT DOES
❌ If it fails, OpenVPN Cloud needs a routing rule for 10.10.0.0/24.
🛠 Step 3: Check If Your Laptop Can Reach the Internet
Test if internet-bound traffic is working:
ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
Request timeout for icmpseq 0 ^C
— 8.8.8.8 ping statistics —
4 packets transmitted, 0 packets received, 100.0% packet loss
mbam2@MBAM2 %
FAILS
• If it works, OpenVPN Cloud is forwarding traffic out correctly.
• If it fails, UniFi Ultra is not NAT-ing OpenVPN traffic properly.
✅ If ping works, continue to Step 4.
❌ If it fails, we need to check NAT/firewall rules.
🛠 Step 4: Check If OpenVPN Cloud is Forwarding Traffic
Since traceroute works on macOS, run:
traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 40 byte packets
1 unn-138-199-20-67.datapacket.com (138.199.20.67) 11.547 ms 11.816 ms 12.139 ms
2 no.rdns.ukservers.com (81.92.218.4) 32.406 ms 33.932 ms 33.222 ms
3 100.96.1.18 (100.96.1.18) 38.425 ms 35.562 ms 36.719 ms
4 ^C
mbam2@MBAM2 %
• If it stops at OpenVPN Cloud (100.96.X.X),IT DOES OpenVPN Cloud is not forwarding internet traffic.
• If it stops at UniFi Ultra (10.10.0.1), UniFi Ultra is blocking or failing to NAT traffic.
🛠 Step 5: Check Your Public IP
Reconnect OpenVPN Cloud and test:
curl ifconfig.me
• Expected Result: It should show 212.132.163.2 (your UK public IP).
• If it still shows a Swiss IP, OpenVPN Cloud is not routing internet traffic correctly.
🚀 Next Steps
• What test fails?
• Does OpenVPN Cloud assign an IP (ifconfig check)?
• Can you ping 10.10.0.1?
• Can you ping 8.8.8.8?
• What does traceroute 8.8.8.8 show?
Once you test these, we’ll pinpoint the issue! 🔧🚀
More Musings 