|
|
ARCHIVE: TCP-IP Distribution List - Archives (1993)
DOCUMENT: TCP-IP Distribution List for November 1993 (545 messages, 358594 bytes)
SOURCE: http://securitydigest.org/exec/display?f=tcp-ip/archive/1993/11.txt&t=text/plain
NOTICE: securitydigest.org recognises the rights of all third-party works.
START OF DOCUMENT
-----------[000000][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 03:29:06 GMT From: ctkosti@afterlife.ncsc.mil (Chris Kostick) To: comp.protocols.tcp-ip Subject: Re: ping's maximum packet size
In article <fred_sCFq1oM.E9H@netcom.com>, Frederick Scott <fred_s@netcom.com> wrote: >ctkosti@afterlife.ncsc.mil (Chris Kostick) writes: > >>I was hoping to experiment with the affects of various packet sizes >>on a network and was going to use ping. >> >>On a Sun (SUNOS 4.1.3) I tried >> >> $ ping -s afterlife 2048 >> PING afterlife.ncsc.mil: 2048 data bytes >> sendto: Message too long >> ping: wrote afterlife.ncsc.mil 2056 chars, ret=-1 >> sendto: Message too long >> ping: wrote afterlife.ncsc.mil 2056 chars, ret=-1 >> ^C >> ----afterlife.ncsc.mil PING Statistics---- >> 2 packets transmitted, 0 packets received, 100% packet loss >> >>The man page for sendto() says >> >> If the message is too long to pass atomically through the >> underlying protocol, then the error EMSGSIZE is returned, >> and the message is not transmitted. >> >>I'm assuming the problem is with sendto() and not ping itself. Is there >>anything I can do to make ping work with a packet size over 2000 bytes? >>Do I need to change the source? the OS? Is there another program out in >>net land that gives me the same functionality as ping? > >I don't think the problem is with sendto(). What kind of network are you >pinging on? An ethernet network has a maximum packet size of 1518 bytes, >And I believe the ethernet and ICMP/IP headers and the CRC checksum will >reduce the number of bytes you give ping as a parameter further. > >Anyway, the point is, I don't think there's any way you can convince SunOS >to fragment your ping packet on the local network. You're stuck with the >maximum packet size. I'm pinging on an ethernet network. From my understanding of the protocols, if I have 4K of data to send, then IP can handle that. It just fragments the data. Isn't that how NFS works? By default 8K UDP packets are sent. IP has no problem fragmenting that. You say I can't convince SunOS to fragment. Well, if send the 2000 bytes and then monitor the network, it's fragmentmented into two packets. So obviously I can, my question is why the 2000 byte limitation? > >As for another program giving you the "same functionality as ping does", >that depends on exactly what functionality you want. *No* program will >allow you to transmit more bytes in a single packet than a network's MTU on >that network, of course. If you just want to send an arbitrary "X number of >characters" to another host and have it reply with the same data coming back, >I suppose you could just write a simple TCP program to do that. TCP, of >course, will have additional implications to any study of network performance. >Alternatively, you could use UDP if you consented to use multiple sendto's. >But any program attempting to implement the use of the ICMP/echo message >in order to get a reply directly from the remote node's IP stack will run up >against the same limitation that ping has. > >Fred Sorry for the ambiguity. The functionality I was looking for was being able to generate arbitrary packet sizes and measure the round trip time for a series of packets sent. -- chris
-----------[000001][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 1993 03:47:27 GMT From: Martin Visser <Martin.mc.visser@bhpmelmsm.bhp.bhpmel04.telememo.au> To: comp.dcom.cell-relay,comp.protocols.tcp-ip Subject: Re: which type of fiber to use?
In article <CFHME8.21s@world.std.com> Craig Partridge,
craigp@world.std.com writes:
> Given the job of installing fiber into and between two buildings,
what
>type of fiber should you install? Let's assume both buildings are no
more
>than six stories high, and no office in each building is more than 100m
>from a central wiring closet that runs up the core of each building, and
>the two buildings are 500m apart. What type of fiber do you run:
We'll be undertaking a project of a similar nature ( but longer average
distances) in the next year
or so in out Steelworks. Currently we intend our backbone cable to be 18
core MM and 6 core SM.
Because of cost and the bandwidth requirements at the moment, we would
expect the SM to remain dark for the next 5 years at least. Single mode
interfaces are likely to very expensive until then , and probably will
not required to meet our needs.
One difficulty may be also choosing the specs of fibre. In another post,
ATM Forum have specified 500 MHz/km for MM fibre UNI. Garden-variety
62.5/125 seems to be only 400MHz/km, meaning older fibre may not be as
good, and you also may have order a special.
In article <1993Oct26.082922.6626@dxcern.cern.ch> Brian Carpenter
CERN-CN, brian@dxcern.cern.ch writes:
>Inside buildings: multi-mode up to the closet
> UTP 5 to the desk (plus empty tubes!!!)
Are these "empty tubes" for fiber and if so are they in the same cable as
UTP?
Also how far can you blow fibre through tubes, both in straight runs, and
around bends?
: Martin Visser
/\/\ : BHP Steel - Slab & Plate Products Division
/ / /\ : Engineering Technology - Computer Systems
/ / / \ : PO Box 1854 Wollongong NSW 2502, AUSTRALIA
/ / / /\ \ : A.C.N. 006 476 218
\ \/ / / / : Phone +61-42-753852
\ / / / : Fax +61-42-757897
\/\/\/ : Internet MARTIN.M.C.VISSER@
: BHPMELMSM.BHP.bhpmel04.telememo.au
: X.400 G=MARTIN I=MC S=VISSER OU=BHPMELMSM O=BHP
: P=BHPMEL04 A=TELEMEMO C=AU
-----------[000002][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 93 13:36:12 PST From: EricR@cup.portal.com (Eric - Rupert) To: comp.protocols.tcp-ip,comp.dcom.sys.cisco Subject: Re: multiple subnets behind a router
I posted a question last week about netmasking multiple subnets to look as one. I havent received any responses yet, but have a possible way to do this and am looking for comments on potential problems. Given: a cisco router and a cluster of class B subnets(ie. netmask 255.0) How do you get a couple of thousand addresses to look like a single net. Use 8 subnets beginning on say: x.x.8.yyy x.x.9.yyy x.x.10.yyy x.x.11.yyy x.x.12.yyy x.x.13.yyy x.x.14.yyy x.x.15.yyy With the following environ: A --- Cisco ---T/1 (internet) where A is a group of systems(actually a unix cluster). This is quite simple with the "secondary" ip address function of the router. Look on pg 14-53 , Vol II of the manual, no need to mess around with the mask. Eric Rupert - RPM Associates Ericr@rpm.com
-----------[000003][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 06:51:29 GMT From: fred_s@netcom.com (Frederick Scott) To: comp.protocols.tcp-ip Subject: Re: ping's maximum packet size
ctkosti@afterlife.ncsc.mil (Chris Kostick) writes: >In article <fred_sCFq1oM.E9H@netcom.com>, >Frederick Scott <fred_s@netcom.com> wrote: >>I don't think the problem is with sendto(). What kind of network are you >>pinging on? An ethernet network has a maximum packet size of 1518 bytes, >>And I believe the ethernet and ICMP/IP headers and the CRC checksum will >>reduce the number of bytes you give ping as a parameter further. >> >>Anyway, the point is, I don't think there's any way you can convince SunOS >>to fragment your ping packet on the local network. You're stuck with the >>maximum packet size. > >I'm pinging on an ethernet network. From my understanding of the >protocols, if I have 4K of data to send, then IP can handle that. That is correct. Any IP packet can be fragmented, it's just that if you know that the MTU of your local net is X bytes, there (theoretically) isn't any reason to attempt to send an IP packet of greater than X bytes. The BSD implementation of TCP, I believe, takes advantage of that by assuming a default maximum segment size of the local net's MTU, to be reduced if it is later found necessary or useful to for other reasons. >It just fragments the data. I'm somewhat surprised by this for the reasons I just stated. However, if the IP stack implementation is written to that with ICMP echos, then that's how it is. It's certainly "legal" to do. >Isn't that how NFS works? By default 8K UDP packets are sent. Yes, that would make sense. RPC probably needs of UDP's record boundary preservation feature in order to "atomize" an RPC operation, so that RPC doesn't have to worry about, say, partial receipt of an RPC request. That is, some UDP packets arriving and some not. By using a single, fragmented UDP packet, RPC in essense leaves this problem for the IP protocol to deal with. So I guess there IS a reason to purposely transmit a packet you know needs to be fragmented right from the start. >IP has no problem fragmenting that. You say I can't convince SunOS to >fragment. I was assuming so because I'd run into Berkeley distributions where you couldn't. (I knew it was legal to do - it's just that that the code wouldn't let you.) Of course, when you ASS-U-ME.... :-) >Well, if send the 2000 bytes and then monitor the network, it's fragmentmented >into two packets. So obviously I can, my question is why the 2000 byte >limitation? Well, now you've got me. It may turn out to be arbritrary limit or it may not. So I'll leave the original question open to anyone who knows more about this IP implementation than I do. Sorry. Fred
-----------[000004][next][prev][last][first]---------------------------------------------------- Date: Mon, 01 Nov 1993 14:58:08 EST From: Robert_Meindl__ISSG@bbsnewsgate1.ads.com To: comp.protocols.tcp-ip Subject: Newbie OSPF Question
Greetings Could someone provide a clear explanation of how to determine the subnet mask when you are using the variable length subnet mask feature of OSPF for route summarization. Specifically, I understand the case when the internet consists of multiple Class B addresses, but don't quite get how to determine the mask for breaking up a Class B into several areas. Thanks in advance Bob Meindl meindlr@v3.hanscom.af.mil *************************************************************************** This message was sent from FirstClass(tm) by PostalUnion(tm) originating at BOOZ-ALLEN & HAMILTON INC. The views expressed in this posting are those of the individual author and do not necessarily reflect the views of BOOZ-ALLEN & HAMILTON INC. ***************************************************************************
-----------[000005][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 13:10:35 GMT From: bagpuss@spuddy.uucp (Mark Liversedge) To: comp.protocols.tcp-ip Subject: Re: How to read any packet in the ethernet
In article <1993Oct26.194928.10458@litwin.com> hoang1@litwin.com (Ted Hoang) writes: >Hi, >Could someone explain how to read any packet (TCP, UDP, IP, IPX ...) directly >from the ethernet. Should I use open(), socket(), or none_of_the_above()...? >How could I read this packet from beginning (byte 0)? Ultrix "man packetfilter" SunOS "man nit" (and etherfind) BSDi "man bpf" (and tcpdump) Anything else and I haven't a clue. If you want some sample code I can mail it to you, these devices read from the wire It's down to the user to decode protocols. Good luck! -- * Meeeow ! Call Spuddy on (0203) 364436/362560 for FREE mail & Usenet access *
-----------[000006][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 13:31:58 GMT From: leighd@syma.sussex.ac.uk (Leigh Dodd) To: comp.protocols.tcp-ip Subject: Ethernet MAC address programme required
Hi All Can anyone give me a glue as to where I can find a P.D. (Free) programme that will give me the MAC address on a selected computer ?. I can ping and the arp a few computers and I get the address, but a number don't update the arp tables (Sun OS 4.1.3). I can also run snoop but it's a bit messy considering I need to get the addresses of about 100 machines. A simple ping type thing would be nice. Can be Unix or DOS. Thanks in advance Leigh -- ******************************************************************************* * Leigh Dodd (Sun System Administrator) | Three Steps to Heaven * * University of Sussex | 1). C.B.T. ----- Passed * * Brighton, England. | 2). Part 2 ----- Passed * * INTERNET: leighd@eaps.susx.ac.uk | 3). Gota GPz550 and Riding To HELL * *******************************************************************************
-----------[000007][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 1993 15:50:51 GMT From: hunenr@cis.corp.medtronic.com (Roger Hunen) To: comp.protocols.tcp-ip Subject: Re: ping's maximum packet size
In article <1993Nov1.032906.8590@afterlife.ncsc.mil> ctkosti@afterlife.ncsc.mil (Chris Kostick) writes: #I'm pinging on an ethernet network. From my understanding of the #protocols, if I have 4K of data to send, then IP can handle that. It just #fragments the data. Isn't that how NFS works? By default 8K UDP packets #are sent. IP has no problem fragmenting that. You say I can't convince #SunOS to fragment. Well, if send the 2000 bytes and then monitor the network, #it's fragmentmented into two packets. So obviously I can, my question #is why the 2000 byte limitation? It may be that DON'T-FRAGMENT is set on ping packets (which makes sense to me). In that case the maximum ping size equals the minimum MTU on any part of the path. Regards, -Roger
-----------[000008][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 16:27:32 GMT From: cawilco@afterlife.ncsc.mil (Chris A. Wilcox) To: comp.dcom.cell-relay,comp.protocols.tcp-ip Subject: Re: which type of fiber to use?
In article <1993Oct26.082922.6626@dxcern.cern.ch>, Brian Carpenter CERN-CN <brian@dxcern.cern.ch> wrote: > >Craig, > >What's hypothetical? These are exactly the questions we've been >asking for two years. Our current answers are: > >Between buildings: multi-mode up to 1 km; single mode for longer >distances. > >Inside buildings: multi-mode up to the closet > UTP 5 to the desk (plus empty tubes!!!) > >We are betting on FDDI over UTP5 and ATM over UTP5. The empty tubes >are vital, in case we are wrong. > >Regards, > Brian Carpenter CERN, brian@dxcern.cern.ch > voice +41 22 767 4967, fax +41 22 767 7155 I would think that the expected rates you want to run between buildings would also make a difference as to whether you use multimode or single mode fiber. As an example, I don't think you could run an OC-48 SONET trunk between buildings using multimode fiber. As a matter of fact, if you are planning on using SONET, you must use single mode fiber (I have heard that the ATM forum has defined a SONET interface using multimode fiber, but as far as I know that has not been coordinated with any of the "official" standards bodies such as ANSI or ITU (formerly CCITT)). Sorry for the late response; I just got back from an ANSI meeting... :-) -- Chris Wilcox |"The guy sure looks like plant food to me" Dept. of Defense | Seymour and Audrey II cawilco@afterlife.ncsc.mil | 'Little Shop of Horrors' The views represented here probably aren't held by the DoD. Get over it.
-----------[000009][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 93 16:36:45 GMT From: anils@ada.CS.ORST.EDU (Anil Srivastava) To: comp.protocols.tcp-ip Subject: UNIX based time servers...
I am looking for the ip address of a really accurate time server which allows me to poll it for time and synch our Novell server's with it using RDATE.NLM. Any help would be greatly appreciated. I have a copy of Murkworks RDATE and all I need is the ip address of a machine that allows me poll it for time. Thanks.... PS: SInce I don't follow this news group regularly, responses via e-mail would be REALLY appreciated :-) -- Anil Srivastava anils@research.cs.orst.edu
-----------[000010][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 17:50:56 GMT From: sharmila@forge.Tandem.COM (Sharmila Podury) To: comp.protocols.tcp-ip Subject: Service port #s in inetd.conf???...
Does anyone know why the entries for each service in the inetd.conf file do not contain the port numbers? Is there a reason why one would not want to put the port numbers in inetd.conf? Answers would be greatly appreciated. Thanks. -- PODURY_SHARMILA@Tandem.com
-----------[000011][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 1993 17:56:44 GMT From: nessett@framsparc.ocf.llnl.gov (Dan Nessett) To: sci.crypt,mitre.crypt,alt.security,comp.protocols.tcp-ip Subject: ISOC Symposium on Network and Distributed System Security
ISOC Symposium on Network and Distributed System Security
---------------------------------------------------------
Program
-------
Wednesday, February 2
6:00 P.M. Ð 8:00 P.M.
Registration and Reception
Thursday, February 3
7:30 A.M.
Continental Breakfast
8:30 A.M.
Opening Remarks
9:00 A.M.
Session 1: Electronic Mail Security
Chair: Steve Kent (BBN)
Certified Electronic Mail, Alireza Bahreman (Bellcore) and Doug Tygar
(Carnegie Mellon University), USA
Privacy Enhanced Mail Modules for ELM, Selwyn Russell and Peter
Craig, Queensland University of Technology, Australia
Management of PEM Public Key Certificates Using X.500 Directory
Service: Some Problems and Solutions, Terry Cheung, Lawrence
Livermore National Laboratory, USA
10:30 A.M.
Break
11:00 A.M.
Session 2: Panel: Public Key Infrastructure, Santosh Chokhani (MITRE),
Michael Roe (Cambridge University), Richard Ankney (Fischer, Intl.)
Chair: Miles Smid (NIST)
12:30 P.M.
Lunch
2:00 P.M.
Session 3: Protocols
Chair: Tom Berson (Anagram Labs)
Paving the Road to Network Security, or The Value of Small Cobblestones,
H. Orman, S. O'Malley, R. Schroeppel, and D. Schwartz, University of
Arizona, USA
A Complete Secure Transport Service in the Internet, Francisco Jordan
and Manuel Medina, Polytechnical University of Catalunya, Spain
3:00 P.M.
Break
3:30 P.M.
Session 4: Internet Firewall Design and Implementation
Chair: Jim Ellis (CERT)
Inter-LAN Security and Trusted Routers, Pal Hoff, Norwegian Telecom
Research, Norway
Trusted to Untrusted Network Connectivity: Motorola Authenticatd
Internet Access -- MANIAC(TM), Bill Wied, Motorola, USA
BAfirewall: A Modern Firewall Design, Ravi Ganesan, Bell Atlantic, USA
WhiteHouse.Gov: Secure External Access and Service for the Executive
Office of the President, Frederick Avolio and Marcus Ranum, Trusted
Information Systems, USA
7:00 P.M.
Banquet
Friday, February 4
7:30 A.M.
Continental Breakfast
8:30 A.M.
Session 5: Panel: All Along the Watchtower: Experiences and Firefights
Managing Internet Firewalls, Brian Boyle (Exxon Research), Brent
Chapman (Great Circle Consulting), Bill Cheswick (AT&T Bell Labs),
Allen Leibowitz (Warner-Lambert), Marcus Ranum (TIS)
Chair: Frederick Avolio (TIS)
10:00 A.M.
Break
10:30 A.M.
Session 6: Issues in Distributed System Security
Chair: Cliff Neuman (USC-ISI)
CA-Browsing System -- A Supporting Application for Global Security
Services, Denis Trcek, Tomas Klobucar, Borka Jerman-Blazic, and Franc
Bracun, Jozef Stefan Institute, Slovenia
The X.509 Extended File System, Robert Smart, CSIRO Division of
Information Technology, Australia
Auditing in Distributed Systems, Shyh-Wei Luan (VDG, Inc.) and Robert
Weisz (IBM Canada Laboratory), USA/Canada
12:00 Noon
Lunch
1:30 P.M.
Session 7: Authentication
Chair: Dave Balenson (TIS)
The S/KEY(tm) One-Time Password System, Neil Haller, Bellcore, USA
A Technique for Remote Authentication, William Wulf, Alec Yasinsac,
Katie Oliver, and Ramesh Peri, University of Virginia, USA
Remote Kerberos Authentication for Distributed File Systems: As
Applied to a DCE DFS-to-NFS File System Translator, Thomas Mistretta
and William Sommerfeld, Hewlett-Packard, USA
3:00 P.M.
Break
3:30 P.M.
Session 8: Panel: IP Security Alternatives, K. Robert Glenn (NIST), Paul
Lambert (Motorola), David Solo (BBN), James Zmuda (Hughes)
Chair: Russell Housley (Xerox)
PROGRAM CO-CHAIRS
Russell Housley, Xerox Special Information Systems
Robert Shirey, The MITRE Corporation
GENERAL CHAIR
Dan Nessett, Lawrence Livermore National Laboratory
PROGRAM COMMITTEE
Dave Balenson, Trusted Information Systems
Tom Berson, Anagram Laboratories
Matt Bishop, University of California, Davis
Ed Cain, U.S. Defense Information Systems Agency
Jim Ellis, CERT Coordination Center
Steve Kent, Bolt, Beranek and Newman
John Linn, Geer Zolot Associates
Clifford Neuman, Information Sciences Institute
Michael Roe, Cambridge University
Robert Rosenthal, U.S. National Institute of Standards and
Technology
Ravi Sandhu, George Mason University
Jeff Schiller, Massachusetts Institute of Technology
Peter Yee, U.S. National Aeronautics and Space
Administration
BEAUTIFUL SAN DIEGO
The Symposium venue is the Catamaran Resort Hotel, providing 7 acres of
gorgeous surroundings, facing Mission Bay and only 100 yards from
beautiful Pacific Ocean beaches. Spouses and family members can catch a
convenient Harbor Hopper for a quick trip to Sea World. After the
Symposium, plan to spend the weekend visiting La Jolla, the world
famous San Diego Zoo or Mexico, only 30 minutes by car or Trolley.
A limited number of rooms have been reserved at the Catamaran for the
very special rate of $77 single, $87 double. Reservations, on a space
available basis, can be made by calling (800) 288-0770 and indicating you are
attending the ISOC Symposium. Reservations must be made before Jan. 1,
1994 to ensure this rate.
CLIMATE
February weather in San Diego is normally very pleasant. Early morning
temperatures average 51 degrees while afternoon temperatures average 67
degrees. Generally, a light jacket or sweater is adequate during February;
although, occasionally it rains.
TRANSPORTATION
San Diego International Airport is 10 miles (15 minutes) from the
Catamaran Hotel. Supershuttle operates a continuous service between the
airport and the hotel: fare is $6.00. When you arrive at the airport, use the
free Supershuttle phone. Taxi fare between the airport and the hotel is $20.
The Catamaran charges $6 per day for parking.
REGISTRATION FEES
Postmarked Subsequent
by Jan. 1 registration
$305 $350
REGISTRATION INCLUDES
- Attendance - Symposium Proceedings
- Reception - Banquet
- Luncheons - Coffee Breaks
On-site registration is available Wednesday evening at the reception, and
Thursday morning at the Symposium. For more information on
registration and local arrangements contact Dan Nessett at (510) 422-4033
or nessett@llnl.gov.
SYMPOSIUM REGISTRATION FORM
Name ________________________________________________
Affiliation__________________________________________
Name on Badge _______________________________________
Vegetarian Meals?____________________________________
Mailing Address _____________________________________
_____________________________________________________
_____________________________________________________
Area Code/Phone # ___________________________________
Email Address _______________________________________
Make check (credit cards not accepted) payable to SNDSS94. (Registration is
not effective until payment is received). Mail to: ISOC Symposium, C/O
Belinda Gish, L-68, Lawrence Livermore National Laboratory, Livermore,
CA. 94550.
-----------[000012][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 18:08:05 GMT From: davidb@ndl.co.uk To: comp.protocols.tcp-ip Subject: Deployment of RFC1058 X25 RR's
I'm interested in finding out out whether anyone has deployed the DNS resource record scheme for X.25 given in RFC1058. Any experiences, examples or other tales of interest should be mailed to me please.
-----------[000013][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 1993 18:13:31 GMT From: datkins@polaris.unm.edu (Drexel Atkinson CIRT) To: comp.protocols.tcp-ip,comp.dcom.sys.cisco Subject: multiple subnets behind a router
I posted a question last week about netmasking multiple subnets to look
as one. I havent received any responses yet, but have a possible way to
do this and am looking for comments on potential problems.
Given: a cisco router and a cluster of class B subnets(ie. netmask 255.0)
How do you get a couple of thousand addresses to look like a single net.
Use 8 subnets beginning on say:
x.x.8.yyy
x.x.9.yyy
x.x.10.yyy
x.x.11.yyy
x.x.12.yyy
x.x.13.yyy
x.x.14.yyy
x.x.15.yyy
With the following environ:
A --- Cisco ---T/1 (internet)
where A is a group of systems(actually a unix cluster).
Set broadcast to be: 255.255.15.255
Set netmask on router to be: 255.255.255.0 (ie. same as on the remainder of
the class B)
Set netmask on systems in area A to be: 255.255.248.0
Does anyone see any problems with doing this. It seems there may be a problem
with route updates since there would be multiple network interfaces behind the
router. There would be a couple of different ethernet cards and an fddi ring.
Comments.
-------------------------------------------------------------------------
Drexel Atkinson datkins@unm.edu
Systems Programmer CIRT-ACS University of New Mexico
---------------------------------------------------------------------------
-----------[000014][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 18:14:15 GMT From: donp@novell.com (don provan) To: comp.protocols.tcp-ip Subject: Re: NetBIOS over TCP/UDP and IP over NetBIOS ???
In article <1993Oct27.131624.16356@newstand.syr.edu> fkyu@top.cis.syr.edu (Fang-Kuo Yu) writes: > >RFC1001 and RFC1002 define 'Protocol standard for a NetBIOS >service on a TCP/UDP transport'. > >RFC1088 defines 'Standard for the transmission of IP datagrams >over NetBIOS networks'. > >As a result, we can get a configuration, such as, > > 'Application -> NetBIOS -> TCP/UDP -> IP -> NetBIOS -> ...' > >in a single host?! > >I feel comfortable about RFC1001 and RFC1002. But, why we need >RFC1088? If you have a TCP/IP network and you want to talk using the NetBios API between machines, you use RFC1001/2. If you have two machines already talking through the NetBios API and you want to connect them with TCP/IP, you can use RFC1088. The fact that you could run RFC1001/2 on top of RFC1088 (on top of RFC1001/2...) is just a curiousity of very little practical interest. If two machines are talking TCP/IP directly, there'd be no reason to connect them again with TCP/IP on top of NetBios. (You can construct legitmate configurations that include such recursion in parts of the path, but I doubt any would actually come up in real life.) I don't really knowing what's going on in the world of NetBios, buy I'd guess that RFC1088 is becoming less and less interesting as more and more machines talk TCP/IP directly on the physical network. don provan donp@novell.com
-----------[000015][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 18:26:35 GMT From: donp@novell.com (don provan) To: comp.protocols.tcp-ip Subject: Re: definition of 'internet'
In article <18822@auspex-gw.auspex.com> guy@Auspex.COM (Guy Harris) writes: >Umm, at least the way I've heard it used, *the* Internet refers only to >those machines connected via TCP/IP. > >I would be nice if somebody could come up with a name for the set of all >machines that can exchange email In The Internet, it's been traditional to refer to the entire email domain as the internet, with a lower case "i". Kind of fitting, I think: "the internet" is just a noun, like "the sky". don provan donp@novell.com
-----------[000016][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 18:36:18 GMT From: bruce@cortex.elekta.com (R. Bruce Rakes) To: comp.protocols.tcp-ip Subject: Re: definition of 'internet'
guy@Auspex.COM (Guy Harris) writes: >>>I have always called the Internet: "A network of interconnected networks >>>using TCP/IP" >>> >> Or uucp, or kermit, or...... >Umm, at least the way I've heard it used, *the* Internet refers only to >those machines connected via TCP/IP. >I would be nice if somebody could come up with a name for the set of all >machines that can exchange email, which is what I assume you are >referring to (there already *is* a name for the set of all machines that >can exchange netnews - "USENET"). I have heard the expression "Outernet" to include all other networks and/or protocols that can xchange email w/ the internet. -- R. Bruce Rakes, Software Systems Manager Elekta Instruments, Inc. 8 Executive Park W, Suite 809, Atlanta, GA 30329 Voice:(404)315-1225 FAX:(404)315-7850 email: bruce@elekta.com
-----------[000017][next][prev][last][first]---------------------------------------------------- Date: Mon, 1 Nov 1993 18:56:28 GMT From: visser@convex.com (Lance Visser) To: comp.protocols.tcp-ip Subject: Re: ping's maximum packet size
In <1993Nov1.032906.8590@afterlife.ncsc.mil> ctkosti@afterlife.ncsc.mil (Chris Kostick) writes: +>I'm pinging on an ethernet network. From my understanding of the +>protocols, if I have 4K of data to send, then IP can handle that. It just +>fragments the data. Isn't that how NFS works? By default 8K UDP packets +>are sent. IP has no problem fragmenting that. You say I can't convince +>SunOS to fragment. Well, if send the 2000 bytes and then monitor the network, +>it's fragmentmented into two packets. So obviously I can, my question +>is why the 2000 byte limitation? The ping source I have access to has a #define in it for the maximum packet size. There is no good reason. I have upped it to 60k occasionally for hippi testing. There is a bad reason for leaving it at 2k though. If you send enormous icmp packets (10k+) to certain systems over ethernet, you can crash them.
-----------[000018][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 1993 19:20:34 GMT From: rawn@lead.aichem.arizona.edu (Rawn Shah) To: comp.protocols.nfs,comp.protocols.tcp-ip,comp.answers,news.answers,comp.sys.mac.comm Subject: NFS & TCP/IP FAQ for PCs & Macs [part 01/06]
Archive-name: pcnfs-faq/part1
Last-modified: 1993/10/28
Version: 1.5
Back again from the blue. Here's version 1.5.
Disclaimer:
The material in this FAQ is not based on preferrence for any
one product. All questions have been drawn from the archives of
comp.protocols.nfs starting from the very beginning. To all distributers/
software houses: If you feel that there is unfair representation of your
product in this list please mail me at:
rawn@rtd.com or
rawn@xray1.chem.arizona.edu
or call:
(602) 318-0696 [US]
I have to admit that there is one bias. All addresses or phone numbers which
do not state which country they are in, are in the US. I've been pretty
oblivious about that.
NOTE: If you use this FAQ list and decide you like a product listed here
enough to purchase it, please mention where you got this information to the
product seller. Thank you.
Rawn Shah
RTD Systems & Networking, Inc.
Tucson, AZ
-------------------------------------------------------------------------------
*. This FAQ
*-1. What topics does this FAQ cover?
*-2. Where can I get this FAQ?
*-3. Who helped write this FAQ?
*-4. Who maintains this FAQ?
*-5. Who maintains comp.protocols.nfs?
*-6. Where are the archives for comp.protocols.nfs?
*-7. Trademarks and Registered names.
*-8. What do the -, + and * before the questions mean?
*-9. *Whats up and coming in the next issue of the FAQ list?
The real FAQ:
A. Basics
A-1. What is NFS?
A-2. What is (PC)NFS?
A-3. Where can I get (PC)NFS for my DOS system?
A-4. Where can I get (PC)NFS for my MS-Windows system?
A-5. +Where can I get (PC)NFS for my Macintosh system?
A-6. What is PC-NFS as opposed to (PC)NFS?
A-7. What is TCP/IP?
A-8. What is telnet? What is ftp?
A-9. What is a client? What is a server? Why do I need them?
A-10. Where can I get (PC)NFS cheap/free/PD?
A-11. What is SOS & SOSS? Where can I get it?
A-12. +Are there any free NFS clients available for DOS?
A-13. What is SLIP?
A-14. What is PPP?
B. Setup
B-1. *What are the different types of drivers available?
B-2. -What are "shim"s? What shims are available?
B-3. What are packet drivers? Where do I get them?
B-4. Can I use packet drivers with (PC)NFS?
B-5. +Can I run (PC)NFS over SLIP?
B-6. Can I run (PC)NFS at the same time as Netware?
B-7. Can I run (PC)NFS at the same time as CUTCP or NCSA Telnet?
B-8. Can (PC)NFS run with NDIS drivers?
B-9. +Can I use (PC)NFS to mount a diskless PC from a remote server?
B-10. Can (PC)NFS run over token ring?
B-11. Can I run PC-NFS with my 3C509 Etherlink III card?
B-12. Can I run PC-NFS slip at higher baud rates than 9600?
B-13. Can I access an MSCDEX CD-ROM with PC-NFS?
B-14. Can I run NDIS over Packet drivers?
B-15. *How does ODI compare to NDIS?
C. Server
C-1. What is pcnfsd? What is pcnfsdv2?
C-2. +Where can I get pcnfsd for my server system?
C-3. -What is lockd?
C-4. How can I test NFS performance?
C-5. What is NHFSSTONES? Where can I get it?
C-6. -What will help my server increase performance?
C-7. How many nfsd's & biod's should I run on my server?
C-8. What is asynchronous I/O? How can I modify my NFS server system to use
asynchronous I/O?
C-9. What is a good NFS server?
C-10. What is LADDIS?
C-11. -What is XRemote & LBX?
D. Applications
D-1. +Where can I get mail with (PC)NFS?
D-2. Where can I get news with (PC)NFS?
D-3. Where can I get an FTP server?
D-4. Where can I get rwalld for (PC)NFS? [May be removed, please read]
D-5. Where can I get a INT-14 redirector for (PC)NFS?
D-6. Where can I get YPPASSWD for PC-NFS?
D-7. Where can I get IBM 3270 terminal for (PC)NFS?
D-8. Where can I get an X-Windows server for (PC)NFS?
D-9. -Where can I get a calender/scheduling program for (PC)NFS?
D-10. +Where can I get a database that works with (PC)NFS?
D-11. Where can I get a WAIS client for (PC)NFS?
D-12. +Where can I get an archie for (PC)NFS?
D-13. +Where can I get a gopher client for (PC)NFS?
D-14. +Where can I get a WWW (World Wide Web) client for (PC)NFS?
D-15. Where can I get X25 for (PC)NFS?
D-16. Where can I get NEWGRP.EXE for PC-NFS?
D-17. Where can I get AUTOCONF for PC-NFS?
D-18. Where can I get a backup utiliy for (PC)NFS?
D-19. Which (PC)NFS packages support DNS [named]?
D-20. Where can I get a traceroute program?
D-21. +Where can I get an LPD program?
E. Problems & General Q&A
E-1. -How can I load (PC)NFS into DOS high memory?
E-2. Can I use DNS instead of NIS with PC-NFS?
E-3. Why do some versions of (PC)NFS not follow symbolic links?
E-4. PC-NFS v4.0 has trouble with Cntl-S, Cntl-Q.
E-5. PC-NFS v4.0 has trouble with redrawing the window while in MS-Windows.
E-6. +PC-NFS v4.0 doesn't allow me to access the local printer when I have
network printers.
E-7. I cannot delete any file that PC-NFS makes with a ~ (tilde) in it.
E-8. PC-NFS says that it cannot open any more files even when the limit in
autoexec.bat is set higher.
E-9. Can (PC)NFS mount file systems which are bigger than 2 GB?
E-10. What is NFS/TCP? Will it work with my NFS?
E-11. +What is PKTD.SYS? Where can I get it?
E-12. How can I run Novell Netware (tm) 3.xx at the same time as (PC)NFS
using NDIS?
E-13. -How many PC's can work with a single PC-NFS server?
E-14. Is it possible to modify the read & write buffer sizes in (PC)NFS?
E-15. How can I install Ethernet boards not supported by (PC)NFS?
E-16. *In postscript files I sometimes get a ^D before the header from my
programs. How do I get rid of it?
F. Programming
F-1. +Is there a toolkit for (PC)NFS programming? Whats the latest version
and where can I get it?
F-2. What is the Windows Sockets API (winsock)? Where can I get it?
F-3. What is the latest version of the NFS protocol?
F-4. What happened to version 3 of the NFS protocol?
F-5. What is the current RPC version? Where can I get it?
F-6. Where can I get the RPC definition for PCNFSD?
F-7. What are RFC's? What RFC's describe the NFS protocol? Where can I get
these RFC's?
F-8. How can I tell if a file is NFS mounted from a server?
G. Product Features Comparisons
G-1. +Driver support comparison chart of different products.
G-2. +Protocol support comparison chart of different products.
G-3. +MS-Windows applications and support chart of different products.
G-4. +Utilities available with different products.
G-5. +Telnet features of different products.
G-6. +TCP/IP package compability with other network protocols.
G-7. Features of different X-windows products.
H. Information Sources
H-1. Chest - Council for Higher Education Software Transfer [UK]
H-2. X/Open
H-3. +Books
H-4. Related Papers (published)
H-5. +Popular FTP sites
H-6. Related FAQ's, USENET lists, mail lists.
H-7. *Glossary.
W. Third-Party Email Software
W-1. CliqAccessories Quadratron Systems
W-2. Higgins Group Prod sw Enable Software
W-3. Linkage Concentric Technologies
W-4. OpenMail Hewlett-Packard
W-5. PathWay Messenger The Wollongong Group.
W-6. PC-Eudora Qualcomm Software.
W-7. SelectMail SunSelect
X. X-Windows Software
X-1. eXceed Hummingbird Software Ltd.
X-2. eXcursion DEC
X-3. eXodus White Pines Software.
X-4. Micro X-Lite StarNet Communications Corporation.
X-5. MultiView/X JSB Corporation
X-6. PC-Xware & PC-Xview NCD, Inc.
X-7. PC X-server & PC Link XLink
X-8. PC-Xsight Locus Computing Corp.
X-9. PC DECWindows Motif DEC
X-10. -Reflection X Walker, Richer & Quinn
X-11. X Appeal Xtreme s.a.s.
X-12. Xoftware AGE Logic, Inc.
X-13. Xvision VisionWare Soft, Inc
X-14. X-windows for OS/2 IBM
Y. Other Third Party & Related Software
Server Products:
Y-1. eNFS INTERSTREAM
Y-2. Multinet TGV, Inc.
Y-3. -DEC TCP/IP Digitial Equipment Corp.
Y-4. -NHFSSTONE Legato
Y-5. -PrestoServe Legato
Y-6. SOSS Rich Braun
Y-7. TCPWare for VMS Process Software Corp.
Other software:
Y-9. -WinTrumpet/Trumpet Peter Tatam.
Y-10. -WinVN
Y-11. -Cello
Y-12. MacPPP
Z. TCP/IP & NFS Products
Z-1. AIR for Windows SPRY, Inc.
Z-2. BW-NFS Beame & Whiteside, Inc.
Z-3. Chameleon NFS NetManage
Z-4. CU/TCP Clarkson University/Rutgers University
Z-5. Distinct TCP Distinct Corp.
Z-6. -LAN Manager TCP/IP Microsoft Corp.
Z-7. LAN Workplace NFS Novell, Inc.
Z-8. NCSA Telnet Nat'l Center for Supercomputing Applications.
Z-9. NFS/Share Intercon, Inc.
Z-10. NS & ARPA Services Hewlett-Packard, Inc.
Z-11. +Pathway Access DOS/Win The Wollongong Group.
Z-12. PathWay Access OS/2 The Wollongong Group.
Z-13. PC-NFS SunSelect Inc.
Z-14. PC/TCP FTP Inc.
Z-15. Reflection Walker Richer & Quinn, Inc.
Z-16. SuperTCP Frontier Technology, Corp.
Z-17. TCP/IP for DOS IBM
Z-18. -TCP/IP for OS/2 IBM
Z-19. TCP/Open Lanera Corp.
Z-20. TTCP Turbosoft Pte. Ltd.
Z-21. WATTCP Erick Engelke
Z-22. WinQVT QPC Software, Inc.
Z-23. *Fusion Pacific Softworks, Inc.
Z-24. *PathWay Access for Mac The Wollongong Group.
Z-25. *ICE/TCP James River Group
Z-26. *Piper/IP IPswitch, Inc.
-------------------------------------------------------------------------------
*-1. What topics does this FAQ cover?
This Frequently Asked Questions list covers questions on commonly available
NFS products and related products and topics running on PC systems and
Macintosh systems. The original section of topics has increased so much that
I've expanded them into separate sections as well. The topics now covered
are:
A. Basics - general questions on what NFS, (PC)NFS, & TCP/IP are.
B. Setup - questions on setting up these products
C. Server - questions on the PCNFSD server & server system
administration
D. Applications - commercial and public-domain applications which
will work with these systems.
E. Problems & General Q&A - questions, problems and general info on
(PC)NFS maintainence.
F. Programming - Programming toolkit and NFS & RPC related
programming questions.
G. Product Features Comparions - This compares the features of
the TCP/IP packages.
H. Information Sources - This is a list of organizations or sources
of information on NFS, XDR, Winsock, lists, etc.
W. Third Party Email - This is a list of commercial and shareware
email packages
X. Xwindows Packages - This is a list of commercial Xwindows
software
Y. Third Party & Related Software - Third party products such as
server software, news, etc.
Z. TCP/IP & NFS products - Commercial and public domain/shareware
TCP/IP & NFS products.
NOTE: Throughout this document all vendors are referred to by their entry
number in section Z, eg.
Z-X refers to entry X in section Z.
-------------------------------------------------------------------------------
*-2. Where can I get this FAQ?
This FAQ is available on the USENET newsgroup, posted once in every two
weeks and also on the following FTP sites:
seagull.rtd.com: /pub/tcpip/pcnfs.FAQ
ftp.york.ac.uk: /pcnfs/FAQ/pcnfs.FAQ
As of August:
bcm.tmc.edu: /nfs
src.doc.ic.ac.uk
ftpserver.massey.ac.nz
-------------------------------------------------------------------------------
*-3. Who helped write this FAQ?
The information in the FAQ is a collection generated from my personal
knowledge and with the help of the following people who I'm very grateful
to:
Geoff Arnold (geoff@east.sun.com) Sun Microsystems
Farid Rahmi (fr@sunbim.be) Sunbim (?)
Marty Udescci (martyu@twg.com) The Wollongong Group
Chip Sparling (chip@ftp.com) FTP Software
Fred Whiteside (fred@bws.com) Beame & Whiteside
C. J. Sacksteder, et. al. (cjs@psuvm.psu.edu) Penn State Univ.
Dean (Dean@frontiertech.com) Frontier Tech.
Winifred Crowther Beame & Whiteside
Kenneth Adelman (Adelman@tgv.com) TGV, Inc.
Bruce Miller (Miller@tgv.com) TGV, Inc.
John Keyes (john.keyes@east.sun.com) Sun Microsystems
Vernon Schryver (vjs@sgi.com) SGI, Inc.
Marc Wiz (mwiz@austin.ibm.com) IBM Corp. (The Core Group)
Dave Fetrow (fetrow@biostat.washington.edu) Univ. of Washington
Fritz Mueller (fritz@netmanage.com) NetManage, Inc.
Zvi Alon (zvi@netmanage.com) NetManage, Inc.
Brian Pawlowski (beepy@ennoyab.eng.sun.com) Sun Microsystems
Edmund J. Sutcliffe (edmund@york.ac.uk) Univ. of York
Erick Engelke - Independent
Giovanni Novelli Xtreme s.a.s
Danny Thomas (vthrc@mailbox.uq.oz.au) Independent
Thomas Dwyer III (tomiii@mtu.edu) Independent
Geert Jan de Groot (geertj@ica.philips.nl) Philips
Francis K. Selkirk (fks@ftp.com) ftp Software Inc.
Alan Arndt (aga@Comtech.com) Comtech Labs
Gavin Longmuir (gavin@sorokin.anu.edu.au) Australian Nat'l Univ.
George Brad Weiner (sales@age.com) AGE Logic, Inc.
George Stump The Wollongong Group, Inc.
Bob MacFadgen (bob@ipswitch.com) Ipswitch, Inc.
Special thanks to:
Edmund Sutcliffe & the University of York for providing an FTP site and his
endless help.
Geoff Arnold for placing the FAQ on the comp.protocols.nfs FTP sites.
C.J.Sacksteder for allowing the use of portions of his document,
"Features of TCP/IP Packages for DOS and Windows"
Brian Pawlowski for allowing the use of his list of bibliographic entries on
papers for NFS, XDR, and RPC.
To any others that I may have forgotten, you have the right to look me up
in Tucson and demand a beer out of me.
-------------------------------------------------------------------------------
*-4. Who maintains this FAQ?
This FAQ is maintained by Rawn Shah. Any additions, clarifications,
modifications and other changes to the FAQ should be directed to me. You can
reach me at any of the following addresses (in order of preferrence):
rawn@rtd.com
rawn@xray1.chem.arizona.edu
You can also contact me at the following postal address:
Rawn Shah
RTD Systems & Networking, Inc.
2601 N. Campbell Ste 202B,
Tucson, AZ 85719
USA
or the following US phone numbers:
Phone: (602) 318-0696
FAX: (602) 318-0695
This FAQ list may not be modified or redistributed under any other name
other than that reserved by the author. You may reproduce the FAQ and
distribute it freely as long as you maintain the original author.
-------------------------------------------------------------------------------
*-5. Who maintains comp.protocols.nfs?
This is an unmoderated USENET newsgroup although there are regular posters
who will be able to help with your questions related to (PC)NFS products.
-------------------------------------------------------------------------------
*-6. Where are the archives for comp.protocols.nfs?
The archives for comp.protocols.nfs are kept at the following FTP sites:
bcm.tmc.edu
src.doc.ic.ac.uk
ftpserver.massey.ac.nz
-------------------------------------------------------------------------------
*-7. Trademarks and Registered names.
AppleTalk, LocalTalk and Macintosh are registered trademarks and MacX and
A/UX are trademarks of Apple Computer Corp.
VMS, and OpenVMS are registered trademarks of Digital Equipment Corp.
ONC, NFS, NIS & PC-NFS are registered trademarks of Sun Microsystems
Computer Corp.
PC/TCP and Interdrive are trademarks of FTP Software Inc.
BW-TCP and BW-NFS are trademarks of Beame & Whiteside Software, Ltd.
IBM, IBM PC, AIX & OS/2 are registered trademarks and LAN Server is a
trademark of International Business Machines, Inc.
Chameleon, ChameleonNFS and Newt are trademarks of NetManage Corp.
DEC, VMS, OpenVMS, DECnet are registered trademarks and eXcursion and
DECwindows are trademarks of Digital Equipment Corporation
TSSNet is a trademark of Thursby Software Systems, Inc.
PathWay, PathWay Access & PathWay Client NFS are trademarks of The
Wollongong Group
SuperTCP is a trademark of Frontier Technologies, Inc.
XVision is a trademark of VisionWare Software Ltd., UK.
eNFS is a trademark of INTERSTREAM, Inc.
AIR is a trademark of SPRY, Inc.
ODI and LAN WorkPlace are trademarks of Novell, Inc.
NDIS, MS-DOS and MS-Windows are registered trademarks and LAN Manager is a
trademark of Microsoft Corp.
MOTIF is a trademark of the Open Software Foundation, Inc.
WINQVT/NET and WINQVT/NFS are trademarks of QPC Software Corp.
HCL-eXceed, HCL-eXceed Plus, and HCL-eXtend are trademarks of Hummingbird
Software, Ltd.
TCPOpen is a trademark of Lanera Corp.
UNIX is a trademark of Unix Systems Laboratories
Multinet is a trademark of TGV, Inc.
PC-Xware & PC-Xview are trademarks of NCD, Inc.
PC-Xsight is a trademark of Locus Computing Corp.
Multiview/X is a trademark of JSB Corporation
PC X-server & PC-Link are trademarks of XLink Corp.
eXodus is a trademark of White Pines Software.
CU/TCP is a trademark of Clarkson University and Rutgers University
NCSA Telnet is a trademark of the National Center for Supercomputing
Applications.
Micro X-Lite is a trademark of StarNet Communications Corp.
AIR is a trademark of SPRY, Inc.
ICE.TCP is a trademark of the James River Group, Inc.
Piper/IP is a trademark of Ipswitch, Inc.
-------------------------------------------------------------------------------
*-8. What do the -, + and * before the questions mean?
The - is used to signify that the question is out of date or has no
information related with it.
The + is used to signify that the question has been recently updated with
new information or corrections have been made to the answer.
The * signifies the question as a new one as of the current FAQ version
-------------------------------------------------------------------------------
*-9. Whats up and coming in the next issue of the FAQ list?
The FAQ is expanding at good rate and I'm still waiting for it to level off.
Coming issues should include:
- a few more TCP products (VxDTCP, DLink, etc)
- a better description of NFS 3 once I finish reading it.
- Cello, trumpet, MacWAIS, etc.
-------------------------------------------------------------------------------
A. Basics
=========
A-1. What is NFS?
Network File System (NFS) is file system that will mount remote file systems
across homogenous and heterogenous systems. NFS consists of a client and
server systems. An NFS server can export local directories for remote NFS
clients to use. NFS runs over IP using UDP (commonly). There are NFS
implementations that will work using TCP as the network transport service.
NFS was originally developed by Sun Microsystems Computer Corp. (SMCC) and
is now part of their Open Network Computing (ONC) initiative. NFS has been
accepted by the IETF in certain RFC's (see question F-X) as a standard for
file services on TCP/IP networks on the Internet.
-------------------------------------------------------------------------------
A-2. What is (PC)NFS?
(PC)NFS is a generic term referring to all NFS systems running on IBM PC and
compatible systems as well as other Personal Computer systems as defined
upon by the X/Open Group.
-------------------------------------------------------------------------------
A-3. Where can I get (PC)NFS for my DOS system?
(PC)NFS for DOS systems is available from the following vendors:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Product Name Vendor Pricing Entry
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
AIR SPRY Z-1
PC-NFS SunSelect *$435 Z-13
BWNFS Beame & Whiteside *$395 Z-2
PC/TCP FTP Corp. *$400 Z-14
IBM TCP/IP IBM Z-17
LAN Manager TCP Microsoft Z-6
PathWay The Wollongong Group * Z-11
SuperTcp Frontier Tech. *$495 Z-16
LAN Workplace Novell $ Z-7
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
* means other pricings available see corresponding entry for product in
Section Z.
-------------------------------------------------------------------------------
A-4. Where can I get (PC)NFS for my MS-Windows system?
(PC)NFS for MS-Windows is available from the following vendors:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Product Name Vendor Pricing Entry
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
AIR SPRY $ Z-1
PC-NFS SunSelect *$435 Z-13
BWNFS Beame & Whiteside *$349 Z-2
Distinct Distinct Corp. Z-5
TCPOpen Lanera Corp. Z-19
PC/TCP FTP Corp. *$400 Z-14
PathWay The Wollongong Group * Z-11
ChameleonNFS NetManage *$495 Z-3
SuperTCP Frontier Tech. Z-16
WinQVT/Net QPC Inc. $40 (shareware) Z-22
$20 (student)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
* other pricings available; see corresponding entry for product in
Section Z.
-------------------------------------------------------------------------------
A-5. Where can I get NFS for my Macintosh system?
You can get NFS clients for Macintosh from:
The Wollongong Group: PathWay NFS [Z-11]
Intercon: NFS/Share [Z-9]
There are also packages for hardware gateways which will allow Macintosh
systems to NFS drive systems. Cayman systems puts out the GatorShare
software for their GatorBox and GatorStar series which gateway LocalTalk
based Macintosh systems onto an Ethernet and allow IP tunneling inside
Appletalk to reach external systems. GatorShare allows Macintoshs to mount
NFS disks as AFP (Apple Filing Protocol) volumes which are displayed as
remote drives on the Apple Chooser. Shiva & Fallaron have similar gateway
(DDP-IP) systems.
IPT has a software only system that works in concert with one of the above
mentioned hardware systems that allow Unix systems to export disks as AFP
volumes. IPT's Partner is not in strict sense an NFS system. It implements
Appletalk on Unix systems and exports drives and printers as Appletalk ones.
CAP (Columbia Appletalk) is a public domain package which has similar
services.
Work is currently in progress to produce a software based DDP-IP package
that will connect LocalTalk Macintoshes through a Mac system with both
LocalTalk & Ethernet interfaces to Ethernet based IP systems. Hopefully the
project will be completed before October. Initial prospects are to
distribute this as shareware.
-------------------------------------------------------------------------------
A-6. What is PC-NFS as opposed to (PC)NFS?
PC-NFS is a specific NFS product for PC systems from SunSelect. PC-NFS is a
registered trademark and so should NOT be used as a generic term describing
all NFS systems on PC's. (PC)NFS is a generic term describing NFS systems on
PC's as decided upon by the members of X/Open.
-------------------------------------------------------------------------------
A-7. What is TCP/IP?
Transmission Control Protocol/Internet Protocol (TCP/IP) is the main
transport protocol used on the Internet for connectivity and transmission of
data across heterogenous systems. It is an open standard which is available
on most Unix systems, VMS and other minicomputer systems, many mainframe &
supercomputing systems and some microcomputer & PC systems.
TCP/IP is a software solution for network connectivity. There is little
assumption on the hardware system used for actual physical connections. The
most common hardware solution is Ethernet, but TCP/IP will also run on
Token-Ring, AT&T StarLAN, microwave & spread spectrum systems , LocalTalk
(needs a gateway), Serial lines (modems, serial connections) and other
systems as well.
To run TCP/IP on a system you first need a hardware driver. On Macintosh
systems, the hardware drivers are built into the system or is provided by
the board manufacturer. On a PC system, there are different types of
hardware drivers available both commercially and via public domain/shareware
including the Packet driver specification by FTP Software, Inc., Microsoft's
Network Device Interface Specification (NDIS), & Novell's Open Datalink
Interface (ODI). Drivers for OS/2 systems are available from IBM and/or the
board manufacturer (if they support OS/2). If a driver is not available for
your hardware, look for a shim. This is a software device which translates
between two driver specifications. There are shims for ODI-on-NDIS,
NDIS-on-Packet driver. ODI-on-Packet driver, etc. usually publically
available.
You then need a TCP/IP stack. This is package specific usually comes with
every product. Each such stack has its own requirements for hardware
drivers. you must find a combination of driver & TCP/IP stack which is
compatible with your hardware & system. Macintosh's do not have a problem
since most Macintosh systems use the MacTCP stack which is available from
Apple and is provided with most if not all Macintosh TCP/IP packages. PC
systems have something close to a standard in TCP applications called the
Windows Sockets API (Winsock). [Note: This is not specific only to TCP/IP it
is a general standard for networking on PC irrelevant of the transport
protocol. Hence, there may be versions for NetBEUI, IPX, etc.]. The Winsock
API is avaialble in 16 bit and 32 bit versions. The 32 bit versions are for
Windows NT systems. Winsock is implemented in Dynamically Loaded Libraries
or DLLs. Currently work is under way to develop a freeware Winsock DLL but
many commercial versions are available.
With the TCP/IP stack in hand, you then need all the TCP/IP application
programs such as Telnet, FTP, mail, etc. Just about every TCP/IP package has
a corresponding set of applications although some do not provide all the
different applications available.
-------------------------------------------------------------------------------
A-8. What is telnet? What is ftp?
Telnet & FTP are two TCP/IP applications for remote host access and remote
file transfer, respectively. Any host with a telnet client can connect to
any host with a telnet server. Any work done within a telnet session is
executed on the server host, thus for most intents and purposes your are on
the remote server, virtually. FTP clients can connect to FTP servers to
transfer files either direction. You can preserve the file contents
independent of the client and server hosts.
-------------------------------------------------------------------------------
A-9. What is a client? What is a server? Why do I need them?
A client application uses resources available on a remote site. This remote
site runs a server for this purpose. NFS is a client-server technology. You
need an NFS client to mount remote disks or directories. The server makes
these disks or directories available for other systems to use. For example,
If you have an NFS client on your PC, you can mount remote drives on your
PC. However, if that PC does not have an NFS server, then you cannot make it
possible for other systems to use your local drive.
-------------------------------------------------------------------------------
A-10. Where can I get (PC)NFS cheap/free/PD?
There are currently no free or shareware NFS _client_ packages
available. Please read [A-X].
SOSS [Y-6] is a public domain NFS _server_ available by FTP.
There are, however, a few different TCP/IP packages available as shareware
and freeware such as WATTCP, NCSA Telnet, CU/TCP, WinQVT (shareware). Please
see the product list in section Z for appropriate referrences.
-------------------------------------------------------------------------------
A-11. What is SOS & SOSS? Where can I get it?
SOS (stan's own server) is the original NFS server developed by See-Mong Tan
and is a public domain nfs server.
SOSS (son of stan's server) is a souped up version of SOS developed by Rich
Braun, et al with better performance capabilities.
SOS is still available although it is advised that you use SOSS when
necessary. SOSS is available at the following site:
grape.ecs.clarkson.edu
-------------------------------------------------------------------------------
A-12. Are there any free NFS clients available for DOS?
There was once a project at the Univ. of Maryland which made an NFS client
for free distribution but is now no longer available.
There have also been reports that NCSA Telnet may come out with an NFS
client in the future but so far there hasn't been any further news on that.
There is a client being developed for the WATTCP package by Micheal Durkin.
This will be released as shareware ($15) in executable format only. Source
code may be available depending on the authors preference.
-------------------------------------------------------------------------------
A-13. What is SLIP?
Serial Line Internet Protocol (SLIP) is a standard on the Internet for
serial line and modem connectivity between two systems. This allows any one
SLIP client to connect to a SLIP server to provide connectivity between
different IP hosts. Both systems must have TCP/IP stacks running. Certain
SLIP packages even allow the SLIP client to act as a gateway between a local
network and a remote network, ie. all machines on the local network can
connect automatically over the SLIP line to remote systems and vice versa.
SLIP packages are available for PC systems. See G-1.
-------------------------------------------------------------------------------
A-14. What is PPP?
PPP (Point-to-Point Protocol) is a direct link protocol which works over
serial lines and direct links similar to SLIP. Overall it gets more
throughput than SLIP. The remote host needs to accept PPP connections and
the local host should act as a client.
-------------------------------------------------------------------------------
Section B. Basics
=================
-------------------------------------------------------------------------------
B-1. What are the different specification types of drivers available?
The following are common specification types of drivers available:
A. Packet drivers - freely available set of drivers on the net maintained by
ftp Software and also in part by Russell Nelson of Crynwyr.
B. NDIS v2.0 & v3.0 - Network Device Interface Specification developed by
Microsoft and 3Com. Version 2.0 is the current version for
MS-Windows and Windows for Workgroups. Version 3.0 is the new
specification for MS-Windows NT.
C. ODI - Open Driver Interface developed by Novell, Inc.
D. SLIP, PPP - These are more protocol specifications for serial and
distance links. Both are defined in the Internet RFCs. PPP is
described initially in RFC 1172 with related descriptions in 1331-1334,
1376-1378, and several newer ones. SLIP is described in RFC 1055.
-------------------------------------------------------------------------------
B-3. What are packet drivers? Where do I get them?
Packet drivers are the link between your Network interface card and your
TCP/IP protocol stack (of each application). They are a low level driver
specification with support for many different Network interface cards.
The packet driver specification is maintained by FTP Software and is
available from:
vax.ftp.com:/pub/packet-d.*
Russ Nelson of Crynwyr, Inc. (nelson@crynwyr.com) also maintains many packet
drivers. He also maintains the FAQ available for packet drivers
on comp.protocols.tcp-ip.ibmpc. This FAQ can be received by ftp from the
following sites:
seagull.rtd.com: /pub/tcpip/other-faqs/pktdrv.faq
-------------------------------------------------------------------------------
B-4. Can I run packet drivers with (PC)NFS?
Yes. See chart G-1 for compatibility with different packages.
-------------------------------------------------------------------------------
B-5. Can I run (PC)NFS over SLIP?
Yes. See chart G-1 for availability in the different products for PC
systems.
Macintosh systems can run NFS/Share from Intercon with the InterSLIP package
copyrighted & freely distributed by Intercon available from:
ftp.intercon.com: InterCon/sales/InterSLIP1.0fc3.sea.hqx
This will run with MacTCP 1.1.1.
-------------------------------------------------------------------------------
B-6. Can (PC)NFS run with NDIS drivers?
Yes. See chart G-1 for availability in the different products.
-------------------------------------------------------------------------------
B-7. Can I run (PC)NFS at the same time as CUTCP or NCSA Telnet?
Yes. You need to run PKTMUX.EXE. This will multiplex connections between two
different applications using packet drivers. PKTMUX allows one to run
multiple TCP/IP protocol stacks.
There is also a version of CUTCP which runs over SunSelect's PC-NFS and is
available via ftp from:
ftp.york.ac.uk:/pub/pc/pc-nfs/cutcp/CUTCP.ZIP
-------------------------------------------------------------------------------
B-8. Can (PC)NFS run with NDIS drivers?
Yes. Please look at chart G-1 for compatibility with different products.
-------------------------------------------------------------------------------
B-9. Can I use (PC)NFS to mount a diskless PC from a remote server?
Yes. The following products have this capability:
PC-NFS
PC/TCP
BW-NFS
AIR for Windows
PC-NFS can be installed partially onto disk to access network applications
like telnet, ftp, etc. placed on a remote server.
PC/TCP also has PROM chips for ethernet cards for diskless PCs to boot with
network services.
In Europe, BOOTP PROMs are available from Dirk Keoppen [dirk@incom.de].
These PROMs support a large number of Ethernet cards and works with many
versions of (PC)NFS including that from SunSelect, FTP Software, Novell and
Microsoft LAN Manager.
-------------------------------------------------------------------------------
B-10. Can (PC)NFS run over token ring?
Yes. See chart G-1 for availability in the different products.
-------------------------------------------------------------------------------
B-11. Can I use my 3C509 Etherlink III card with (PC)NFS ?
Yes. The 3C509 has both NDIS and ODI drivers shipping with the box. Trouble is
some are not where they are supposed to be. The NDIS drivers are in the following directory on the floppy :
A:\MSLANMAN.DOS\DRIVERS\ETHERNET
Also, a packet driver is obtainable for this card (also see B-1)
-----------------------------------------------------------------------------
B-12 Can I PC-NFS SLIP at higher baud rates than 9600 ?
The built-in slip driver will not allow any higher speeds than 9600, but there
is a way around this. Instead of using SLIP.SYS, you can always configure
PC-NFS in packet driver mode (look for the PKTD.SYS shim) and use a shareware
slip driver than conforms to the packet driver specification. Ask archie
about SLIPPER.EXE or ETHERSL.COM.
-----------------------------------------------------------------------------
B-13 Can I access an MSCDEX CD-ROM with PC-NFS ?
No, but you can fool your PC by using an 'MSCDEX simulator', i.e. a small
utility that will redirect the interrupt used by MSCDEX and return constant
values. Does not work will all the published CD's, but is worth the try.
Mounting an ISO9660 CDROM over NFS is not always sufficient to get full access
to the application residing on it. Some utilies refer to MSCDEX for various
reasons. So, can you use the NFS-mounted volume and still have full MSCDEX
access ? No, but you can fool your PC by using an 'MSCDEX simulator', i.e. a
small utility that will redirect the interrupt used by MSCDEX and return
constant values. Does not work will all the published CD's, but is worth the
try. These utils are obtainable from ftp.york.ac.uk (/pub/pc-nfs/CD-rom)
-------------------------------------------------------------------------------
B-14. Can I run NDIS over Packet drivers?
Yes. You can run packet drivers along with the DISPKT9.COM shim and run the
program as a generic NDIS driver.
-----------------------------------------------------------------------------
B-15. Which is better NDIS or ODI?
After a small discussion, it seems that ODI is generally faster and it does
not need be to loaded in the config.sys which helps enormously during
debugging and development).
Both NDIS and ODI are widely available with most Ethernet cards and many
Token-Ring cards as well.
ODI however has one slight problem when it comes to development. Although it
is an "open" specification and is available via ftp, Russel Nelson of
Crynwyr pointed out that:
Message-ID: <744695828snx@crynwr.com>
"
The documentation for Novell's driver development kit is available
from dev_docs/lan_drv. This should not be mistaken for a
specification of an "open" interface. If you want to write an "ODI
driver" (that is, the thing that adapter manufacturers ship), you
must purchase the Lan Driver Development Kit for $7,000. When I
suggested to Novell that they should document the LSL <--> MLID
interface, they seemed somewhat bemused, as if to say "Whyever would
you want that?? -- just buy the DDK!"
Apparently, there *is* no "ODI driver" spec -- Novell doesn't even
have an internal document for the LSL <--> MLID interface.
"
You can FTP the NDIS specification from:
vax.ftp.com
You can FTP the ODI specification from:
sjf-lwp.sjf.novell.com:/dev_docs/{lan_drv, pstacks}/*
[email to Dave Murphy dmurphy@novell.com]
-------------------------------------------------------------------------------
Section C. Server
=================
-------------------------------------------------------------------------------
C-1. What is pcnfsd? What is pcnfsdv2? What is BWNFSD?
PCNFSD is the server software run on remote systems for service access such
as User authorization and print services. PCNFSD is freely distributed. It
was originally designed for SunSelect's PC-NFS software package but has been
accepted by the X/Open committee as a semi-standard for (PC)NFS.
PCNFSDv2 is the current version of this server software.
BWNFSD is an alternate server package from Beame & Whiteside, Inc. which is
also freely distributable.
-------------------------------------------------------------------------------
C-2. Where can I get PCNFSD for my server system?
PCNFSD has been ported to many different platforms. The following is a list
of FTP sites for the different versions:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Platform Location
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SunOS 4.x, Solaris, bcm.tmc.edu
Solbourne, src.doc.ic.ac.uk
NeXTStep ftp.york.ac.uk:/pun/pv/pc-nfs/RPC.pcnfs/*
Ultrix 4.2 bcm.tmc.edu
IRIX/SYSV sgi.sgi.com:/support/pcnfsd.sysV [unsupported]
ftp.york.ac.uk:/pub/pc/pc-nfs/RPC.pcnfsd/*
AIX 3.2 Call IBM and ask for PTF# U412556
AIX 3.2.1 Call IBM and ask for PTF# U419359
AIX 3.2.3 Call IBM and ask for PTF# U414701
MIPS platforms ftp.york.ac.uk:/pub/pc/pc-nfs/RPC.pcnfsd/*
IBM MVS Call IBM and ask for PTF# UY84244 [pcnfsd v1 only]
OpenVMS 5.5 DEC TCP/IP v3.0 [product]
SCO Unix v3.2 SCO NFS [product]
HP 9000 [HP-UX 9.x] HP-UX NFS [product]
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
There is a combined version of PCNFSD v2 for the following systems: Sun,
Ultrix, MIPS, SGI, BSD, SVR4 which is available from
ftp.york.ac.uk:/pub/pc-nfs/RPC.pcnfs/pcnfsd.tar.Z
BWNFSD (V3.0f) is available from:
dorm.rutgers.edu: /pub/msdos/bws/bwnfsd
ftp.bws.com: /pub/bw/bwnfsd
-------------------------------------------------------------------------------
-----------[000019][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 1993 19:21:55 GMT From: rawn@lead.aichem.arizona.edu (Rawn Shah) To: comp.protocols.nfs,comp.protocols.tcp-ip,comp.answers,news.answers,comp.sys.mac.comm Subject: NFS & TCP/IP FAQ for PCs & Macs [part 02/06]
Archive-name: pcnfs-faq/part2
Last-modified: 1993/10/28
Version: 1.5
C-4. How can I test NFS performance?
The following information does not contain information on LADDIS which is a
newer test suite for NFS systems. Please look at C-10 for information on
LADDIS.
The following is a post from the archives from a while back which answers
this directly:
As it turns out, there's a surprising amount of software floating around
that looks at NFS. Such software includes:
nfswatch -- curses-based promiscuous NFS monitor. This program
prints out a running tally of how many of each type of
request comes in, and of which file systems are the most
heavily used. Nfswatch can be used to look at traffic to
individual files, too. This is anonymously FTPable from
icarus.riacs.edu.
server_stat -- a NFS monitor program that runs on Encore Multimaxes.
This shows information on hosts, users, and NFS request
types performed. This is capable of talking to a
rpc.srvstatd process on another machine, though I don't know
of other machines that support the Encore srvstatd program.
nfsstone -- the Encore NFS benchmark, as presented in:
Shein, B., Callahan, M., Woodbury, P., NFSSTONE: A Network
File Server Performance Benchmark, Usenix Summer 1989
conference proceedings, pp 269-275.
This is a synthetic benchmark load, with an empirically-
determined mix of operations.
nhfsstone -- the Legato NFS benchmark. This is also a synthetic
load generator, based again on a particular observed
load mix. You can get this by sending mail like:
To: request@legato.com
Subject: send nhfsstone
path path_back_to_me
I had some problems getting this, though I was ultimately
successful.
NetMetrix (formerly EtherView) --
a Sun-based packet spy that is capable of doing some
characterization of NFS load and response times. This is
a commercial product. For more information, contact:
Hewlett Packard, Network Test Division
One Tara Blvd., Suite 403, Nashua NH 03062
(603) 888-7000
LANWatch -- another packet spy, from FTP Software, Inc. This can
filter out NFS traffic; I don't know what can be done with
the packets though once they're filtered out. For more
information, call FTP at (800) 282-4FTP, or send mail to
info@ftp.com.
[ There's lots of other packet spies, too, and I suspect that most
of them can do at least a little bit with NFS packets. ]
The problem with most of the programs above (except for the synthetic
loads, to which this just doesn't apply, since they're not NFS monitors) is
that you don't get raw data points which you can then analyze. You get the
data that the authors thought you might want... and which might not be what
you really want. There's much to be said for the approach of dumping traces
and lots of timestamps into a file, then providing (a) programs that analyze
such files, and (b) the format of the files, so that people can write their
own analysis programs. On a PC-based packet spy, this is a hard thing to
do.
There's a fair number of people (at the major NFS server vendors, Sun,
DEC, and a few universities) who are also poking around at the problem.
Some people are looking at filesystem activity tracers, which (in addition
to being interesting research on its own) could provide still more reams of
interesting statistics when combined with a NFS tracer.
The consensus was that the best way to trace NFS operations is to do so
via a promiscuous packet spy. Such an approach has many advantages. First,
if you don't have kernel sources, you can still get useful information.
Second, because you don't instrument the server kernel, you don't have to
worry about influencing the experiment in adverse ways. However, there's
some chance (depending on your hardware and on how fast you make your
software go) that you'll drop packets. The 'hack the server kernel'
approach won't drop any requests, but violates the above constraints. I
suspect that the best way to gather statistics is by using *both* methods of
measurement, then comparing the results.
I was also referred (twice) to the SunOS 4.1 NFS implementation, and in
particular the adaptive NFS retransmission code therein. These numbers might
be interesting to see, once 4.1 is more easily available.
Of course, the usual Unix file access pattern (i.e., lots of short-lived
files in /tmp, most of which get written, then read once, then deleted)
information applies. This was mentioned by several people; one reference
given was:
Floyd, Rick, Short-Term File Reference Patterns in a UNIX Environment,
University of Rochester Department of Computer Science TR 177,
March 1986.
Another good paper (with not much data on NFS, though) is:
Lazowska et al, "File Access Performance of Diskless Workstations",
ACM TOCS, volume 4, number 3, August 1986, pp 238-268.
Not a whole lot was said about general models of NFS access. Most places
that had any models had derived them from some number of studies and from
the output of nfsstat, or so it seemed. It does seem that there's a few
general trends, however. There are some sites (including ours, I suspect)
that fall into the low-utilization, few write model, where the server rarely
satisfies more than one client's NFS requests in some given time slot.
There's also the high-utilization, many write model, which is what I'm sure
a lot of sites see. One responder said that once one's clients have enough
memory, the buffer cache ends up reducing the number of random reads going
on, so one is left with the reads that happen to start up a new process, and
with writes.
Those who talked about models generally said that they think there's
almost as many models as there are networks using NFS. I suspect that this
is true, but that perhaps some useful information (or at least methods) can
be abstracted out, regardless.
A number of people also suggested that I talk to Legato and to Auspex and
see what they've done in this area. I have a couple of papers from Auspex;
at a first glance, I don't think they look too closely at NFS load
characterization (at least, not as I define that), but instead concentrate
on what Auspex did to get better speed out of their NFS file server. The
Auspex paper titled, "Benchmark Methodology and Preliminary Performance
Specifications for the Auspex NS5000 Network Server" (Bruce Nelson, Auspex
TR #2, October 1989) has more load characterization information than do the
other Auspex TRs I have, but it still doesn't have a whole lot. (By the
way, I'm not implying that Auspex hasn't looked at load characterization,
because they obviously have. I just don't have the fine details of their
results.) I also did some talking with people at Legato; their comments and
models show up in the nhfsstone benchmark, or are otherwise repeated above.
-Steve
Spoken: Steve Miller Domain: steve@umiacs.umd.edu UUCP: uunet!mimsy!steve
Phone: +1-301-454-1808 USPS: UMIACS, Univ. of Maryland, College Park, MD 20742
-----------------------------------------------------------------------------
C-5. What is NHFSSTONES? Where can I get it?
"Nhfsstone" (pronounced n-f-s-stone, the "h" is silent) is a
copyrighted product of Legato Systems, Incorporated and is provided for
unrestricted use and distribution of the binary program derived from
it.
nhfsstone is a NFS load generating program. It is used on an NFS client
to generate an artificial load with a particular mix of NFS operations.
It reports the average response time of the server in milliseconds per
call and the load in calls per second. The program adjusts its calling
patterns based on the client's kernel NFS statistics and the elapsed
time. Load can be generated over a given time or number of NFS calls.
The current version of the program can only be compiled on 4.x BSD
based UNIX systems.
To obtain the nhfsstone source shar file, send email to
"request@Legato.COM" or {sun,uunet}!legato!request. The Subject line
and/or body of the message should have contain the command line:
send unsupported nhfsstone
Note the exact spelling of "nhfsstone". To issue delivery, you should
also add a line of the form:
path <address>
where <address> is the preferred email address to use. Generally,
using a domain-style email address works best. A uucp path starting
with "sun!" or "uunet!" can also be used.
Joseph Moran
Legato Systems Inc.
260 Sheridan Avenue
Palo Alto, CA 94306
(415) 329-7886
mojo@Legato.COM or {sun,uunet}!legato!mojo
-------------------------------------------------------------------------------
C-7. How many nfsd's & biod's should I run on my server?
Default number of nfsd's & biod's is 8
Suggested Equation for nfsd's is:
[number of disks exported] + [number of network interfaces]
Suggested maximum number of nfsd's runinng on a Sun system (SunOS 4.x) without any
accelerators is 22. Any more does not help in performance.
-------------------------------------------------------------------------------
C-8. What is asynchronous I/O? How can I modify my NFS server system to use
asynchronous I/O?
Asynchronous I/O (ASYNC) means that information comes and leaves at unannounced
intervals whereas synchronous I/O (SYNC) has a predetermined interval when
I/O can actually pass.
NFS has been used both through SYNC and ASYNC communications. The original
specification stated that SYNC I/O should be used although did not bind to
it. This results in slower communications during transfers. ASYNC creates
problems in that, if for some reason communications should fail (eg., your
NFS server crashes), there may be inconsistency in the data. The bright side
of ASYNC is that performance increases by a great deal.
Many implementations of NFS using asynchronous I/O are available. Despite
the disadvantage, the number of complaints about data loss due to this are
far fewer than the reports of performance increase. However, be warned that
asynchronous I/O is a direct violation of the NFS specification from X/Open
which states that all procedures of the NFS protocol are synchronous. This
makes such a server no longer compliant to X/Open
-------------------------------------------------------------------------------
C-9. What is a good NFS server?
Network Appliances Corp have recently come out with a product which they
call an NFS appliance, the FAServer. It is a 486 based system with an EISA
bus, 16 MB RAM, 2 MB NVRAM, and a RAID subsystem. The RAID subsystem keeps
up to 20 logical copies of the entire file system. They have a proprietory
operating system which does only simple management and disk serving.
The pricing is about $20,000.
-------------------------------------------------------------------------------
C-10. What is LADDIS?
LADDIS is multi-vendor and vendor neutral SPEC NFS Benchmack designed by
engineers from Leato, Auspex, Data General, DEC, Interphase and Sun [LADDIS
is an abbreviation using their first letters]. This covers local Ethernet or
FDDI nets and not WAN.
An excerpt from the LADDIS abstract:
"
The purpose of the LADDIS benchmark is to give users a credible and
undisputed test of NFS performance, and to give vendors a publishable
standard performance measure that customers can use for load planning,
system configuration, and equipment buying decisions. Toward this end,
the LADDIS benchmark is being adopted by SPEC (the System Performance
Evaluation Cooperative, creators of SPECmarks) as the first member of
SPEC's System-level File Server (SFS) benchmark suite."
"
LADDIS is available directly from SPEC. Here is the contact person:
Name: Dianne Dean (SPEC contact person at NCGA)
Phone: 703-698-9600 Ext 318
Fax: 703-560-2752
Email: spec-ncga@cup.portal.com
Mail: SPEC
c/o NCGA
2722 Merrilee Drive, Suite 200
Fairfax, VA 22031-4499
There is about a $1000 charge for the distribution tape.
-------------------------------------------------------------------------------
C-11. What is XRemote & LBX?
These are specifications for running the X11 windows system over lower
bandwidth connections like serial lines.
XRemote is a private specification developed by NCD. Inc. It is available in
commercial packages.
LBX (Low-Bandwidth X) is the specification also contributed by NCD to the
X11 standard forthcoming next year, ie. X11R6. You can get information on
LBX via FTP from:
export.lcs.mit.edu:/contrib/LBX-xconf93-paper.ps.Z
This is not a formal document only an informative disclosure.
Running a low bandwidth X protocol over something like Ethernet would not be
useful since the compression algorithms involved would incur additional CPU
usage and so you would not get much of a performance advantage at all.
-------------------------------------------------------------------------------
Section D: Applications
=======================
-------------------------------------------------------------------------------
D-1. Where can I get mail with (PC)NFS?
POPmail versions 2 and 3 and SMTP are the most common mail protocols for
(PC)NFS and TCP/IP systems for PCs. Please look at the chart G-3 for mail
systems.
Here are some additional third-party mail packages that work with PC-NFS:
a. Open Systems Mail by Pinesoft (US) [pinesoft@netcom.com]
b. Mail-It by Unipalm (UK) [tomk@unipalm.co.uk]
Tom Kermeen
Unipalm Ltd
216 Cambridge Science Park
Milton Road
Cambridge CB4 4WA
UK
+44 223 420002
+44 223 426868 [FAX]
[Site license is available for L5000 (five-thousand pounds)]
Distributed in the US by:
Unipress Software
2025 Lincoln Highway,
Edison, NJ 08817
USA
(800) 222-0550
info@unipress.com
c. WinELM was written by Peter Churchyard of Imperial College,
London. It is available for winsock systems from the ftp site
ftp.york.ac.uk:/pub/pc-nfs/Mail/winelm.zip
lister.cc.ic.ac.uk:/pub/winelm
There are also DOS, PC-NFS and WinSock API versions there.
d. ECSMail is a commercial package which supports IMAP & MIME
contact steve@edm.isac.ca. I also supports Macintosh & Unix
You can get a demo version of ECSMail from
ftp.york.ac.uk:/pub/pc-nfs/Mail/ecs.zip
[The demo requires an IMAP daemon such as in the Pine mailer]
e. Cin'etic Mail Manager works directly with mounted file systems
and sends mail via different setups like rsh on PC-NFS. Its
publicaly availble via ftp (cmm21f.zip). You can also contact
them at:
Cinetic@speedy.cam.org
71460,666 (Compuserve)
This package currently supports PathWay, PC/TCP, PC-NFS, FSUUCP
by Fubar Systems, UUPC/extended by Drew Derbyshire. Its
configuarble for other systems as well.
In addition, for mail arrival notifiers, there is WinBiff (version 1.6)
for MS-Windows 3.x that works with PC-NFS, UUPC, Waffle and FSUUCP. This is
available from:
ftp.cica.indiana.edu: /pub/pc/win3/mirrors/wnbff16.zip
wsmr-simtel20.army.mil: PD1:<MSDOS.WINDOWS> WNBFF16.ZIP
-------------------------------------------------------------------------------
D-2. Where can I get a news client for (PC)NFS?
USENET News (NNTP) clients are available specifically from:
Super-TCP [Z-16] - Windows version
WinQVT [Z-22] - Windows version
Chameleon [Z-3] - DOS version.
There is a public domain program called WinVN which uses the Winsock API.
This means that just about any product which has the Winsock.dll should be
able to run it. It is available from:
sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps/winvn.zip
Trump and WinTrump are other popular packages for news available from
sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps/*
A simple news client by Stan Barber and a client by Kjettil Otter Olsen
(with source code) are avalable from
ftp.york.ac.uk:/pub/pc-nfs/news
WinVN is a newsreader for Windows 3.x systems publically available from:
titan.ksc.nasa.gov: [anonymous.pub.win3.winvn] (Its a VAX host)
Macintosh newsreaders include:
TheNews
Newsreader
MacNews
Nuntius
All are available from:
mac.archive.umich.edu:/mac/util/comm/*
-------------------------------------------------------------------------------
D-3. Where can I get an FTP server for (PC)NFS?
The following systems have FTP servers:
BW-TCP, PC-NFS, PC/TCP, Chameleon, PathWay, Super-TCP, IBM TCP/IP, Lanera TCP
-------------------------------------------------------------------------------
D-4 Where can I get RWALL for my (PC)NFS system?
As far as memory serves me there currently are no implementations of the
rwall command as in Sun ONC on (PC)NFS systems, except possibly one for
the Macintosh NFS/Share product from Intercon.
Sorry folks. If anyone has information on this one please mail me, there are
people who want to know.
Here is what Geoff Arnold had to say about it back in 1989:
"
One of the questions I am often asked about PC-NFS is "how come
there's no way for me to find out when a particular file server
is going down? Unix users get notified." I point out that (at least
on SunOS) the mechanism used is "rwall", which is an RPC service, and that
for size reasons we can't afford to embed a version of rpc.rwalld in
PC-NFS. This explanation is reasonable, but unsatisfactory.
My reaction was to say "let's ask the NIC for a UDP port so that
we can use it to send unsolicited messages to PCs running PC-NFS."
That would certainly do the trick. However, a moment's thought
reveals that the problem is bigger than just PC-NFS. Surprisingly,
there is at present no simple ubiquitous message protocol to fulfil this
function. rwall is fine for SunOS and other ONC licensees, but
what about other systems? Do I have to rely upon SMTP? That's
incompatible with the idea of broadcasting a simple message
such as "The backbone will be down for five minutes at 12:00
to replace a bridge."
This could be trivially simple or slightly more involved
(but still simple). The trivial approach is to dedicate
a UDP port for unsolicited system messages. Anyone could send one,
in a single datagram, and the listener process would be responsible
for delivering it as seemed appropriate for the system (dialog
box, console message, etc.) A more complete approach would be to
define a formal protocol so that it would be possible to convey
information about the coding of the message, message length (so that
TCP could be used instead) and so forth. [If the spec exceeds
one page, it's too complicated.]
Comments?
Geoff
"
-------------------------------------------------------------------------------
D-5. Where can I get an INT-14 redirector for (PC)NFS?
INT-14 redirectors are available with various (PC)NFS products including:
BW-NFS [Z-2]
PC/TCP [Z-14]
Chamelon NFS [Z-3]
There is a version for PC-NFS v5.0 (by Geoff Arnold) at:
ftp.york.ac.uk:/pub/pc-nfs/utils/int14/*
sorokin.anu.edu.au:/pub/nfs5-addons/int14.zip
An INT-14 redirectory for WATTCP is available from:
dorm.rutgers.edu:/pub/msdos/wattcp/apps.zip
-------------------------------------------------------------------------------
D-6. Where can I get YPPASSWD for PC-NFS?
There is a version of YPPASSWD for PC-NFS v5.0 at:
ftp.york.ac.uk:/pub/pc-nfs/utils/yppasswd/yppasswd.zip
-------------------------------------------------------------------------------
D-7. Where can I get IBM 3270 terminal for (PC)NFS?
Please see chart in section G-1 under TN3270.
-------------------------------------------------------------------------------
D-8. Where can I get X-Windows for (PC)NFS?
The following X-windows products are available:
For DOS:
Product Cost Company Version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Xvision $395 VisionWare Soft, Inc X11R5
PC-Xware $545 NCD, Inc. X11R5
PC DECwindows ?? DEC X11R4
PC Xsight ?? Locus Computing X11R4
Micro X-Lite $75 StarNet Comm. Corp. X11R4
X Appeal $350 Xtreme X11R5
Xoftware ?? AGE Logic X11R4
PC X-Kit $249 XLink X11R5
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
For MS-Windows:
Product Cost Company Version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
HCL-eXceed ?? Hummingbird Software X11R5
eXcursion ?? DEC X11R5
MultiView/X ?? JSB Corp. X11R4
PC-Xview $445 NCD Inc. X11R5
Xoftware ?? AGE Logic X11R4
eXodus $295 White Pine Software X11R5
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
For Macintosh:
Product Cost Company Version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
MacX ?? Apple Computer Corp. X11R5
eXodus $295 White Pines Software X11R5
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
For OS/2:
Product Cost Company Version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
X Windows $150 IBM X11R5
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-------------------------------------------------------------------------------
D-10. Where can I get a database that works with (PC)NFS?
Any database would be able to use the NFS mounted drive as long as it
recognizes it as a local drive. Most network versions of a database however
will not work unless they specifically say they support (PC)NFS & TCP/IP.
DBMS's known to work with (PC)NFS include SQL*Net (Oracle), and Sybase for
DOS.
PC-NFS is known to work with Paradox for Windows & DOS for network file
storage.
-------------------------------------------------------------------------------
D-11. Where can I get a WAIS client for (PC)NFS?
WAIS Manager 3.0 by Kebin Gamiel (representing MCNC CNIDR and UNC-Chapel
Hill) has recently been announced which is WinSock compliant. Features
include multi-format handling capability, relevance feedback and a new
interface with Toolbar for quicker access.
You can get this via ftp from:
sunsite.unc.edu: /pub/micro/pc-stuff/ms-windows/winsock/apps/waisman3.zip
ftp.cnidr.org: /pub/NIDR.tools/wais/pc/windows/waisman3.zip
There is a WAIS client for PC/TCP at:
calvin.sfasu.edu: /pub/dos/network/pc-tcp/wais.zip
WinWAIS is another winsock version of WAIS by EINET
is available from:
ftp.einet.net:/einet/pc/*
sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps
MacWAIS is a MacTCP compatible application for System 6 and 7 by EINET:
ftp.einet.net:/einet/mac/*
-------------------------------------------------------------------------------
D-12. Where can I get an archie client for (PC)NFS?
A ported version of c-archie is available for PC-NFS at the ftp sites:
bcm.tmc.edu: /nfs/archie.exe
ftp.york.ac.uk:/pub/pc-nfs/utils/archie.exe (has source as well)
This version works for PC-NFS v4.0a
There is a version for PC/TCP at:
calvin.sfasu.edu:/pub/dos/network/ftp-pctcp/archie.zip
-------------------------------------------------------------------------------
D-13. Where can I get a gopher client for (PC)NFS?
nfsgopher is available from bcm.tmc.edu in /nfs which will work with PC-NFS
gopher for MS-Windows is available for PC-NFS systems in an alpha release
from the ftp site:
lister.cc.ic.ac.uk: pub/wingopher/{readme.txt,gopher.exe}
ftp.york.ac.uk:/pub/pc-nfs/utils/gophersfx.exe
source available in ftp.york.ac.uk:/pub/pc-nfs/utils/gofer.zip
HGopher (Hampson's Gopher) is a client for gopher systems. The following
version has been tested at ANU:
sorokin.anu.edu.au: /pub/nfs5-addons/hgopher.exe
It is originally distributed from:
lister.cc.ic.ac.uk: /pub/wingopher
There is a gopher client for PC/TCP at the following site:
calvin.sfasu.edu:/pub/dos/network/ftp-pctcp/goph1_05.exe
gophbook from UNC is an Asymetrix Toolbox application which uses winsock.dll
and is available from the ftp site:
sunsite.unc.edu: /pub/micro/pc-stuff/ms-windows/winsock/apps/gophbook.zip
-------------------------------------------------------------------------------
D-14. Where can I get a WWW (World Wide Web) client for (PC)NFS?
There is a version of such a client for PC-NFS at
ftp.york.ac.uk:/pub/pc-nfs/utils/wwwpcnfs.zip
Winsock clients are now commonly available and should work with any PC
TCP/IP system which supports winsock. Some winsock clients are Cello and
NCSA Mosaic.
-------------------------------------------------------------------------------
D-15 Where can I get X25 for (PC)NFS ?
The Software Forge developed a PC/TCP-IP adapter for X25, which is a hardware/
software bundle that :
- conforms to PDS specification 1.09
- conforms to RFC 877/1356 (TCP-IP over X25)
- supports PC/TCP and PC-NFS (probably any PDS-compliant software)
- does address resolution of 100 Internet adresses (expandable)
- can have up to 20 simultaneous sessions
For more information, contact UniPalm (+44(0)223250100) or unipalm@unipalm.co.uk
The Software Group Ltd also makes X.25 software for PC systems. They can be
contacted at:
2 Director Court, Suite 201
Woodbridge, Ontario,
Canada L4L 3Z5
(418) 856-238
(418) 856-0242
or email scott@group.com
There is also an X.25 package available with Super-TCP from Frontier
Technologies [Z-16].
-----------------------------------------------------------------------------
D-16 Where can I get NEWGRP.EXE for PC-NFS ?
NEWGRP.EXE is a utility written by Geoff Arnold that does the equivalent of
the Unix newgrp command. See man newgrp if you are really interested. It can
be ftp-ed from some of the ftp sites found in C-2.
-----------------------------------------------------------------------------
D-17 Where can I get AUTOCONF for PC-NFS ?
AUTOCONF is a shareware utility designed and implementes by Henk Swaters that
allows system administrators to define an NIS map (pcnfs.config) that holds
the equivalent of DRIVES.BAT. The NIS map works on a user-basis and the mounting
and unmounting of existing resources is performed trough a single .EXE file.
AUTOCONF.ZIP is available on ftp.york.ac.uk in /pub/pc-nfs. You do need at least
PKUNZIP 2.04G to unzip it. What follows is the README.
AUTOCONF 14-06-93
autoconf utility for pcnfs
==========================
NAME
autoconf.exe - configure PCNFS-client network drives and printers
DISCRIPTION
This program is made to configure the network drives and printers
of a PCNFS-client from the NIS database. The name of the NIS-map
is pcnfs.config. Each line of the pcnfs.config file defines user
or group information and has the format
username/groupname list-of-drives/printdevices
where list-of-drives/printdevices is either another username/
groupname, or a network drive/printdevice:
(drive:,hostname:/path,/option,option..)
or
(printdevice:,hostname:printername,/option,option..)
example:
----------------------------------------------------------------
all\
(g:,calibra:/export/MSDOS/WinEnv)
printer_staff\
(lpt1:,pslw1:lw1,/fmt=raw)
smith\
all (f:,calibra:/export/MSDOS/DosEnv)\
printer_staff
----------------------------------------------------------------
When user smith executes autoconf.exe he mounts the following
environment:
g: calibra:/export/MSDOS/WinEnv
f: calibra:/export/MSDOS/DosEnv
lpt1: pslw1:lw1 /fmt=raw
USAGE
A known user has to be logged in, otherwise the program
terminates. If the program is executed without any options
the username is used as keyvalue. It is possible to give
one or more keyvalues as argument of the program. These
arguments can be either usernames or groupnames. By Default
the program unmounts a drive before mounting a new drive on the
same device. The argument /n or /nounmount switches this
option off. The argument /h or /help prints out a help screen
and terminates the program. There will be no mount or unmount
command.
example with the same auto.config as above:
autoconf printer_staff /n
or
autoconf /nounmount printer_staff
These equivalent commands try to mount:
lpt1: pslw1:lw1 /fmt=raw
There will be no unmount command and if there is already
a network device on lpt1: there are no changes made.
AUTHOR
Henk Swaters Dept. of Computer Science University of Twente.
swaters@cs.utwente.nl
HISTORY
autoconf.exe
-------------
14-06-1993 verion 1.0
-------------------------------------------------------------------------------
D-18. Where can I get a remote backup utility for (PC)NFS?
WATTCP has a backup utility called "rtar" with its applications
distribution.
The following commercial packages have similar facilities:
PC/TCP, Super-TCP, BW-TCP, Lanera TCPOpen, XLink PC-Link
-------------------------------------------------------------------------------
D-19. Which (PC)NFS packages support DNS [named]?
Please see the chart Z-3.
-------------------------------------------------------------------------------
D-20. Where can I get a traceroute program?
BW-TCP [Z-X] has a traceroute program with their package.
There is a traceroute program available for WATTCP at:
polysla.calpoly.edu:/pub/mdurkin/trtb91b.zip
This is for an older version of WATTCP but is being converted to the new
version currently.
-------------------------------------------------------------------------------
D-21. Where can I get an LPD program?
For commercial and some PD packages which have an LPD program please look at
the chart G-4.
There's a Winsock-compliant LPD called NLPD available via ftp from:
sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps/wslpd.exe
A PC-NFS LPD version is in ftp.york.ac.uk:/pub/pc-nfs/utils
-------------------------------------------------------------------------------
Section E: Problems & General Q&A
=================================
-------------------------------------------------------------------------------
E-2. Can I use DNS instead of NIS with PC-NFS?
No. PC-NFS currently only supports the Sun ONC NIS product. (Even NIS+ is
not fully compatible).
DNS is available with other packages.
-------------------------------------------------------------------------------
E-3. Why do versions of (PC)NFS not follow symbolic links?
This is because according to the NFS definition, filenames are handled by
the NFS client. In some (PC)NFS if the files in the symbolic links may not
be in the same exported directory as the directory the link is in. NFS
mounted files appear as drives on the clients and the clients cannot parse
any files which appear higher up on the tree or on a different tree segment
than that of the NFS exported drive (from the server).
Certain versions can be clever enough to counter this problem by their own
methods but it is generally accepted that (PC)NFS systems do not support
symbolically linked files.
-------------------------------------------------------------------------------
E-4. PC-NFS v4.0 has trouble with Cntl-S, Cntl-Q.
This has been fixed in release 4.0a and 5.0. For 4.0a please look at the ftp
sites [H-5]
-------------------------------------------------------------------------------
E-5. PC-NFS v4.0 has trouble with redrawing windows.
This has been fixed in release 4.0a and 5.0. For 4.0a please look at the ftp
sites [H-5]
-------------------------------------------------------------------------------
E-6. PC-NFS v4.0 doesn't allow me to access the local printer when I have
network printers.
This is because the default setup for printers in PC-NFS v4.0 is as a
network printer. In the print manager choose the printer and change the
setup. At the bottom of the setup screen for the printer should be a
checkbox indicating that it is a network printer. Uncheck this box.
-------------------------------------------------------------------------------
E-7. I cannot delete any file that PC-NFS makes with a ~ (tilde) in it.
To get rid of the problem, in your config.sys, run pcnfs.sys as:
C:\NFS\PCNFS.SYS /c^
where c reassign the immediately following character. [In this case to the
character '^']
-------------------------------------------------------------------------------
E-8. PC-NFS says that it cannot open any more files even when the limit in
autoexec.bat is set higher.
PC-NFS uses its open own file limit and not the DOS system open file limit. To
modify this limit use the /f flag as such in the config.sys:
C:\NFS\PCNFS.SYS /f50
The limit here is set to 50. The maximum is 64.
-------------------------------------------------------------------------------
E-9. Can (PC)NFS mount file systems which are bigger than 2 GB?
Most server file systems do not handle such large file systems, but this is
possible with various software enhancements like Disk-Suite for Sun systems.
NFS clients on the other need not know how big the actual remote file system
is. It only receives information on how big the individual files are and not
the file system itself.
The Network Appliance server has one partition under which all drives can be
mounted for NFS exportation.
-------------------------------------------------------------------------------
E-10. What is NFS/TCP? Will it work with my NFS product?
NFS/TCP is a different type of the original NFS protocol which uses the TCP
protocol as opposed to the originally specified UDP protocol. NFS over UDP
works well over a single LAN but is as not suitable for multiple LANs or
WANs as NFS/TCP. TCP's windowing of packets capability and reliability gives
it an advantage. In UDP dropped packets are not acknowledged between the two
hosts, however, TCP retransmits all dropped packets. One more aspect of TCP
(which is more idealistic than real) is the congestion control capacity
between routers for TCP which prevents overflooding of a congested network
link. In NFS/UDP it is easy to create UDP data which look like NFS requests
from other machines. However, TCP makes it much more difficult to add
falsified packets which impersonate another machines data.
The problem with NFS/TCP is that it is incompatible with NFS/UDP. Therefore
all servers running the TCP version will be invisible to clients running a
UDP version and vice versa.
NFS/TCP is available in PC/TCP and BWNFS.
-------------------------------------------------------------------------------
E-11. What is PKTD.SYS? Where can I get it?
PKTD.SYS is a shim that allows PC-NFS to use packet drivers instead of its
native drivers. It is available from:
bcm.tmc.edu
src.doc.ic.ac.uk
ftpserver.massey.ac.nz
ftp.york.ac.uk:/pub/pc-nfs/pktd/pktd.zip
The current version is 5.0.
-------------------------------------------------------------------------------
E-12. How can I run Netware 3.xx at the same time as (PC)NFS using NDIS?
You can run the NDIS-over-ODI shim available from Novell that will let you
run netware at the same time as any other product running NDIS (ie. many
(PC)NFS products.
-------------------------------------------------------------------------------
E-14. Is it possible to modify the read & write buffer sizes in (PC)NFS?
Different (PC)NFS systems have different sizes with default at 1024 Kbytes
for both. The standard maximum is 8 KB.
In PC-NFS, read buffer size is fixed (1024KB) but you can modify the write
size to any thing below this maximum. Currently anything less than 128 bytes
is cached into a 256 byte datagram. Anything more than this is passed as its
specific size.
PC/TCP, PathWay Client NFS & BWNFS allow modification of read & write buffer
sizes.
-------------------------------------------------------------------------------
E-15. How can I install an Ethernet board not supported by (PC)NFS?
Contributed by Farid Rahmi:
If you're installing on an IBM PC or compatible, you can use NDIS drivers in
general for your Ethernet board.
Although I only upgraded to 5.0 after installing a beta version of 5.0
on my 3C509 PC, the procedure should still be the same :
1) Get the NDIS driver, the PROTOCOL.INI and the .NIF file from the LANMAN
directory off the floppy that shipped with the 3C509 and copy these three
files onto your harddisk (*NOT* in C:\LANMAN !!!, see below)
2) Select NDIS during installation.
3) This should wake up QUIKNDIS, which will transform PROTOCOL.INI for you
and put it in C:\LANMAN together with the NDIS driver.
Three remarks :
- If you have an EISA machine and an ISA 3C509, please RTFM before complaining
about lockups.
- I noticed that QUIKNDIS would scratch (make zero byte file) the NDIS driver
if placed into C:\LANMAN. As mentioned, this was in the beta release.
- Too bad SunSelect couldn't ship the drivers with 5.0. Seen most of the other
vendors ship these drivers and they are publicly available (ftp.3com.com)...
Farid (fr@sunbim.be)
-------------------------------------------------------------------------------
-----------[000020][next][prev][last][first]---------------------------------------------------- Date: 1 Nov 1993 19:23:15 GMT From: rawn@lead.aichem.arizona.edu (Rawn Shah) To: comp.protocols.nfs,comp.protocols.tcp-ip,comp.answers,news.answers,comp.sys.mac.comm Subject: NFS & TCP/IP FAQ for PCs & Macs [part 03/06]
Archive-name: pcnfs-faq/part3
Last-modified: 1993/10/28
Version: 1.5
E-16. In postscript files I sometimes get a ^D before the header from my
programs. How do I get rid of it?
This happens mostly on PC systems sending output to postscript printers.
The ^D is the EOF character and sometimes causes a blank page to be output
by the printer before the print job. It can be disabled by the following:
In your WIN.INI file, add below [yourprintername, port] this line:
CTLD=0
If you wish to do this permenantly for all windows systems, you can
reprogram your printer with the following piece of Postscript code (Thanks
to Mark Fleming of Queen's Univ.). Send this as a file to your printer:
%!
%%Title: CTRL-D serial EOF (End-of-File) character fixed
%%Creator: R. Mark Fleming
%%+ Queen's University at Kingston
% Check if EOF is installed, if not install it
% assumes serverloop password is the default one
currentdict % Get current dictionary
(\004) cvn known
{ % Check if CTRL-D defined in this dictionary
(%% CTRL-D procedure already installed\n %%) print
} {
(%% CTRL-D procedure not installed!\n %%) print
% Define IBMpc (serial) EOF character to do nothing
serverdict begin
0 exitserver % Make permanent changes
(\004) cvn
{} def % To ignore ^D at the end of prologs.
} ifelse
%%EOF
-------------------------------------------------------------------------------
Section F: Programming
======================
-------------------------------------------------------------------------------
F-1. Is there a toolkit for (PC)NFS programming? Where can I get it?
Until recently, programming toolkits were developed independently by vendors
alongside their products. Due to the efforts of different persons and
organizations there is a formal definition of MS-Windows in the Windows
Sockets API. The current version is 1.1. This is only a standard and product
vendors are allowed to distribute their own programming toolkit. Most are
now developing or selling Windoes Sockets API compatible toolkits. Please
refer to the chart G-3 for products with Windows Sockets API.
Certain libaries for mounting drivers and user authentication with PC-NFS
5.0 are available on
ftp.york.ac.uk:/pub/pc-nfs/dnet/DNET50.tar
-------------------------------------------------------------------------------
F-2. What is Windows Sockets (winsock)? Where can I get it?
Windows Sockets is an API developed by a group of NFS vendors as a standard
for future network based communications in MS-Windows. The current version
of the API is 1.1. Further information for this is available on request.
Mail all questions and comments to "winsock@microdyne.com". To join the
mailing list, mail to "winsock-request@microdyne.com". Windows Sockets API
documentation and related documents are available by ftp to:
microdyne.com: /pub/winsock
sunsite.unc.edu [Mirror site of the above address and much
faster and up 24 hrs]
Peter Tatham (developer of the Trumpet newsreader) has developed an alpha
release of winsock.dll which uses a packet driver as the network driver. Its
currently available from ftp.utas.edu.au:/pb/trumpet. This winsock will be
used in the developement of WinTrumpet.
-------------------------------------------------------------------------------
F-3. What is the latest version of the NFS protocol?
The current official version of the NFS protocol is version 3. It has just
recently come out and is being tested at this years Connectathon.
A Postscript file is available from:
ftp.uu.net:/networking/ip/nfs/NFS3.spec.ps.Z
bcm.tmc.edu:/nfs/nfsv3.ps.Z
gatekeeper.dec.com:/pub/standards/nfs/nfsv3.ps.Z
All comments and questions should be mailed to: nfs3@eng.sun.com
-------------------------------------------------------------------------------
F-4. What is new in version 3 of the NFS protocol?
New features of version 3 are:
- 64bit support
- exclusive creates,
- asynchronous writes (I guess its official now Vernon)
- improved attribute caching
- the "ACCESS" command works on the server attributes as well
- relaxed transfer size restrictions.
- reduced required "GETATTR" operations.
More information to come later.
-------------------------------------------------------------------------------
F-5. What is the current RPC version? Where can I get it?
The current version of RPC is 4.0. It is available at the ftp sites:
bcm.tmc.edu
src.doc.ic.ac.nz
ftpserver.massey.ac.nz
There is a version 4.0 which works with WATTCP which is available from
polyslo.calpoly.edu:/pub/mdurkin/rpc01a.zip
-------------------------------------------------------------------------------
F-6. Where can I get the XDR/RPC definition for PCNFSD?
The .x file in the current source kit is available by FTP from:
bcm.tmc.edu
src.doc.ic.ac.uk
ftpserver.massey.ac.nz
sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/gen/spry-rpc.zip
-------------------------------------------------------------------------------
F-7. What RFC's describe the NFS protocol? Where can I get these RFC's?
RFC's (Requests for Comments) are standards approved by the IETF (Internet
Engineering Task Force) which maintain order on protocols and information
technology affecting on the Internet. There are about 1500 or more Internet
RFC's and many more drafts & proposals.
There are three RFC's currently related to the NFS protocol:
RFC 1094 - NFS: Network File System Protocol Specification
RFC 1057 - RPC: Remote Procedire Call Specification Version 2
[supercedes RFC 1050]
RFC 1014 - XDR: External Data Representation Standard
These RFC's are available by ftp from:
NIC.DDN.MIL
seagull.rtd.com: /pub/tcpip/papers
or by mail server from:
SERVICE@NIC.DDM.MIL
with subject "HELP"
or retrieve with "RFC index"
-------------------------------------------------------------------------------
F-8. How can I tell if a program is NFS mounted?
Here's a message which discusses C code and methods of doing this:
In article <21egppINN5li@hoss.usl.com> mdash@usl.com (-candee-+Scheer M.D.)
writes:
>By happy (?) coincidence, both NFS (at least implementations based closely
>on the Sun reference port) and RFS assume that (1) local file systems have
>major device numbers where the high bit is off, and (2) the client is
>therefore free to play in the namespace of devs with the high bit on.
>Clients of both types synthesize devs with the high bit on. I'm aware of
>no environment that breaks assumption (1).
We're aware of several. We've been down that route and abandoned it
several years ago. While this is true of faithful SVRx (where I'm not
sure whether "x" includes any 4) ports with RFS, it breaks on many other
machines. Including SunOS, which uses a major number that is determined
at driver configuration time to denote NFS mounted files. If I recall
correctly, out-of-the-box, the magic major number is 20 on SunOS, but may
change on reconfig. Other machines where I'm fairly sure that the highbit
kludge doesn't work are Pyramid DCOSX, AIX3. It's been a while...
If I have to, I could confirm and expand the list by pawing thru
our SCCS history databases. Please don't make me - it's scary in there ;-)
Furthermore, st_dev will not change between different NFS mounts.
Thus st_dev:st_ino cannot be unique.
If you're on a SVR3'ish port, there is a macro in sys/types.h (or param.h)
analogous to major() and minor(). I seem to recall it is called "bmajor()".
If you're on a system that has bmajor(), you can use it - I remember it
masking off the upper bit of a major number. So you can say:
if (major(x.st_dev) != bmajor(x.st_dev))
file is remote
If it doesn't, you have to experiment and keep your fingers crossed.
I hate to say this, but there is no easy way to do this universally.
We ended up having to read the mount tables and match path prefixes.
Yuck. #defines up the wazzoo.
I suggest you start reading about getmntent() and analogues, and parse
the file system type fields. If performance isn't particularly critical,
it may be easier to popen /etc/mount and parse the output:
f = popen("/etc/mount", "r");
while(fgets(buf, sizeof(buf), f)) {
...
}
pclose(f);
If you use getmntent() (or /etc/mount kludge), and get a reasonable stat()
st_ino value for each file, you can use a "mount number":st_ino as a unique
key. But you cannot guarantee that a single file has only one
key (multiple NFS mounts of a directory heirarchy).
You may also have to resolve symlinks depending on how your application
works. This isn't a lot of fun either.
If you merely have to determine whether the occasional file is
remote or not, just "df <file>" it, and parse the output.
Grotty, effective, reasonably portable, and *usually* reliable.
But we know systems that can't even get this right...
[On HPUX, use "bdf" not "df" ;-)]
--
Chris Lewis; clewis@ferret.ocunix.on.ca; Phone: Canada 613 832-0541
Psroff 3.0 info: psroff-request@ferret.ocunix.on.ca
Ferret list: ferret-request@ferret.ocunix.on.ca
-------------------------------------------------------------------------------
Section G: Product Features Comparisons
=======================================
-------------------------------------------------------------------------------
G-1. Driver support comparison chart of different products.
Additional codes:
s = supported with a "shim" (perhaps some "y" should be "s", tell me)
m = "must be used with" as opposed to "also works with"
Drivers Included Interfaces Supported
------------------- -----------------------------
Stack Token Packet
ID Provided Ethernet Ring FDDI Drivers NDIS SLIP PPP ODI
--------- -------- -------- ----- ---- ------- ---- ---- --- ---
AIR y y y y
PC/TCP y y y y s y y s
Chameleon y y y y s y y n
Super-TCP y y y n y y y x y
IBM/DOS y y y s y y n n
BW y y y y y y n y
Distinct y y y n y y y y y
Pathway y y y y y y y
PathWay.OS2 y y y n y y
PC-NFS y y y s y y n y
LWPD y y y s s y y y
HP y y y y y n n s
NCSATel n n n m
CUTCP n n n m
QVT/Net n n n m
MSLanMan y y y
TTCP y y y s n n s
TCPOpen y y y y y y n y
WinNT y y y n y n n
Piper/IP y y y y y y
ICE-TCP y y y
Notes:
Many packages include drivers for many different network adapters,
and/or can use interfaces to existing drivers. Packet driver
compatibility implies NDIS and ODI compatibility through the use of
dis_pkt and odipkt.
-------------------------------------------------------------------------------
G-2. Protocol support comparison chart of different products.
It is presumed that a TCP/IP package supports TCP, IP, UDP, ICMP, and
ARP, so these are not listed.
ID BootP Client RARP DNS NetBIOS (2)
--------- ------------ ---- ------- -------
AIR n n y y
PC/TCP y y y
Chameleon y y n
Super-TCP y y y y
IBM/DOS y y y
BW y y y y
Distinct
Pathway y y y
PathWay.OS/2 y y y
PC-NFS y(3) y n y
LWPD y y y y
HP n y y
NCSATel n y
CUTCP y n y
QVT/Net y