home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!wupost!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!slc6!trier
- From: trier@slc6.INS.CWRU.Edu (Stephen C. Trier)
- Subject: Re: DV/X and NCSA Telnet WORKS!
- Message-ID: <1992Jul23.204306.27235@usenet.ins.cwru.edu>
- Sender: news@usenet.ins.cwru.edu
- Nntp-Posting-Host: slc6.ins.cwru.edu
- Organization: Case Western Reserve University, Cleveland, OH (USA)
- References: <1992Jul23.175757.1607@blaze.cs.jhu.edu>
- Date: Thu, 23 Jul 92 20:43:06 GMT
- Lines: 27
-
- In article <1992Jul23.175757.1607@blaze.cs.jhu.edu> silano@newton.cs.jhu.edu (Mike Silano) writes:
- >The reasons for this are clear - when the task is swapped out,
- >the ISR(Interrupt Service Routine) is swapped as well. ...
-
- >The solution to this is pktmux - the packet driver multiplexor.
-
- What?? No, pktmux is a solution to a different problem. The -w option
- to the Crynwr packet drivers is a solution to the problem you describe.
-
- Pktmux is designed to solve the problem of running more than one TCP/IP
- protocol implementation simultaneously. It gets it *almost* right, too.
- There are many potential problems with using it, enough that most (all?)
- TCP/IP vendors won't provide tech support for a problem that occurs
- while pktmux is loaded.
-
- It's possible that pktmux also solves the first problem you describe,
- even though that is definitely not its raison d'etre. If you are running
- only one TCP/IP stack at a time, try using the -w flag on your packet
- driver instead of running pktmux.
-
- If you are trying to run two TCP/IP stacks, you will have to use pktmux.
-
- --
- Stephen Trier "Think of an [IBM] RT as a large coupon..."
- CWRU IRIS/INS -- Irene Fung, describing a Sun trade-in deal
- trier@ins.cwru.edu
-