Can we bond (with Manage Virtual Interfaces, or similar) across an USB Ethernet dongle and the Airport Wifi

bondingmac-osxnetworking

We've got a Macbook Air (Actually, we've got some Airs, Some Pros and some iMacs). We've got a consistently annoying problem, which is that when they connect to our DHCP server, they've actually got 2 different IP addresses, and that causes 2 different IP addresses to get set in our DHCP lease file, as well as 2 in our DNS (automagically updated).

On linux workstations with multiple NICs, we bond/team them into bond0 and set the MAC address by hand to be equal to one of the NICs in the bond.
This pretty much fixes all the associated ballache.

I just tried to bond the NICs on the Air, using Manage Virtual Interfaces (Advanced settings in Networking, under the little gearwheel in the Adaptors list).
I could add eth0 (the USB Ethernet dongle) to the bond just fine, but the wireless Airport adapter didn't show up.

Is it not possible to bridge across the interfaces in this way?

Is there another way to do it?

Are we crazy for wanting to do it this way? Is there a better way?

Best Answer

Unfortunately, to the best of my knowledge, no Wi-Fi card used by Apple in a Mac has ever supported LACP. Using the terminal you can easily confirm whether or not your various interfaces can be aggregated with the following command: networksetup -isBondSupported (interface)

In my case, using a Mid-2010 MacBook Pro running 10.7, I get the following:

$ networksetup -isBondSupported en0
YES
$ networksetup -isBondSupported en1
NO

Where en0 is Ethernet and en1 is AirPort.

Related Topic