Hot and Bothered at Starbucks
Cruising for hotspots on a Linux Laptop can be a royal pain. It's not that we don't have good Wi-Fi support—we do—it's more that a lot of places offer free Wi-Fi with strings and dongles. My favorite coffee shop for working in, for example, offers free Wi-Fi to customers, and they control access by means of PCMCIA cards with the router set to allow only those MAC addresses. Leaving aside the fact that I have no way to install their Windows-only drivers, my laptop sports only an ExpressCard slot, so I'm pretty much screwed no matter what.
Of course, if I could find a way to get my paws on a device that gives me Wi-Fi wherever I go, this wouldn't be a problem. Imagine writing a shipwreck story on the beach where it takes place while still having access to all the glorious resources of the Internet to help make sure you have the details of tall ship rigging, local wildlife life cycles and edible plants at your fingertips. Or, if you're not a half-mad fiction writer, you still could use such a device to blog about a movie you're watching from the back row of the theater or about a protest from a park bench nearby and get the drop on other bloggers who will have to wait in line for a table at Starbucks.
I recently discovered, much to my delight, that such a device does exist. The Cradlepoint PHS300—PHS standing for Personal HotSpot—is a compact little router that, once turned on, establishes a solid wireless cloud suitable for use by anyone with a properly equipped laptop or other Wi-Fi-enabled device (www.cradlepoint.com/phs300/phs300.php).
Technically speaking, the PHS is a wireless router/firewall designed to work with 3G phones and EVDO devices. You plug said device in to the PHS's USB port and turn them both on, and (after a bit of tinkering) you have a wireless access point to the Internet.
Opening up the box, you'll find only the router itself, a small pamphlet, a battery and a power adapter. The package doesn't contain the extras that usually come with USB devices or computer parts. There isn't, for example, a driver disc or a manual, nor is there a USB cable for connecting the PHS to your 3G phone. In both cases, you're on your own.
Don't worry though; the small pamphlet actually contains all the information you're going to need. It's not terribly well organized (for example, you don't find out what the default router password is until several steps after you're told you need it), but it gives you the leg up you're looking for.
The router itself is small and light—not much bigger or heavier than a double-thick checkbook. It has three indicator lights: one tracks battery status, one lights up when a Wi-Fi cloud is established, and the final one indicates connectivity with the phone and/or EVDO modem when plugged in to the single USB port.
From there, the rest of the setup falls like a string of dominoes. Once the unit is powered up, use Wi-Fi Radar or GNOME Network to grab an IP address and log in to 192.168.0.1 to configure the router. Configuration is quite self-explanatory—about the only difference between this and setting up a normal SOHO router is the screen for configuring login information for your ISP, should it be necessary. All the current encryption standards, from WEP through WPA2, are supported.
The PHS300 is advertised as a universally compatible, secure, simple solution for emergency response, vacation broadband and mobile business. Both the box and the promotional materials give the impression that it's a product that “just works”.
I'm pleased to say that it performs as advertised.
It's not easy to imagine what they could have done better. The PHS300 is battery-powered, with about a two-hour battery life, and it recharges either over USB or via the power adapter. Because it operates like any other router appliance, it's not just useful for connecting to the Internet on the go. It also works well for setting up a proper network between your laptop and your colleague's, a little feature I've found useful recently while out on a film shoot. It handily supports full 802.11g speeds behind the Net gateway, and it has easy-to-administer traffic management to keep your cellular bandwidth usage well within the limits of your service plan.
I have only three gripes with this little marvel box, and two of them are pretty minor. The lack of an included USB cable is irritating—mostly because including such things is de rigueur in the current marketplace. The other minor quibble has to do with the battery light—namely, there isn't one. In fact, there's no way to know how much battery life you have left until the power light flashes red, which loosely translates to “this router will commit suicide in two minutes unless you plug it in to something from which it can draw power”. Still, in the grand scheme of things, it's a minor problem.
The major irritant is an oversight that keeps the PHS300 from completely knocking my socks off. The thing doesn't have an Ethernet port, and not having one limits its utility when in the presence of a wired uplink. It also makes it useless as an independent Net segment for diagnostic techs on a wired network. Alas, despite its otherwise brilliant potential as a WAP, the lack of one port pooches the deal, which is particularly disappointing since its little brother, the CTR350, has one. Paying more for less isn't exactly my idea of a good time; however, the PHS300 makes up for it with the firmware's bandwidth management and load-balancing abilities, which maximize the speed you get over your 3G device. Used as a 3G router, its transfer speeds outperform both the CTR350 and using a 3G phone or modem directly from your laptop.
Despite this, it's an excellent little appliance, quite reasonably priced, and (at this point) it's one of only two battery-powered travel routers on the market (the other being Cradlepoint's CTR350). If you have a use for one, it's worth picking up and supporting a company that's advertising is Linux compatibility—and living up to it!
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide