Xref: utzoo comp.dcom.lans:3629 comp.protocols.nfs:477
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!apple!sun-barr!newstop!east!hinode!geoff
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.dcom.lans,comp.protocols.nfs
Subject: Re: PC/IP and the Packet Driver.
Keywords: TCP/IP, packet driver
Message-ID: <923@east.East.Sun.COM>
Date: 13 Oct 89 16:59:42 GMT
References: <489@excelan.COM> <6635@pdn.paradyne.com> <736@ftp.COM> <6646@pdn.paradyne.com>
Sender: news@east.East.Sun.COM
Reply-To: geoff@East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Followup-To: comp.dcom.lans
Organization: Sun Microsystems, Billerica MA
Lines: 20

In article <6646@pdn.paradyne.com> dixon@gumby.paradyne.com (0000-Tom Dixon) writes:
>A couple of questions:  
>We have never tried this but have always wondered it. Can you use
>the packet driver with multiple TCP/IP applications?  Say for example
>NCSA Telnet and PC-NFS.  Or would the packet driver get really confused?

The packet driver interface that I shipped off to Clarkson was very basic:
it grabs all incoming packets rather than filtering on packet
types. Modifying it to do static filtering (i.e. all ARP, RARP, IP)
is pretty trivial.  (This is what's needed for coexistence with
NetWare or other non-IP stacks.) Modifying it for dynamic filtering based
on individual UDP or TCP ports, etc. is _much_ harder, and in
general not particularly useful: how, for example, do you persuade
NCSA Telnet to use a TCP port which doesn't clash with one
used by a PC-NFS Toolkit app?

Geoff Arnold,                              Internet: geoff@East.Sun.COM
PCDS Group, Sun Microsystems Inc.
---------------------------------------------------------------------------
"Who's next?" "Me, doctor?" "No, ME doctor, YOU patient." (Graham Chapman, RIP)