By Collin Allen

IceKey in Black

March 11, 2007

My favorite keyboard, the IceKey by MacAlly, is now available in black to match Apple’s product lineup. Though I already have one IceKey, I might just have to order the black version for my PC, as well! You can never have too many low-profile, laptop style keyboards around. I couldn’t recommend this keyboard any higher, particularly if you enjoy typing with the tactile feedback of Apple laptop keys.

Installing DD-WRT on a WRT54GL

February 12, 2007

After running into continued troubles with my Linksys WRT54G v5 router, I decided to make a change in my network setup. In the past, I have had great success with Linksys devices, but lately I’ve found that my router keeps dropping packets, causing Safari to report “You are not connected to the internet.” Updating the firmware on the router seemed to have no noticeable effect.

A while back, I had checked out some open-source firmware for Linksys routers called DD-WRT, and I decided to give it a shot. Unfortunately, the WRT54G v5 router has had some limitations imposed, both in memory and CPU speed, so that particular model is incapable of running the full DD-WRT installation.

Though Apple’s recently updated AirPort Extreme base station will be shipping soon, I decided to replace my router with a new WRT54GL. The ‘L’ model has more resources to dedicate to the firmware. I like Apple’s base stations, but I also value the web-based interface of nearly all other routers. Apple requires a Mac-only AirPort configuration program, and I like being able to make a quick change from a PC or Mac using just a simple web browser. The replacement I chose is also substantially cheaper than Apple’s – $65 vs $179.

Upon opening the box, I promptly set aside everything except the router itself and the power cable. To this day, I’m still not entirely sure what’s on those CDs that come with them, as I just plug it in an configure it using a browser. The default Linksys firmware was the target for replacement, and here’s a step-by-step rundown of what I did to overwrite it with DD-WRT.

  1. Check the router’s hardware version by looking at the sticker underneath. Version 1.1 is easer in that it does not require you to first load the ‘mini’ version to enable additional memory. Mine was v1.1, so I went straight for the DD-WRT v23 SP2 Standard generic” firmware.
  2. Turn off AirPort on my PowerBook so that I’m not attempting to talk to the wrong router or over the potentially unstable wireless connection.
  3. Plug into the new router via Ethernet – Mac Ethernet to any router LAN port, 1 through 4.
  4. Check the IP assigned to the Mac by opening System Preferences, Network, Built-in Ethernet, TCP/IP tab. It gave me, which is well within the standard .100+ DHCP range. DHCP looks to be working as expected.
  5. Visit the WRT54GL administration interface by browsing to in Safari, logging in as admin/admin. Logged in successfully, everything seems to be working here, also.
  6. To ensure the configuration is completely cleared, hold the small reset button on the back of the device for a full 30 seconds. Let it boot up again.
  7. Re-visit the administration interface, and go to the Firmware Upgrade page.
  8. Browse for the dd-wrt.v23_generic.bin firmware binary file, and hit Upgrade.
  9. Wait for the device to re-flash itself and report complete. Don’t touch that Continue button. Just wait 5 full minutes. Then unplug power from the router.
  10. Hold the reset button again, while plugging power back in. Continue holding the reset button for 30 seconds, just like before. Let the router boot up once more (the power LED will stop flickering when it’s booted).
  11. Visit the new DD-WRT administration interface, again at The new login and password are root/admin.

So far, DD-WRT has proven very stable, and provides plenty of advanced controls. I might have to turn off DHCP on my old router and just use it as a 4-port switch!

Update: After several months of using DD-WRT full time, I’m happy to report that it’s one of the most stable pieces of software I’ve ever used. It’s provided outstanding router uptime and performance, with plenty of features. I’ll be keeping it as my default firmware for the forseeable future!

Mac Meet Xbox: Part 3.1

February 11, 2007

Networking a Mac and an Xbox can sometimes be troublesome, occasionally involving unusual network setups, so I decided to publish this little Mac Meet Xbox addition to better cover the subject. Having in-depth, detailed knowledge of networking isn’t necessary, but some basic concepts are key in keeping Xbox Media Center updated with new builds and fresh content.

For most, there are two main ways of attaching your devices: using a router as a central network hub, and wired Ethernet using a “crossover cable.” Both ways work, and the choice is up to you depending on your existing network setup or personal preferences.

Key Networking Technologies

