|
Replies
:
3
-
Pages
:
1
-
Last Post
:
Sep 12, 2008 6:14 AM
by: BobHarris
|
|
|
Posts:
23
From:
Dallas
Registered:
Oct 7, 2007
|
|
|
|
Leopard multihoming and failover
Posted:
Sep 11, 2008 7:19 PM
|
|
|
I want to be able to use multihoming in Leopard to set up redundant IP access. I have a number of Macs that have both ethernet and Airport connections. I have them connected to an Airport Extreme N with both ethernet and Airport using DHCP with manual (static) IP addresses.
If I leave both interfaces on with the same IP addresses with ethernet as first in service order, would it cause any problems? Or would ethernet failover to Airport when it is disconnected? Please note I do not want the IP addresses to change when failover occurs.
Thanks.
MacBook Pro
Mac OS X (10.5.4)
|
|
Posts:
2,293
From:
New England, USA
Registered:
May 13, 2005
|
|
|
|
Re: Leopard multihoming and failover
Posted:
Sep 11, 2008 8:12 PM
in response to: jamalm
|
|
Helpful
|
|
|
At home, I setup my MacBook with fixed IP addresses. I configure the Airport and build-in ethernet interfaces with the same IP address (the Firewire interface as well).
Normally I use Airport, but if I'm copying a large file and decide I want to get better performance, I just take my MacBook over to the router and plug in an ethernet cable. My transfer speed jumps from WiFi speeds to 100baseT speeds.
If I remove the ethernet cable, my transfer speed drops back to WiFi speeds.
NOTE: This is all the same huge file transfer switching interfaces sometimes just for fun.
Is that what you desired?
MacBook 2GHz, PowerMac Dual G5/2.5GHz, Mac mini intel Dual Core 2/1.83Ghz
Mac OS X (10.5.3)
I also manage: 12" iBook G4/1GHz, iMac G4/1.25GHz
|
|
Posts:
23
From:
Dallas
Registered:
Oct 7, 2007
|
|
|
|
Re: Leopard multihoming and failover
Posted:
Sep 11, 2008 8:27 PM
in response to: BobHarris
|
|
|
Yes, this is what I was talking about. Do you have the same static IP address on both Airport and ethernet or is it variable by DHCP? When I tried to do this in Tiger, I had networking problems with at least one software. I was hoping leopard is better.
MacBook Pro
Mac OS X (10.5.4)
|
|
Posts:
2,293
From:
New England, USA
Registered:
May 13, 2005
|
|
|
|
Re: Leopard multihoming and failover
Posted:
Sep 12, 2008 6:14 AM
in response to: jamalm
|
|
|
Do you have the same static IP address on both Airport and ethernet or is it variable by DHCP? When I tried to do this in Tiger, I had networking problems with at least one software. I was hoping leopard is better.
I use the same fixed IP address on Airport and Ethernet interfaces.
You MUST have the same IP address, otherwise existing connections will be broken. With the same IP address the router just switches traffic to the newly declared primary interface.
NOTE: I Have used this trick since the Mac OS 8 days, when I got my first Graphite Airport Base Station, and I was using a 56K dial-up ISP service. And this includes all the releases of Mac OS X.
My environment:
I use a Manually TCP/IP setup. Not much different from a DHCP with manual IP, except I need to enter the router IP address, my own mask (255.255.255.0) and my DNS server IP addresses (which I got by looking at /etc/resolv.conf while using a DHCP setup, or using the OpenDNS.org DNS servers). But then again, I don't see any reason why this would not work using DHCP with manual IP. It is the IP address that is important.
I have mostly used Apple Airport Base Stations as my routers.
I ONLY allow 1 (one, mono, single, solo) active router in my home. When I have more than one device capable of routing, I disable its routing features. For example, somewhere along way, I've used a D-Link router (since retired), and I've attached additional WiFi base stations to extend my WiFi range. In all cases only 1 router was acting as a router and DHCP server. All the other router capable devices have been put into Bridge mode either because they had a Bridge mode option, or they had options to disable their DHCP and NAT services. Allowing multiple active routers means multiple subnets which would cause problems if the ethernet transfer was started in 1 subnet, and then when switching to WiFi, it was on a different subnet. In this case, the router would not be able to transparently switch the traffic to a different path as it wouldn't even know that you on the new subnet was the same you from the old subnet.
My fixed IP addresses have been of the form 10.0.1.50 (since my router IP address is 10.0.1.1). For a non-Apple router the Fixed IP address would most likely be of the form 192.168.1.* or maybe 192.168.2.*. As long as you are in the routers subnet. You would know this as anything not in your router's subnet would cause the router to ignore you.
MacBook 2GHz, PowerMac Dual G5/2.5GHz, Mac mini intel Dual Core 2/1.83Ghz
Mac OS X (10.5.3)
I also manage: 12" iBook G4/1GHz, iMac G4/1.25GHz
|
|
|
