Open Wireless Diagnostics in /System/Library/CoreServices/Applications, then click Window -> Utilities. Gives lots of detailed info, frame capture, logging, etc.
https://www.dropbox.com/s/2ndc35q0gxynffl/Screenshot%202014-...
You can access it easier by holding down the "option" key and selecting the Wifi menu http://imgb.mp/jxy.jpg
>I disagree. It's possible to get advanced output from
various command line tools in Linux
dont worry, Lennart Poettering (systemD/pulseaudio) is working to solve this problem
Re:The sad state of Linux Wi-Fi
by jaseemabid on Thursday July 24, 2014 @08:49AM
(#8079310)
Sarcasm?
Re:The sad state of Linux Wi-Fi
by stevenhuang on Saturday July 26, 2014 @04:11AM
(#8089207)
Oh man, the audio problems I sometimes had with pulseaudio...
airport -s is incredibly important in setting up roaming correctly with heterogeneous APs. You absolutely want SECURITY column to be identical, else devices won't roam.
> There's no way I'll remember it
I have history(1) and a symlink in a toolbox git repo.
> you likely can't Google it
"!g OSX airport command" works fine
> route
I found netstat -r is the most "Unix-portable" way of querying the routing table (Windows route is a peculiar beast anyway). route is deprecated on linux in favor of ip route.
> > you likely can't Google it
> "!g OSX airport command" works fine
Of course. The parent was referring to a situation when someone lacks internet access, due to a networking problem they are trying to fix, rendering them unable to use Google to find the command.
Furthermore, I care. My 2013 Macbook Pro is terribly slow to associate to even nearby APs, and drops the connection often. I have no idea why, because it is opaque: how do you list nearby APs? their signal strength or encryption type? I didn't learn this until just now, and it's,
Seriously. There's no way I'll remember it, and if you're reaching for it, you likely can't Google it. And it appears to be deprecated. It's a much shorter command in Linux, and in general I find it easier to determine if the problem is the network connection or DHCP failure. IIRC, Network Manager's icon changes — admittedly not much – depending on which one it's on, so even without command line tools, I have some idea what's going on.OS X has the troubleshooter dialog, but that's never been able to fix the problem. (In general, I feel, those things never do. They also never tell you what they're doing. For all I know, they're just progress bars and timers.) WiFi off, WiFi on fixes a lot of problems.