Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

jasonmvp

macrumors 6502
Original poster
Jun 15, 2015
422
345
Northern VA
Hey Gang -

This is an odd one, and maybe it belongs in the Catalina section vs the Mac Pro one. I rebooted my 7,1 after installing another PCI-E M.2 adapter (not NVMe ... it's a lot slower). When it came up, the wireless icon in the menubar had an exclamation point in it. Hm. That's... peculiar.

I have that interface active only for AirDrop, and its IP address is set manually. It appears to be working; I can ping it from other machines on the same LAN.

Code:
joker$ ping 192.168.10.11
PING 192.168.10.11 (192.168.10.11): 56 data bytes
64 bytes from 192.168.10.11: icmp_seq=0 ttl=64 time=143.000 ms
64 bytes from 192.168.10.11: icmp_seq=1 ttl=64 time=109.043 ms
64 bytes from 192.168.10.11: icmp_seq=2 ttl=64 time=77.845 ms
64 bytes from 192.168.10.11: icmp_seq=3 ttl=64 time=40.876 ms
64 bytes from 192.168.10.11: icmp_seq=4 ttl=64 time=107.176 ms
64 bytes from 192.168.10.11: icmp_seq=5 ttl=64 time=75.946 ms
64 bytes from 192.168.10.11: icmp_seq=6 ttl=64 time=41.290 ms
^C
--- 192.168.10.11 ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 40.876/85.025/143.000/34.691 ms

And from the box itself, it sees en2 just fine:
Code:
harleyquinn$ ifconfig en2
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=400<CHANNEL_IO>
    ether f8:ff:c2:0d:a4:af
    inet6 fe80::471:d45d:a155:4d5a%en2 prefixlen 64 secured scopeid 0x1c
    inet 192.168.10.11 netmask 0xffffff00 broadcast 192.168.10.255
    nd6 options=201<PERFORMNUD,DAD>
    media: autoselect
    status: active

AirDrop works as well. But the exclamation point remains in the icon. I've yet to reboot the box again to see if that clears it. Running the Diag app on it doesn't return any interesting info. And nothing jumps out at me in /var/log/wifi.log.

Thoughts?
 
Interesting. I don't have a default route set for this interface. I don't ever want the Mac Pro to use the WiFi interface for any outbound traffic to my local LAN, whatsoever. And that appears to be the reason why I have a "!" in my WiFi icon; I just hadn't noticed it previously. Even though the WiFi interface is working fine, apparently if it doesn't have a default route set (manually or via DHCP) it complains.

That's a bit... silly.
 
  • Like
Reactions: OkiRun
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.