Subject: Re: Single link multi homing
From: Brian Bennett (bahamat@home.com)
Date: Sun Feb 20 2000 - 23:32:07 EST
Thanks Ron, those will make due as a workaround. But still, does anyone
know a way to tell netatalk which IP address to use? If not, maybe this
needs to be added in future versions.
B
> From: Ron Chmara <ron@Opus1.COM>
> Reply-To: ron@Opus1.COM
> Date: Sun, 20 Feb 2000 21:01:04 -0700
> To: Brian Bennett <bahamat@home.com>
> Cc: netatalk-admins@umich.edu
> Subject: Re: Single link multi homing
>
> Brian Bennett wrote:
>> ...I've
>> added additional IP addresses to each of my computers in the 192.168.1.x
>> range.
>> To simplify: each computer has 1 ethernet card, and 2 IP Addresses.
>> When I connect to netatlk through the chooser it connects to the external IP
>> (ie, the one assigned by my ISP) which makes things really slow (10-20
>> seconds to transfer 3k).
>> My question:
>> How do I make netatalk use my private IP as it's primary IP address in the
>> chooser rather than the one assigned by my ISP?
>
> What's happening (to summarize): Your machines are connecting over an
> IP you don't want to use.
>
> Solution? Try this: See if you can connect over the IP you do want to use.
> Chooser-> Appleshare->Server IP address.
> Make aliases to that IP.
>
> Possible complications:
> 1. If your routing isn't set up right, you may have to go to the public IP,
> or change your routing.
> 2. If Netatalk tries to bind afp over tcp the first address assigned, change
> the order you assign them.
> 3. If you try to connect via DNS name, or some other method that uses the
> public IP, you have to use that IP.
>
> HTH,
> -Bop
>
> --
> Brought to you from iBop the iMac, a MacOS, Win95, LinuxPPC machine,
> which is currently in MacOS land. Your bopping may vary.
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:07 EST