home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.appletalk
- Path: sparky!uunet!darwin.sura.net!jvnc.net!nuscc!ccewch
- From: ccewch@nuscc.nus.sg (Wong Chee Heng)
- Subject: Re: Proteon AppleTalk Router problem
- Message-ID: <1992Jul30.075746.13409@nuscc.nus.sg>
- Organization: National University of Singapore
- References: <1482@shaman.wv.tek.com>
- Date: Thu, 30 Jul 1992 07:57:46 GMT
- Lines: 36
-
- andrew@frip.WV.TEK.COM (Andrew Klossner) writes:
- : []
- :
- : "IF the router generates an NBP LkUp packet with a DDP source
- : address set to the address of the originating node (A), and a
- : hop count of zero, the receiving nodes (B) can (incorrectly)
- : GLEEN an AARP entry mapping the node A DDP address to the
- : Router Ethernet address."
- :
- : -=- Andrew Klossner (andrew@frip.wv.tek.com) write:
- :
- : Huh? The incorrect behavior in this case is the router putting
- : something other than its own address in the DDP source address field.
- : The originating node's address goes in the NBP tuple.
- :
-
- The router is behaving correctly in this case. Because, router are not suppose
- to change DDP source address, it only pass packets to different network
- interfaces and thus change only the Ethernet address in this case.
-
- The problem is, if (using the same example mentioned) node A and node B are
- truely in the same network, shouldn't NBP lookup be a link layer broadcast
- to the local network rather than querying it from the router? My guess is
- that there may be some configuration fault that cause this to happen,
- probably the router believe there are multiple subnets/zone in the same
- ethernet cable, or node A and node B somehow believe that they are on two
- different network.
-
- This is just my $.02.
-
-
-
- --
- Wong Chee Heng
- Systems Programmer
-
-