Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Multi homing is a networking timesaver Network
I have saved a lot of time by using the dual homing cpabilities of OS X - that is, its ability to connect to two networks at the same time. My home network uses a DSL connection and all the printers are wireless, but I prefer a wired cable modem connection when I am at my desk. OS X happily connects me to the internet at the faster cable modem speed, but allows me to print over the AirPort connection to my home network printers.

In my previous occupation, I was able to work on both the office network and through a wireless internet link; the OS just found what I needed on whatever network was required. No muss, no fuss, and no juggling of connections. I am set up to connect automatically to available networks, although AirPort does ask before joining any untrusted access points.

[robg adds: Though not exactly a hint in and of itself, not everyone may know that OS X can use two network connections at once, so I thought it worth publishing this...]
    •    
  • Currently 2.00 / 5
  You rated: 1 / 5 (4 votes cast)
 
[13,795 views]  

Multi homing is a networking timesaver | 12 comments | Create New Account
Click here to return to the 'Multi homing is a networking timesaver' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Multi homing is a networking timesaver
Authored by: digitol on Sep 01, '06 07:37:48AM

Should probably include how to setup multihoming. In the shortest way I can describe it; You can Duplicate your Port Configurations in your Network Preference Panel. So if you have Only One built-in ethernet port, you can click the duplicate button and in a sense have a virtual or two ethernet configs running at the same time. Cool stuff. In Fact all of OS X's networking just blows the doors off anything windows has to offer....as if that was anything to brag about! :) hehehhehe.



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: Coumerelli on Sep 01, '06 08:23:55AM

exactly. what this amounts to is the 'it just works' mantra. What OS X does is typical of any LAN/WAN router insomuch as it looks at the object (printing, in this case) and asks itself, "Self, where does this info need to go? Oh, to the printer? then out the wireless it goes" Otherwise it'll say, "Ahh, you want to access a file on your network share, eh? And the fastest way to get there is through that wire right there."

Again, not that Windows can't or doesn't do this. Just, with OS X the only 'configuring' is connecting to the actual network. no setting priorities or going through wizards and junk.

Good f.y.i.

---
"The best way to accelerate a PC is 9.8 m/s2"



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: davegoulden on Sep 04, '06 12:54:58PM

I don't think this works with Airport only. I have 2 networks (Airport snow and Airport Express which can't do a WDS together) - I don't think I can be on both at once, or can I?



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: ghay on Sep 01, '06 09:39:23AM

Don't get me wrong, I dislike windows very much, but it's networking in recent oses is just as good as Mac. Ok, a little more complex to setup, but consider network bridging, on windows, highlight two network interfaces right click and select "bridge..." - done.

Now do that on a Mac, without the terminal.
And no, internet sharing is NOT the same thing.



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: sapridyne on Sep 02, '06 06:24:09AM

Okay...

View Network Port configurations, click New, under Port choose Link Aggregate, choose the ports.



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: JackSloth on Sep 04, '06 07:05:11PM

huh? I don't have that option in my ports menu



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: rspeed on Sep 28, '06 07:35:43PM

You need to have at least two interfaces.



[ Reply to This | # ]
no locations
Authored by: kholburn on Sep 03, '06 07:54:33PM

Windows networking is simply not as good as Mac networking for at least one reason "locations".



[ Reply to This | # ]
Not as smart as it sounds
Authored by: avramd on Sep 01, '06 10:17:57AM

I just wanted to clarify for people who read this that there is no special magic going on here. Apart from some Rendezvous/Bonjour peripherals, OS X and Windows do the exact same thing, and OS X can not intelligently choose one connection over the other.

The only choice it can make is to look at the network address of the device you are trying to reach, and see if it is in a subnet that is directly connected to one of your non-primary interfaces. This is what all IP hosts have done since long before Mac OS 7 could even do TCP/IP. Beyond that it has to pick one default gateway as being the primary, and it uses it for everything.

The people describing these situations just happen to have a situation where everything they need to get to over their secondary interface actually is on the same subnet as that interface, and they do not need to go through any routers on that interface. OS X could run software to figure that out too, but it is not in there by default, and most network admins would hang you if you tried to get your computer to participate in their routing domains.

I love to tell people about how macs "just work" as much as the next guy, but in this case, Windows "just works" too.

The only thing that is special in this respect on the mac is the ability to swap out entire network configuration sets with the Location feature. That is great and windows can't touch it. But these days most networks have automatic addressing (DHCP), and you don't end up needing the Locations feature on them. Windows works just as well here. In both cases you sometimes need to poke the interface to get it to discover its new address, although I do find that the poking is required more often on Windows than on Mac.



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: felix-fi on Sep 01, '06 01:44:37PM

Having 2 network interfaces "active" is nice... but sometimes it creates some problems. At work, I have both airport and ethernet active, when I do a backup with rsync, Mac OSX does not always use the fastest interface (despite the fact that this interface (ethenet cable) is the first one in the list in the pref. panel). Often I have to shutdown the airport to make sure the internet cable get used. Similarly, some program (such as Xmeeting) have trouble to route traffic back when 2 interfaces are active...



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: Jaharmi on Sep 05, '06 10:59:15AM

This may happen if you try to use an application before the routing tables are updated. In my informal testing, I give about 10 sec before I attempt to use any connections for new traffic after I do something that affects an interface -- such as plug in or remove my Ethernet cable. This is on a PowerBook G4 17-inch 1.33 GHz system with Mac OS X 10.4.7, but YMMV.

You can check your routes by using "netstat -r" at the command line in Terminal. The "default" one is the one that should be used for your new traffic.



[ Reply to This | # ]
Multi homing is a networking timesaver
Authored by: dorianshints on Sep 03, '06 12:49:24PM

Actually, the Location feature in OSX is extremely usefull as it allows a mobile user to access different locations that work thru Proxies.

Windows does not allow and it's auto proxie config usually needs intervention as has been the case with many users at the office.

My vote goes to OSX on this one...



[ Reply to This | # ]