home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.appletalk
- Path: sparky!uunet!mcsun!inesc.inesc.pt!animal.inescn.pt!lquinta@animal.inescn.pt
- From: lquinta@animal.inescn.pt (Luis Quinta)
- Subject: Re: Static IP clients (Summary&Thanks)
- Message-ID: <1992Aug29.183620.4326@animal.inescn.pt>
- Sender: news@animal.inescn.pt (USENET News System)
- Nntp-Posting-Host: mac3.inescn.pt
- Organization: INESC Porto
- References: <1992Aug27.174742.29500@animal.inescn.pt>
- Date: Sat, 29 Aug 92 18:36:20 GMT
- Lines: 58
-
- There is a very conclusive and final reply by a very well know mac net
- man:
-
- >Naturally. If you knew how MacIP (the protocol used between the Macs
- >and the gateway) worked, you'd be very surprised that the DYNAMIC
- >sessions worked out-of-zone.
- >
- >The original (i.e. Stanford KIP code) MacIP (from which all others
- >derive) is specified, and the ONLY "documented" one (meaning the only
- >one for which the source code is available - there are no other
- >"official" documents) does not allow Macs to be in a different ZONE to
- >the MacIP gateway.
- >
- >This is because the concept of IP-ARP as used on Ethernet to resolve
- >IP addresses to Ethernet addresses has been "mapped" to NBP in
- >AppleTalk. NBP is used by both gateways amd Macs to perform a
- >zone-wide "NBP LkUp" for the entity "1.2.3.4:IPADDRESS" (if looking
- >for IP address "1.2.3.4"). This resolves an IP address to a HARDWARE
- >APPLETALK ADDRESS.
- >
- >Now LkUps in AppleTalk are confined to the one ZONE.
- >
- >Why does it work for the "dynamic" addresses? Most gateway code has a
- >"sneak path" between the Dynamic Address Assignment table and the NBP
- >ARP table. Before trying to resolve and IP address to an AppleTalk
- >address, the code "sneaks a look" in the Dynamic Address Assignment
- >table, and if the mapping is found there, the gateway delivers the
- >packet.
- >
- >Static Hosts don't ask for a dynamic address, therefore the address
- >doesn't make it into the table, therefore the gateway can't find the
- >Macintosh.
- >
- >Solutions:
- >
- > 1. Wait for another few years until the IETF group finally
- > produces a MacIP "standard" that has an agreed mechanism to
- > "fix" this non-problem (I'm one of the tardy authors :-),
- > and then wait more years for it to be implemented in
- > products,
- >
- > 2. Change to using all Dynamic addresses,
- >
- > 3. Change the zone names of the networks requiring Static
- > addresses to be the same as the one FP's LocalTalk is in.
- >
- >There's a "good" document (actually a "shock" document - it shows how
- >terribly complex it gets if you try to "solve" everyone's problems)
- >available at:
- >
- >> New MacIP document at ftp.is.sandy.novell.com
- >>
- >> in "ietf":
- >> - [R----F--] cranch 105113 Apr 30 17:51 macip.hqx
- >> - [R----F--] cranch 148806 Apr 30 17:51 macip.txt
-
- Thank you very much Tom
- Luis Quinta
-