Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

How can I bridge two wired ethernet interfaces on Mac OS X (e.g. the current MacPro comes with two ethernet ports)?

Googling turned up (e.g. this Apple forum post and this openvpn post) that this is fairly easy on Linux (using the brctl command) and under Windows (via Network Connections > right-click > Bridge Connections), but how is it done under Mac OS X?

BTW: There also doesn't seem to be a macport for brctl ('port search brctl' didn't turn up any results)

Note: I don't want to have 'internet sharing', which creates a new network (by handing out network addresses in a new range). I want to really 'bridge' two interfaces so to keep the same network subnet.

share|improve this question
    
You need to explain what your end goal is. The links you provided don't help. As the first link's response post says, "I cannot fathom what it is you are trying to do here." –  Stu Thompson Sep 16 '09 at 18:42
    
As the first link did, I am afraid that I have to suggest to look up 'network bridge' if you're not familiar with the concept. As a simplified summary, i want to use a Mac as a sort of hub. –  Rabarberski Sep 16 '09 at 19:01
1  
Time to reevaluate answers, since the accepted one is from 2009. :) –  sjas Jan 19 at 19:07

3 Answers 3

up vote 7 down vote accepted

If you want to build a real Ethernet bridge (Layer 2 bridge) on Mac OS X, answer is, you simply can't without third-party software. That's just the way it is, there is nothing in the kernel or in userspace to do this.

The only software I know capable of doing this is IPNetRouterX, which is not free. Never tried it myself.

share|improve this answer
    
The answer I was looking for. Thanks! –  Rabarberski Sep 17 '09 at 4:59

As of Mountain Lion, you can configure bridges using ifconfig:

sudo ifconfig bridge0 create
sudo ifconfig bridge0 addm en0 addm en1
sudo ifconfig bridge0 up

See man ifconfig for more options.

It doesn't work well with wifi interfaces however due to how they handle lookups.

share|improve this answer
    
As for the edit that should've been a comment: I assume you're not on Mountain Lion (10.8.x). Please check again that you are. –  Per Johansson Oct 2 '12 at 11:08
    
I happen to be having trouble with wifi -- can you give me any more data on why it doesn't work well? –  a paid nerd Nov 8 '13 at 15:56

a bit late, but this feature is called "bond" in OS X: see

networksetup -h | grep -i bond
networksetup -isBondSupported <hardwareport>
networksetup -createBond <bondname> <hardwareport1> <hardwareport2> <...>
networksetup -deleteBond <bonddevicename>
networksetup -addDeviceToBond <hardwareport> <bonddevicename>
networksetup -removeDeviceFromBond <hardwareport> <bonddevicename>
networksetup -listBonds
networksetup -showBondStatus <bonddevicename>
share|improve this answer
4  
Isn't bonding something different? As far as I know, bonding means taking two interfaces together to increase the bandwith (see e.g. the wikipedia entry en.wikipedia.org/wiki/Channel_bonding ) –  Rabarberski Mar 27 '11 at 8:20
    
your right … it was misleading .. and didn't work btw. The closest thing i've found was: hintsforums.macworld.com/showthread.php?t=107086 but the driver "lagg" is not available on OS X Client. –  boecko Apr 21 '11 at 7:50

protected by studiohack May 21 '11 at 0:51

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.