Before you can begin learning about the details of the specific scenarios, a little foundation knowledge will go a long way towards helping you understand how each setup works.

The most common method of getting your Xbox and Mac talking to each other is with the use of a home internet router, be it wired or wireless. To be a router, your networking hub must have some core functionality that’s found in all routers, which includes IP distribution, internet splitting, and switching. Every router or internet gateway you can find on store shelves today will offer these features and more, so you generally don’t need to worry whether or not your particular router does these things.

IP distribution, the fancy-sounding Dynamic Host Configuration Protocol, or more commonly called “DHCP” is the core of the router’s functionality, automatically providing IP addresses to connected computers. When a computer is connected and set to automatically find an IP address, it talks to the router and negotiates assignment of an IP address. When accepted, the computer can talk to others on the same network. Apple likes to call DHCP “Automatic” in many cases, and static “Manual.” They’re just friendlier-sounding words compared to the alphabet soup that is most computer terminology.

Usually, the main goal in purchasing a router is to “split” a single broadband internet connection into many connections, allowing multiple computers and devices access to the internet. The router achieves this using a technology called Network Address Translation (NAT), in which it modifies all packets destined for the internet to have the address of your cable or DSL modem, not the internal IP address of your computer assigned by its DHCP server. Outbound packets have a note made of them in its memory, so when the response packet comes back from the internet, the router looks up which computer it should go to. It’s a clever technology that allows multiple devices to masquerade as one, and your ISP is none the wiser.

Finally, the last major feature that routers inherently provide is switching. Switching is nothing more than intelligent data moving, which has the side effect of making things more secure. Networking technologies of several years ago relied on hubs, which are actual devices, compared to the more general “central location” hub referred to above. A hub was just a device that allowed multiple computers to talk to each other by means of simply shouting at everything connected. When data was sent into a hub, it went out every other port in an attempt to reach the destination computer. If the destination was within reach, it, too, would shout back, keeping all the other attached computers within “earshot.” Any computer attached but not involved in the shouting match as it were, could keep a record of both sides of the conversation, which is bad for security. Switching avoids this problem by keeping track of the port through which each computer is reachable. If necessary, more than one switch can be involved, yet each knows its role in getting the data to the destination without involving other computers. This not only cuts down on potential eavesdropping, but reduces overall network congestion – computers no longer have to wait for the shouting to stop to get their packets on the network.

Why Use a Router with XBMC?

With all the fancy features provided by a router, what applies to getting Xbox Media Center off the ground? At the very least, it gets you and your Xbox an internet connection. For your computer, the internet use is obvious, but Xbox Media Center also uses the internet to get weather, RSS news feeds, IMDB movie information, and more. Simply plugging in your Xbox and computer will get you that much by relying on the DHCP capabilities of the router.

The Router Setup

Most home routers are very straightforward – plug the device into wall power, run Ethernet from your cable or DSL modem the the Internet/WAN port, and run Ethernet to your Mac and Xbox. If your Mac has an AirPort, AirPort Extreme, or other wireless card installed and your router has antennae, you’ll also have the option of just linking up your Mac wirelessly. Both Ethernet and wireless work, and the only noticeable difference is data transfer speed. When copying a 700 MB movie to your Xbox, Ethernet speeds will blow away wireless (at least until 802.11n becomes more popular). After all the devices are connected and powered up, the router will assign them IP addresses, and everything will have internet access and the ability to communicate with each other.

You can view your Mac’s IP address by opening your Mac’s System Preferences, Network, Built-in Ethernet, TCP/IP tab, shown here:

mac automatic ip settings

And just like you’d expect from the Mac, that’s it! No other setup is needed. To connect to your Xbox, you’ll need to find out its IP address, which you’ll FTP into to transfer movies, music, games, or whatever media you choose to play. Boot your Xbox and simply scroll down the main list and highlight the Settings tab. On the right, the assigned IP address will be displayed:

xbmc settings main page

As you can see, the IP is given, which is the same address you would use to connect using Transmit or other preferred FTP client. Using a router makes networking your hardware very easy, especially with the DHCP capabilities that do all the legwork for you.

Why Use a Crossover Cable with XBMC?

A router is usually the most universal way to use XBMC, however there are times and setups where you may not have 24/7 internet access, a router is too far away, or you’re simply in a rush to copy a file over. A crossover cable is a relatively common piece of network cabling, which “crosses over” the “talk” and “listen” wires, making one device talk directly into the other’s listen connection, and vice versa. In doing so, the need for a router or wired switch is made unnecessary. This setup will yield the fastest overall transfer speeds, however a router really doesn’t introduce a noticeable delay.

