The first thing you need to do to start using the airport command is to make a symbolic link to it. Make a symbolic link to the airport utility The ‘airport’ command-line tool, however, doesn’t really have anything to do with AirPort AP’s, it’s an Apple command-line management tool, regardless of the vendor of AP to which you are connected. And, like pretty much everything Apple does, it is seamless and simple. The AirPort Utility allows you to manage Apple AirPort (and Time Capsule) access points from your Apple devices.
#Osx airport utility for free
They have moved away from this and these days most people associate the word “airport” with Apple’s line of access points and/or with the AirPort Utility that is built-in to OSX (and available for free download on iOS). In older versions of OS X (Snow Leapord and older) Apple referred to its client WLAN internals as airport. Yes, you can quickly open it using Spotlight or a third party tool like Alfred. Terminal is nestled in the Applications > Utilities folder and is even more elusive in Launchpad because Apple renamed the “Utilities” Launchpad folder to “Other” a few years back. OSX is designed to be a graphical OS, using its CLI for daily tasks is not desired. I fully expect that this is also by design. One such CLI tool is ‘airport’.Īpple’s built-in CLI tool, Terminal, is not made abundantly visible. But command line tools for OSX are there, hiding. And to that end, Apple has succeeded (as have Microsoft and most common Linux distros). Connecting to a WLAN should be as simple and as seamless as my mom needs it to be. They focus on GUI-driven usability to an enormously diverse group of users who don’t care how WLANs work, only that they work. Apple, on the other hand, does not trumpet the command line offerings of its OS. Netsh, in particular, is an especially powerful tool. Over the years Microsoft has grown into an OS that has a very feature-rich CLI. All one needs to do is tap into the power of netsh to see what I mean. Microsoft offers a good bit of configuration capability and info gathering from the command line.
And while I would appreciate a lot of additional detail in my interfaces I recognize that they are not necessary to the desired end result: to get connected to the WLAN.
#Osx airport utility windows 7
Daily use desktop OS’ like Windows 7 and Mavericks are designed for everyday (non-technical) users, not for me. But that simplicity is not a shortcoming it is by design. As a wireless networking and security expert I have always been annoyed with the wireless configuration interfaces provided by both Apple and Microsoft.
#Osx airport utility professional
I still stay up to date on Windows OS’ but only out of professional necessity. Windows desktop OS, from a personal perspective, is dead to me. But I, like a lot of other people, was born and raised on Microsoft OS’ and for years I would look down and spit on the ground every time Apple was mentioned ( Paul Simon reference intended). Microsoft die-hards hate such statements and will have their own choice words for people that say or write things like that. Like most Mac users I love the “it just works” functionality that OSX brings to the table.
0 kommentar(er)
