| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
I don't do this but a customer has done the following and gotten the
described behavior.
The customer has a Mac OS X system with two network interfaces attached
to the same physical network, and associated two successive IP addresses
in the same IP network. One adapter is a slow speed built-in 10/100 and
the other a 1 Gigabit.
As I say, I would not do this. The behavior the custerm observes is
that when Mac OS 9 based machines use the 'chooser' and the under
lying Appletalk namebinding-to-ip association the ip address is resolved
to the 'slow' speed interface. When the Mac OS 9 user explicitly uses
the Gigabit address, packets sent, according to the customer, are
taken up by the 'highspeed' connection, but replies are sent via the
slow speed connection.
I have not duplicated the customer's set up because I no longer
have Mac OS 9 systems setup convienently in my usual networking
environment.
The question is, is it possible to have such a split on the transfers?
My immediate response to the customer was to place the two cards
on logically different networks, even though physically on the
same network 'cable'.
The thought as to why such a thing may occur is on the Mac 9 to
Mac OS X transmissions the Mac OS 9 system uses given IP
address. On replies from the Mac OS X system, in looking up the ethernet
MAC address, the network stack uses the 'first connection found', which
is the low speed built-in interface. Since the Mac OS 9 system has
'arp'ed both interfaces have received that arp and then associated
the MAC address given with an IP address.
| References: | |
| >Network routing methods (From: John Clark <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.