BROWN@ucf1vm.cc.ucf.edu (04/22/91)
... The question to ask is how does one implement all those PD (Public Domain or Packet Drivers, it doesn't matter) TCP/IP implementations? Now that file servers can be used as IP routers (albeit static IP routers, from what little info I have on the things), one can easily put IP traffic on any network that's connected with file servers on an IP network. Now, there are those who aren't willing to spend the $5K for a site license for LAN WorkPlace for DOS (We might be, but it might be a couple of months) or even the other discounted rates for x-user licenses. So this brings up some interesting questions: 1) Will there be Packet Driver support for ODI? 2) If not, Will such things like the BYU shell still be able to pick up IP and IPX traffic on the wire, if a Netware IP router is at the other end? 3) At our site, we use a KA9Q NOS router w/ an IPXPKT PD to shove IP through our NetWare Networks. This new stuff should outmode such a kludge. But does it? I can't see a way, short of a PD over ODI solution, to multiplex IP and IPX between the NetWare shell and say, CUTCP or NCSA Telnet. 4) Would having the IP software talk directly to the board work? What does LSL do when a packet arrives that doesn't go to IPX? I have a feeling that the TCP/IP routing support inherent to NetWare 3.11 isn't going to do our campus any good unless we obtain LWPfD. I know that the shareware version of the BYU driver (2.0, I believe) has some major connection dropping bug that makes it impractical to use in our situation, so that idea is out. I'm anxiously awaiting any solutions, consolation, etc. Regards, Bill Laughner-Brown Instruction and Research Support University of Central Florida Computer Services Internet: brown@chinchilla.cc.ucf.edu BITNET: BROWN@UCF1VM.BITNET (aka brown@ucf1vm.cc.ucf.edu)