AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() They also never tell you what they're doing. (In general, I feel, those things never do. OS X has the troubleshooter dialog, but that's never been able to fix the problem. 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. 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. ![]() There's no way I'll remember it, and if you're reaching for it, you likely can't Google it. System/Library/PrivateFrameworks/amework/Versions/A/Resources/airport -s 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, My 2013 Macbook Pro is terribly slow to associate to even nearby APs, and drops the connection often. OS X has most of your standard tools, though some in some odd places, e.g., printing the routing table not being done with `route`.įurthermore, I care. I loathe debugging network troubles in Windows, because there is essentially no information. It's much more difficult to do that on other OSs, especially Windows. It's possible to get advanced output from various command line tools in Linux, and it's possible to get networking information. Again why? There is no good central low-level log file or debug tool that lets me see what is going on. Why? Does the AP suggest it, or is it my configuration? Sometimes I can't enter a text password, it only accepts a fixed-length hexadecimal string (happens on Windows a lot). Sometimes I know a connection is WPA2, but it stubbornly tries another encryption method. Or I'd like some way to see whether receiving or sending is the problem - do I get garbled packets, or do I get good ones, but no answers to the ones I send. ![]() Why? I'd like to see something like "sent 100 low level packets, checksum failed on 88 of them, disconnecting". I never know where to start when debugging a bad connection, and I wouldn't know where to start if I wanted to improve Linux WiFi.įor example, sometimes I can see a network, but can't connect. It just connects and you get some bars, or it doesn't. You get no low-level and no debugging information. One problem is that WiFi is completely opaque, especially but not only on Linux. ![]()
0 Comments
Read More
Leave a Reply. |