Dreaming of a single-cable docking station for my MacBook Pro, but not wanting to beta test the Belkin Thunderbolt dock, I decided to build my own using USB 3.0. This meant buying a sizable powered USB 3.0 hub (I chose the well-regarded Satechi “10 port” model) as well as a USB 3.0 Ethernet adapter. I already had a number of fantastic external drives, my Unicomp keyboard, and a (Bluetooth) “Tragic MacPad”.
Cable Matters USB 3.0 Gigabit Ethernet Adapter
Although Apple offers their own USB Ethernet adapter, it is USB 2.0 and 100 Mbps only. I wanted something faster than the 30 MBps those can manage. So I decided to take a look at the various USB 3.0 Gigabit Ethernet adapters on offer. It appears that most use the same chipset, made by a Taiwanese firm called ASIX, and thus would be similar apart from price.
My eye was eventually drawn to an inexpensive USB 3.0 Gigabit Ethernet adapter: Cable Matters SuperSpeed USB 3.0 to RJ45 Gigabit Ethernet Adapter in White. This adapter had fairly positive reviews from Mac users, and the price (US$20 with free Prime shipping) couldn’t be beat. So I took the plunge.
Despite the look of the packaging, this isn’t an Apple-grade device. It’s larger than Apple’s Thunderbolt Ethernet adapter and the white plastic has a cheap glossy (almost translucent) look that’s just a bit off. But that’s good enough for most users as long as it works.
Installation and Use
The first hurdle is drivers: This adapter’s chipset (ASIX’ AX88179) is not supported by Mac OS X. There’s a driver bundled with the adapter, but it’s on a CD-ROM – did Cable Matters miss the memo about Apple discontinuing optical drives?
Rather than dig out my portable SuperDrive, and because commenters on Amazon mentioned newer drivers, I fired up DuckDuckGo and searched for the latest driver from ASIX. Happily, it was easy to find the ASIX AX88179 driver page, which includes software for just about every OS you might run across. They even support Windows CE 6.0!
The driver is a DMG inside a zip file (?) with no auto-pop-up Finder window. It was an easy install, though the required reboot made me feel like I was back to using Windows.
After the reboot, I plugged in the adapter and connected my cable, but my Mac chose to use Wi-Fi instead of Gigabit Ethernet. A quick trip to System Preferences -> Network -> Set Service Order (in the gear drop-down) allowed me to prioritize the USB 3.0 adapter over my Wi-Fi network.
Once I changed the service order, everything appeared to be working smoothly. Wanting to test out the Ethernet adapter (and having video from Wireless Field Day 5 to post), I immediately started a 5 GB upload. A few hours later, I am pleased to report no trouble at all. I don’t really have the ability to stress test it at gigabit speed, but it seems stable and quick.
Warning: Illegal MAC Addresses!
Then I uncovered a serious annoyance: The MAC address.
I was checking out the connectivity in Network Utility when I noticed the MAC address used by this brand-new device. See above: It’s 00:00:00:00:02:d0. This might not matter to most people, but old-school geeks like me know that this is not a legal and kosher value. Cable Matters and ASIX seem to be playing fast and loose with their Ethernet setup!
Let me explain: Every Ethernet device has a MAC address, which is used to identify it on the network. This works below the IP addresses familiar on the Internet. The first three “octets” of an Ethernet MAC are the Organizationally Unique Identifier (OUI), and are set by the IEEE.
Since the MAC address is critical to sending Ethernet packets to the right place, every device on an Ethernet network must have a unique MAC address. Having an OUI doled out by the IEEE allows a vendor to manage their own MACs. If everything works as planned, every Ethernet device will have a globally-unique address. Cool, eh?
This is a fun way to identify devices at a glance: You can look up the first three octets using an IEEE tool and see who made any Ethernet device!
But take a look at 00:00:00 and tell me what you see! That’s right: This OUI belongs to Xerox, the originator of Ethernet. And 00:00:00:00:02:d0 is not a proper MAC address for a device made in 2013 by a company other than Xerox to use.
Duplicate MAC addresses can be seriously bad news. One saving grace is that, since it’s one of the earliest MAC addresses ever issued, the real 00:00:00:00:02:d0 probably looked a bit like this. So it’s unlikely to appear in the same network as my new Cable Matters device. In fact, it’s probably sitting in the back room at Weirdstuff or in a landfill.
ASIX punts responsibility for MAC addresses to the companies that use their chips. So when Cable Matters came calling with an OUI of “00:00:00”, I’m sure they didn’t bother to ask questions. They just set their machines to sequentially number their adapters starting at all-zeroes. As far as I can tell, Cable Matters doesn’t even have an OUI.
@SFoskett @Nick_Lowe @ioshints @etherealmind @CableMatters I see the same thing w/ mine, first time I have used it pic.twitter.com/T2YnNApoOd
— Ed Horley (@ehorley) August 13, 2013
Is this a problem? I raised the question with some knowledgeable folks on Twitter, and they weren’t all that concerned at this point. A collision with an ancient Xerox adapter is inconceivable, but I remain concerned that other ASIX-supplied adapters could reuse the same 00:00:00 range, leading to issues where a large number of these cheap Ethernet adapters are in use. And other manufacturers are likely doing the same thing.
Then there’s the IPv6 issue: The next-generation Internet Protocol uses the Ethernet MAC address as an interface identifier, and this is used across the whole Internet. Although a collision there remains unlikely since there are other elements to the global IPv6 address, we will likely see lots of archaic Xerox addresses out there in the wild.
Stephen’s Stance
Should you buy a Cable Matters USB 3.0 Gigabit Ethernet adapter for your Mac or PC? On the hardware and software side, it seems fine. Once the drivers are installed, it functions adequately. But I am deeply concerned that a vendor that would cut corners on the MAC address and OUI would cut corners other places, leaving me skeptical about the company and its products. Therefore, I cannot recommend this device.
Hi Stephen,
The use of the 00:00:00 MAC OUI is definitely concerning. As for IPv6 issues with it, both OS X and Windows 7/8 use an RFC 3041 privacy address for global Internet communications by default. They still auto-assign an EUI-64 address based on the MAC if the Router Advertisement specifies auto-config for use with a prefix. But across the network and Internet the privacy address is used with higher preference.
Cheers,
Andrew von Nagy
http://revolutionwifi.blogspot.com
I just bought the same device for the same reasons. Same complaint about the drivers – shipping with a CD, REALLY?? – but hadn’t noticed the MAC. Interesting. Mine shows up as 00:00:00:00:06:74, so certainly the bogus vendor ID isn’t something they’ve addressed as yet. Other than that, the adapter seems to function okay. I’ve been meaning to do a throughput test, but have not done so as yet.
All it takes is two of these low-end, fly by night vendors to do the same thing and then you’ll have conflicts especially in the IPV6 world of the future.
If I decide to try one of these out, I think I’ll pay a few bucks more and try one of the other vendors, and see if they play by the rules or not. I have no interest in lining the pockets of cheap, corner cutting companies that shouldn’t be allowed to sell their gear to the public.
I know you guys didn’t know about this when you bought them. But, thanks to this blog, I know, and I won’t be giving any money to them.
I found out the same thing after ordering a significant qty of these, then searched Amazon reviews for ‘OUI’ and found yours. After bringing the issue to their attention, they offered to replace my units (which I declined, since it wouldn’t affect my particular isolated usage), and they said the issue has now been corrected on inventory and future builds.
Forgot to mention – it was not intentional on their part, as the MAC addresses had already been purchased, just a coding error and lack of Q/A to catch it.
I was trying to do the same thing as you, I wanted a single-cable dock for my MacBook Air, but wasn’t too keen on the Belkin’s price tag. Got myself a nice USB3 hub and this gigabit adapter as well. One question though, not sure if you experience it. If I “hotplug” my MacBook into my “dock”, my gigabit adapter doesn’t get connected. If I want to use it I have to restart my MacBook. Does this issue affect you? Not a hub problem, because I also have a USB3.0 HDMI adapter hooked up to the hub for a second display and that works fine. Hhhmmm.
FWIW, I’ve found that if I’m a little patient when reconnecting my USB 3.0 hub, all the devices, including the Ethernet adapter, do come online. I have not timed it, other than to know that at first I thought I had an issue. Then later, I discovered that simply by waiting, all of the hub-attached devices showed back up. Seemed to be a problem only with my USB3.0 external HDD and the Ethernet adapter. The USB2.0 stuff shows up immediately.
I had an additional problem though. With an external HDD plugged into the hub, even though my gigabit network adapter still shows connected, I lose internet connectivity. It’s rather weird/troublesome, I ended up swapping back to the Apple ethernet adapter. It makes me wonder if perhaps that Thunderbolt dock’s price might well be worth the effort…
If you can get around to testing the speeds on this, that’d be great! Would be interested to see what these do when stress tested. -Brian
Does this change your overall conclusion about the product and its performance/price?
I checked on hwaddress.com and ASIX does have a block of MAC Addresses assigned to them.
00:0E:C6 00:0E:C6:00:00:00 – 00:0E:C6:FF:FF:FF
ASIX ELECTRONICS CORP.
I am guessing this is some manufacturing flaw in the way they are assigning the MAC addresses to their devices.
I got an Ethernet USB adapter like this (same chip inside, it says Edimax outside) and it has a correct MAC address, so maybe it’s a problem with the vendor really rather than the chip maker.
Have you had any issues with it overheating or dropping connections from being on for long periods of time ?
Don’t really care about the MAC issue since this will be on the inside LAN.
Thx