Date: Mon, 19 Feb 1996 11:26:47 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: phil@zipmail.co.uk, hackers@FreeBSD.org Subject: Re: BSDi : Internet Gateway for Novell Networks Message-ID: <199602191826.LAA13105@phaeton.artisoft.com> In-Reply-To: <18792.824712223@time.cdrom.com> from "Jordan K. Hubbard" at Feb 18, 96 10:43:43 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > One of these was a system called the BSDi Internet gateway for novell > > networks. it sells for $1595 for 5 users and comes with www/ftp etc, > > but the bit that caught my attention was the fact that it can be used > > for leased-line/dialup routing and (if the article is correct) no > > tcp/ip support is needed on the local n/w at all !! > > Yep! A few people tell me that Novell admins love this since it lets > them keep their networks "pure" - no icky TCP/IP frames on their > lovely little IPX networks (and, of course, the clients don't need to > run TCP/IP stacks). > > I think it would definitely be a well-regarded feature for FreeBSD if > we supported TCP/IP encapsulation like this. I don't know how much > work is involved, but.. I do. I did a product proposal for this type of thing at Novell. Even did some preliminary code. 8-). The biggest pain is setting up the server engine to advertise itself and respond to "GetNearestServer()" requests of the apropriate type. You will need a NetWare developer kit for the client API on the Windows box. The largest amount of grunt-work is in writing the Winsock-over-IPX tunnel. This is not quite traditional tunneling. Anyone have a full set of client developer red-boxes? 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?199602191826.LAA13105>