Can we bond (with Manage Virtual Interfaces, or similar) across an USB Ethernet dongle and the Airport Wifi
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?
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.
You may be a little crazy for wanting this...I guess I never saw it as a problem. For my Mac users, the network interface priority is Ethernet > Wireless. For most users in the office, they'll pickup wireless. If they physically plug in, the Ethernet connection takes over. Is there any reason your users switch back and forth? In my environment, the wireless network has shorter lease times and the DNS records are scavenged... but what is the exact problem? The presence of duplicate entries?
I looked into just this issue a year or two ago (OS 10.6.x IIRC) and found that bonding across interfaces was a driver-level limitation in either the wireless driver or the ethernet driver, I can't remember which, and could only be done with expensive 3rd party software. Looks like it may have been fixed in 10.7 per http://docs.info.apple.com/article.html?path=Mac/10.7/en/mchlp2798.html (which only talks about eth, but may be able to handle wireless too, though you might have to drop down to the terminal to enable it)