From owner-freebsd-hackers Sat Jan 27 09:35:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA18384 for hackers-outgoing; Sat, 27 Jan 1996 09:35:20 -0800 (PST) Received: from etinc.com (et-gw.etinc.com [165.254.13.209]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA18379 for ; Sat, 27 Jan 1996 09:35:18 -0800 (PST) Received: from ppp-082.etinc.com (ppp-082.etinc.com [204.141.95.142]) by etinc.com (8.6.12/8.6.9) with SMTP id MAA07882; Sat, 27 Jan 1996 12:32:49 -0500 Date: Sat, 27 Jan 1996 12:32:49 -0500 Message-Id: <199601271732.MAA07882@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: dennis@etinc.com (dennis) Subject: Re: NetBUI and/or IPX routing? Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org Precedence: bulk >> IPXrouted will answer SAP and RIP requests, so you won't have problems if >> you have a server on one net and hosts (IPX) on the other. The handling of >> SAP and RIP requests is described in the "IPX Router Specification" that is >> available from Novell. > >One SAP broadcast is made every 55 seconds for each service a server >has available. > >It is possible to rebroadcast SAP packets without problems, up to a >hop count of 16. > >The problem in the case of a proxy response is that your "router" must >rebroadcast the "GetNearestServer" NCP, *or* it must be capable of making >a proxy response the the NCP broadcast in such a way as the AttachServer >used by the client will attach to the server being proxied rather than >the machine doing the proxy response. > > >This is complicated by the fact that I can request service ID's (for >instance, I could request "Novell Virtual Terminal" or NVT servers >respond, rather than file servers). > >The GetNearestServer request is a broadcast NCP. It is used by client >machines starting up to locate a server on the local wire. For a proxy >response, this would be the machine in the local bindery (SAP broadcast >information is stored as tempory bindery objects in the local server's >bindery -- under 4.x, this is done with bindery emulation as a local >to each server NDS object). This is not generally true. A true IPX router maintains a server table and a routing table and responds to requests directly. All such requests are handled locally, and traffic is only routed once a destination network number has been determined. I wouldn't call them "proxies" per se....they are simply maintaining a map no unlike some high level routing protocols for the IP world. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX