Date: Tue, 10 Oct 1995 14:19:34 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: dennis@etinc.com (dennis) Cc: terry@lambert.org, hackers@FreeBSD.ORG Subject: Re: IPX Message-ID: <199510102119.OAA11133@phaeton.artisoft.com> In-Reply-To: <199510102107.RAA01799@etinc.com> from "dennis" at Oct 10, 95 05:07:01 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> SPX runs over IPX, so why would an IPX router care about or be incompatible > with either implementation? Because SAP implies temporary bindery objects in previous implementations for routing to operate. If you are talking about serving NetWare clients, then you are talking about responding to GetNearestServer() calls from the clients, at the very least to proxy them, since only a server on the same segment can respond directly. That's why Novell coined the term "brouter" implying a combination bridge/router being necessary -- no flat bridging allowed, unless you don't expect the hop count to be maintained correctly. This whole thing started on someone offering to port the recently released IPX (presumably 3.x or before, without RSA and packet signatures) server code for Linux. I don't expect the code to fully support most clients, in fact, because the number of NCP's you have to support to be a real server is in fact astronomical. It might be enough to allow some clients using restricted NCP sets to operate, in the same way that the MS NT NCP server allows NT and WFWG and Win95 MS supplie Novell clients to operate (though they offer logins at the 4.0 level, having hired mathematicians to reverse engineer the login valid RSA-derived token generation sequence). If someone is willing to do the port, don't look a gift horse in the mouth. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510102119.OAA11133>