Crossover Cable Setup

Hooking up your Mac and Xbox via a crossover cable is as simple as plugging it into the Ethernet ports on both machines. Unlike the router setup, though, they can’t immediately communicate. Both the Mac and the Xbox are normally set to use DHCP to get an IP address. As you recall, the router provides this service, but it’s no longer in the picture, so the devices therefore can’t receive IP addresses without some additional setup. To make the configuration as easy as possible, you can set both devices to have static/manual IP addresses, as opposed to automatic.

Once connected, visit the Mac’s Network settings (again, System Preferences, Network, Built-in Ethernet, TCP/IP tab). Change the “Configure IPv4” popup menu to Manually, and a number of fields will become editable. Fill in an IP address such as, and a Subnet Mask of A router isn’t used in this setup, so the Router and DNS Servers fields can be left blank. Here’s a screenshot of a properly configured Ethernet interface on the Mac side of the network:

crossover settings

Unless you’re sharing an internet connection under the Sharing system preference pane, static is the only option for a crossover cable setup. And, quite frankly, setting all your networked devices to static IPs is probably a good choice in any arrangement if you intend to be interacting with them regularly. You’ll always know which IP to connect to in order to get to the machine you expect. (On my home network, I personally use a router with DHCP enabled, but have all my computers and Xboxes set with static IP addresses so I know where each is when I need to talk to it. Any other computers, such as my fiancee’s laptop, simply get an IP assigned via DHCP when it connects.) Hit “Apply Now” to invoke the new IP setup, and your Mac will be configured.

Next, boot up your Xbox running XBMC and open its Settings page. Highlight the Network tab if it’s not already selected, and move the selection over the Assignment up and down arrows, and choose “Manual (Static)”, as seen below:

xbmc network settings

Once “Manual (Static)” is chosen, you can move the selection down to the IP Address field and type in the desired IP address using the little onscreen number pad. Choose something reasonable (an ending number anywhere between .2 and .254), and one that’s not the static IP of your Mac. That last bit is important – the two devices absolutely must have different IPs, or else they’ll be fighting for control and probably both end up disconnected until you change one of them.

xbmc ip settings

Once you’re done typing an IP, press the “E” key onscreen to Enter your settings. Step back out of the Network settings using the Back button on your controller or remote, and head back to the main XBMC menu. For good measure, reboot your Xbox using the red button in the lower-right corner, and it will start up fresh with the static IP set exactly how you typed it. You’re then ready to connect via FTP using that IP, and start loading up content, browsing around the Xbox filesystem, or updating Xbox Media Center!

I hope this networking tutorial shines some light on what seems to be a trouble spot for many a new Xbox modder. If you still have questions, feel free to post a comment using the form below.

Mac Meet Xbox: Navigation

Part 1: Why Xbox + Choosing Chips

Part 2: Cracking the Case + Installing and Flashing

Part 3: Installing XBMC

Part 3.1: Networking in Detail

Nike+iPod Internals

January 21, 2007

Curious how the Apple/Nike+ iPod accessory set works, the hackers over at SparkFun have taken apart both the shoe insert and the iPod receiver. You can check out all the details here, including some discussion of the hardware choices Apple made.

Interestingly, the shoe insert is transmit-only, whereas the little white gadget that plugs into the iPod’s dock connector has a chip capable of both reception and transmission. With the right hacking, it might be possible to get iPods to talk to each other over a short range – surely not fast enough to transfer music, but “now playing” info is within the realm of possibility.


January 19, 2007

Amit Singh, author of the excellent book Mac OS X Internals, has published a Mac version of FUSE, a kernel extension that allows various data structures to be “remapped” as a local file system. Even internet-dependent sources like Flickr photo albums, RSS feeds, and remotely-connected SSH sessions can be represented as files in a folder. If you’ve never seen technology like this before, this video demo shows just how cool this stuff is. There’s already a FlickrFS extension that can be implemented with FUSE, so it shouldn’t be too much trouble to implement it on the Mac, making Flickr photo managing as easy as drag-and-drop. After backing up my current system (this is unsupported software), I’ll try installing MacFUSE and a handful of plugins.