0
In another thread, it was suggested that the way to bridge two Ethernet ports on a Mac running Mountain Lion was to run the following:
sudo ifconfig bridge0 create
sudo ifconfig bridge0 addm en0 addm en1
sudo ifconfig bridge0 up
It works great! But I can't access the machine that is doing the bridging from the machine behind it. I'm smart enough to discern the answer might have to do with "static routes" and "netmasks," not smart enough to understand how these work. Anyone care to break it down?
Chris Z-S
Posted 2013-09-27T15:33:04.010
Reputation: 1
If you are really creating an ethernet bridge (which it looks like you are), then routes and netmasks are not the answer. Ethernet works at OSI layer 2 - routes and netmasks are at the ip layer, which is OSI layer 3. -- as to what the actual problem is, not sure, but it's likely a bug in the MacOS networking stack. If one of the ethernets is wifi, note that the original article you mention says it is not reliable on wifi. – Dan Pritts – 2013-09-27T16:04:49.933
Any chance you could link the original post in your question for reference? – DanteTheEgregore – 2013-09-27T16:11:10.303
Yep, Zach, I did just that. – Chris Z-S – 2013-09-27T16:39:11.133