HDTenEightyP/NetNews huggingface dataset:
From: David_Murphy@Novell.COM (David Murphy)
Subject: Re: 100MBPS ENET
Organization: Novell, Inc.
Date: Tue, 26 Jan 1993 23:57:22 GMT

In article <JAS.93Jan26145441@mcgarret.proteon> jas@mcgarret.proteon (John A. Shriver) writes:
>
>This silly requirement for no frame format change comes from the fact
>that the PC software industry has (semi-)standardized on NDIS and ODI,
>which mean that every protocol stack has to understand every MAC frame
>format.  If the world had standardized on the Packet Driver, which
>interfaces transparently at the bottom on the Network layer, then
>adding a new class of driver with a larger frame size would have been
>trivial, and transparent to applications.
>
>The same problems happens in the STREAMS DLPI interface.  Token-Rings
>and FDDI often have to masquerade as Ethernet, since the clients only
>support Ethernet.

I have to point the above is in error, NDIS is MAC Header aware, ODI is not
nor has it ever been and is designed to isolate Protocol Stacks from
LAN Drivers and visa versa.  Protocol Stacks just utilize the WorstDataSize
field of the MLID Config. Table to see how much they can Tx/Rx, etc.

I suggest you download the PKZIP'ed postscript files from odi/specs/
on sjf-lwp.sjf.novell.com and see how ODI works.

By the way, a properly written ODI Protocol Stack can work on top of any
underlying Media, ie. Ethernet, Token-Ring, FDDI, ARCNet, etc. transparently
and does so currently. 

David_Murphy@novell.com         All opinions are my own, not the employer's
                                And I am not a support person either, so 
                                support questions should go to support people.
Newsgroups: comp.dcom.lans.ethernet
From: senteck@iss.nus.sg (Tan Sen Teck)
Subject: Problem with BYU/IPX over NDIS
Organization: Institute of Systems Science, NUS, Singapore
X-Newsreader: Tin 1.1 PL4
Date: Thu, 21 Jan 1993 04:34:08 GMT

Hope I've got the right newsgroup, folks.

I'm currently trying to setup a netware 3.11 network using FTP Software's
PC/TCP v2.11 with generic packet driver ethdrv and BYU's IPX implementation
over SMC's NDIS device driver. The setup consists of the following software
and their respective version numbers:

        Protman.sys v1.1 - Protocol Manager from Microsoft
        SMCMAC.DOS v1.19 - SMC's NDIS ethernet adapter driver
        dis_pkt.gup v1.30 - FTP Software's mac/dis Packet Driver Convertor
        netbind.exe v1.1  - Microsoft's netbind program
        byuipx.com        - IPX/SPX v3.10 with BYU Packet Driver v2.01
        netx.com v3.26    - Netware shell
        ethdrv.exe v2.11  - FTP Software's generic TCP kernal

The whole setup on the client workstation works fine. I can communicate
with my netware server and UNIX hosts concurrently from within Windows 3.1.
Trouble starts when the network utilization goes up to about 30-35 percent.
I start to get Network Error on Server; Error sending on network. Abort,
Retry? messages while operating from DOS (Windows not loaded) and complete
hanging of the station when operating from Windows 3.1. It got so bad at
certain times that the station is not even able to bootup onto the
netware network. I've got another station experiencing the same problem,
but after changing the setup to just plain ipx.com without the BYU/NDIS
stuff, the station works albeit slightly slower, when traffic is at 30
percent. At one time I had both stations running side-by-side. The one
with the straight ipx.com was chugging away merrily, whilst the BYU/IPX
station was hanging all the time. Both stations run fine when network
utilization is at about 10-20 percent. I'm running coax thin ethernet
RG58A/U Type cable segments with Synoptics Repeaters and Cisco Routers.
All the stations and server are on the same segment. The heavy traffic
is usually generated by our Sun Workstations in that segment.

Has anyone out there come across this problem. Is there a FAQ site
I can look up for answers? I need help quick! The new network is
scheduled to be up in the next couple of weeks.


Mr. Tan Sen Teck.
Analyst/Programmer
Institute of Systems Science
National University of Singapore.
Internet: senteck@iss.nus.sg

Newsgroups: comp.dcom.lans.ethernet
From: gary@sci34hub.sci.com (Gary Heston)
Subject: Re: Help -- Want do do a PC bridge.
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Systems, Inc., Huntsville, Al.
Date: Mon, 25 Jan 1993 19:44:33 GMT

In article <C1B02r.57t@cmie.ernet.in> shobhana@cmie.ernet.in (Shobhana) writes:
>	I want to do a PC bridge which connects 2 ethernets based on TCP/IP. 
>	Any software available?

Yes, KarlBridge is available from osu.edu, and PCBridge is available from
several places, including uunet.


-- 
Gary Heston    SCI Systems, Inc.  gary@sci34hub.sci.com   site admin
The Chairman of the Board and the CFO speak for SCI. I'm neither.
Windows NT documentation: "Command to change password    CTL-ALT-DEL"
Newsgroups: comp.dcom.lans.ethernet
From: shobhana@cmie.ernet.in (Shobhana)
Subject: Help -- Want do do a PC bridge.
Organization: Centre for Monitoring Indian Economy, Bombay
Date: Sat, 23 Jan 1993 11:04:02 GMT

	I want to do a PC bridge which connects 2 ethernets based on TCP/IP. 
	Any software available?
	Please Help.

	Thanks in advance.
______________________________________________________________________________

shobhana@cmie.ernet.in
shobhana@shakti.ncst.ernet.in
______________________________________________________________________________

Newsgroups: comp.dcom.lans.ethernet
From: jacksond@ogre.cica.indiana.edu (Richard Jackson (Bmg))
Subject: Re: LAN Analyzer recommendations.
Organization: Indiana University
Date: Mon, 25 Jan 1993 17:40:49 GMT

In <1993Jan21.190226.26403@novell.com> rpratt@novell.com (Robert Pratt) writes:

>In article <1993Jan18.194350.5399@pencom.com> mike@pencom.com (Mike Heath) writes:
>>
>>I'm in the market for a LAN Analyzer.  Basically, I want to find where
>>our network bottlenecks are.  We currently have 16 thinnet legs connected
>>through 2 Racal InterLan Multiport Repeaters.  Approximately 100 workstations
>>are connected.
>>We don't currently have a need for a protocol debugger or anything like that,
>>just a traffic analyzer.  The ability to detect shorts/open cables is a
>>plus, but not entirely necessary.

>Although you may not have an immediate need for protocol decoding, almost every
>product includes it, and once you have it I think you'll discover how useful
>it is.  My suggestion, if you want a relatively low cost solution, is to
>look at the software only products that run on arbitrary NICs using either
>ODI or packet drivers to interface to the hardware.  I work on Novell's
>product, the LANalyzer for Windows, which is $1495.  Intel has the NetSight 
>Analyst, which is in the same ballpark pricewise, and there are also
>a variety of other vendors, such as Avante and Triticom.  
>   If you really want to focus on cable shorts, etc., a cable tester from
>someone like MicroTest is going to do a much better job than any
>network analyzer will, so you might want to look at both.

>Bob


>Bob Pratt                               | voice     : (408) 473-8274
>Network Management Products Division    | Fax       : (408) 435-1706
>Novell, Inc.                            | more voice: (800) 243-8526
>2180 Fortune Drive, San Jose, Ca. 95131 | Internet  : rpratt@Novell.com
>"It isn't that I can't help these people, it's that I don't want to."
>Disclaimer:  I do not speak for Novell in any way, shape, or form.


The Novell product at that price is strictly for Novell packets and not others.
NetSight and the Triticom suite of products have both received good reviews
in majors pubs of late (InfoWorld, Data Communications, PC Mag, etc).  They
(the Intel and Triticom products) do a variety of protocols as well as Novell's.

--
   Richard M. Jackson            Internet: jacksond@ogre.cica.indiana.edu
   US Snail - PO Box 1216, Bloomington, IN 47402-1216 (812) 339-1444 x244
   Keep life simple..........................judge not and get on with it 
   All standard disclaimers apply, my employer wouldn't have it otherwise
From: dpike@oavax.csuchico.edu (Dan Pike)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: 10T and number of twists per foot.
Date: 24 Jan 93 22:45:54 GMT
Organization: California State University, Chico
NNTP-Posting-Host: dan-mac.csuchico.edu
X-UserAgent: Nuntius v1.1.1d9
X-XXMessage-ID: <A7885DF4CA011014@dan-mac.csuchico.edu>
X-XXDate: Sun, 24 Jan 93 21:53:40 GMT

In article <slendt.105.727652267@unomaha.edu> Steven Lendt,
slendt@unomaha.edu writes:
>How many twists per foot in solid core unshelded twisted pair wire are
>needed to make it live up to level 3 10baseT spec?
>Also, how many punch blocks (old 66 type) is it safe to go through if
the 
>total wire length is not greater than 75 meters?

I'm pretty sure the recommended number of twists per foot is 7tpf.  As
far as the punch block question goes, when I was working at Apple we
figured out that each punch on a 66 block added the equivalent of about
20 feet of cabling.  This wasn't any scientific testing though.  I think
we measured it with a TDR.

-Dan
Newsgroups: comp.dcom.lans.ethernet
From: seifert@netcom.com (Rich Seifert)
Subject: Re: Who says DELNIs and DEMPRs alter the specs.
Organization: Networks & Communications Consulting
Date: Sun, 24 Jan 1993 00:44:23 GMT

In article <C169LH.Mr4@unixhub.SLAC.Stanford.EDU>, streater@unixhub.SLAC.Stanford.EDU (Tim Streater) writes:
> 
> The issue for us is that this leaves a host of questions unanswered, such as:
> 
> 1) Why is this?

Because the DELNI has inherent delays that were unaccounted for in either
the Ethernet or 802.3 system delay budget. In addition (I forgot to
mention this earlier) the DELNI introduces some bias distortion. Since
it is not a repeater, it does not retime the signals, and this timing
distortion gets added to the signal. Again, this was unaccounted for
in the original specifications. The distortion is on the order of 1-2
nanoseconds, which is significant (there is a total timing budget of 25
nanoseconds).

> 2) Suppose I have 2 of these things thusly connected. DO I knock another 200m
>    off my maximum cable length, do I reduce the allowed length by a factor of
>    300/500 again, or what?

If you are going through two pairs of DELNI/DEMPRs, yes I would reduce
my backbone cable allowance further. I have not gone through the numbers
lately; I think 200 meters is a real worst-case/guaranteed-to-work
figure. It may be less, but you would have to be a rocket-scientist
to figure it out. (or hire a knowledgeable network consultant ;^) )

> 3) We in fact are using Cabletron equivalnets of DELNI/DEMPR units. Do the
    same restrictions apply to these boxes as to the DEC units? If not, why not?

I have no idea of the internals of the Cabletron devices, but I think the
laws of physics are the same in Rochester NH as they are in Maynard MA.
The actual numbers may be different, but their "fan-out" box surely 
introduces some unaccounted-for delay and timing distortion.

> 4) If I use a DELNI without a DEMPR connected, does this restriction apply?
>    (Looks like it doesn't).
>

Actually, it does. A DELNI eats some of the system budget, all by itself.
Also remember that you can't cascade DELNI's AND then connect them to
a backbone (this is because of the timing distortion).
 


-- 
Rich Seifert                    Networks and Communications Consulting
seifert@netcom.com              (408) 996-0922
                                (408) 996-2860 FAX
"... specialists in Local Area Networks and Data Communications systems"
Newsgroups: comp.dcom.lans.ethernet
From: merce@xenitec.on.ca (Jim Mercer)
Subject: Re: Looking for Thinwire (coax) cards.
Organization: Reptilian Research, Toronto, Ontario, CANADA
Date: Sun, 24 Jan 1993 22:40:18 GMT

In article msmith@beta.tricity.wsu.edu (Dragon Lord) writes:
>I'm looking for an ethernet card (PC) that supports LANtastic.
>I DON'T have the money to use a dedicated server so I'm pretty sure I want a
>peer-to-peer setup.  
>... have drivers for LANtastic AND drivers for something like the FTP inc.
>products.  

while this may not address your Lantastic requirements, the Release 11
Crywryn Packet Drivers will have a packet driver for the parallel port that
uses a "standard" parallel-parallel cable (wiring spec included).

this will allow you to use the FTP stuff, as well as any other package that
can use packet drivers, and you don't need to buy any cards. (unless you don't
have any parallel ports.

once i find the time, i'm gonna try and write a companion for 386BSD.


-- 
[ Jim Mercer   Reptilian Research  merce@iguana.reptiles.org  +1 416-506-0654 ]
[                      longer life through colder blood                       ]
From: muench-philip@math.yale.edu (Philip Muench)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: 10baseT electrical characteristics
Date: 24 Jan 1993 21:01:51 -0500
Organization: Yale University Mathematics Dept., New Haven, CT 06520-2155
NNTP-Posting-Host: cantor.math.yale.edu

In article <C14ItD.5Au@comp.vuw.ac.nz> don@rata.vuw.ac.nz (Don Stokes) writes:
>I'm doing a bit of research into optical ethernet links and 10baseT
>extenders.
>
>Does anyone have a feel for the electrical characteristics of the animal?
>Specifically:
>
>	Analogue bandwidth required
>	Voltages present on on cable during mark, space & idle states
>	Any modulation carried out on the baseband signal
>	Link integrity implementation
>	Anything else relevant to the issue
>
>If anyone local has copies of the relevant specs I'd love to hear from them...
>
>TIA
>
>--
>Don Stokes, ZL2TNM (DS555)                      don@zl2tnm.gen.nz (home)
>Network Manager, Computing Services Centre          don@vuw.ac.nz (work)
>Victoria University of Wellington, New Zealand.           +64-4-495-5052

   I think any periodical or book published by the Institute of
Electrical and Electronic Engineers (IEEE) may tell you how
to reach the IEEE sales and information service.
Perhaps "Books in Print" or whatever book retailers and libraries
in New Zealand use to find titles, authors, subjects, and publishers
has a listing for the IEEE. Ask a librarian.
(Sorry, none of these near me as I write this.)
   You need both the main volume on IEEE standard 802.3 and
the supplement volume. The supplement has the 10BASE-T-specific stuff
and refers to the main document.
   Perhaps the International Standards Organization (ISO) has an
efficient sales office, too. I do not know the ISO standard number
corresponding to IEEE 802.3, but IEEE can certainly tell you,
and ISO probably can, too.
-Philip Muench
 muench@cantor.math.yale.edu 128.36.23.26
Newsgroups: comp.dcom.lans.ethernet
From: pat@hprnd.rose.hp.com (Pat Thaler)
Subject: Re: Isochronous Ethernet 
Date: Thu, 28 Jan 1993 17:42:39 GMT
Organization: Roseville Networks Division
X-Newsreader: TIN [version 1.1.3 PL7]

: I have been asked about what Isochronous Ethernet is recently.  I've heard
: the term, but I don't know any details.  The only mention of isochronous
: services I can find is in the 802.6 spec.
: 
: Is there an isochronous service defined for 802.3?  What is its relationship
: to the service in 802.6?  Are there isochronous services now defined in 802.2?
: Any references?
: 
: -- Craig

Isochronous Ethernet is a proposal that was made by National and IBM for
a twisted pair network that contains a 6 Mb/s isochronous channel tdm'ed
(time domain multiplexed) with a 10 Mb/s Ethernet channel.  The proposal
uses hubs supporting a star topology.

Ethernet does not currently offer isochronous service.  Neither does 802.2.
I think that in the proposal the isochronous service has a separate service
interface.  It just shares the wire with the Ethernet.

Pat Thaler
From: muench-philip@math.yale.edu (Philip Muench)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Thinnet problems: "Ethernet jammed"
Date: 23 Jan 1993 20:33:19 -0500
Organization: Yale University Mathematics Dept., New Haven, CT 06520-2155
NNTP-Posting-Host: cantor.math.yale.edu
Keywords: intermittent

In article <1993Jan14.174906.3582@organpipe.uug.arizona.edu> cliff@cs.arizona.edu (Cliff Hathaway) writes:
>
>The machines farther away from the repeater get real slow from time to time,
>sometimes freezing up entirely, other times reporting "<servername> not 
>responding", or "Ethernet jammed".  Usually, the machines closest to the
>repeater continue to work fine when these errors appear.  There are 5 other
>Sun 3 Xterminals on the leg with the server, and they never complain, so I
>don't think it's the server or the leg it's on that is causing the problem.
>
   Perhaps your cables are attenuating signals excessively, are not
terminated with the proper impedance, or have faulty connectors or damage
that introduce excessive reflections. Perhaps a time-domain reflectometer
(TDR) of the cable-scanner type or oscilloscope type will let you compare
cables. I do not know whether letting the outer conductor of the coaxial
cable touch ground would be enough to cause your problems, but maybe
someone reading this can say. Perhaps one of the machines on the cable
(or the machine's external MAU) is causing problems for the rest.
This could be checked by removing one machine at a time and watching
the others.
   The problem could, though, be on the other leg; perhaps there is just
enough distortion or amplitude deficiency to let a bit get flipped or
dropped on the way through the repeater. Perhaps your sniffer could
find more CRC errors in one computer's packets after passage through
the repeater, compared with CRC errors before passage through the
repeater. I imagine this being done under conditions of very low traffic
(utilization < 1%), when CRC errors caused by late collisions would
not obscure those caused by dropped bits.
-Philip Muench
 muench@cantor.math.yale.edu 128.36.23.26
Newsgroups: comp.dcom.lans.ethernet
From: Mehrtens_T@msm.cdx.mot.com
Subject: Re: Who says DELNIs and DEMPRs alter the specs.
Organization: Motorola_Codex
Date: Fri, 22 Jan 1993 18:19:16 GMT

In article writes:
>  shortened for sanity's sake

  Folks, Ethernet rules allow a certain delay between the transmission and
receipt of a packet, end-to-end.  I have giudelines where I calculate the
inherent delays in each component on the network, (TXcvrs, AUI, repeaters,
DELNIs, DEMPRs, coaxial lengths, etc.).  Designing a network takes more
knowledge than what is superficially available in the brocheurs. When designing
a network, one must consider the end-to-end delay of the transmission of a
packet.  The DELNI and DEMPR, and all other repeaters, induce a small delay. 
DEC informed me (1991) that they no longer recommend connecting DEMPRs to
DELNIs.
  If you have a straight piece of thick Enet, and thick TXCvrs, then 500M is
o.k.  The delay end to end has been computed (57.6 us) which guarantees that
collisions happen Before the end of transmission of the smallest packet (64
bytes).  Adding the other DEMPRs along the length of the thick ethernet cable,
inducer a end-to-end delay, which must be subtracted from somewhere.  In this
case, active devices on the thick ethernet cable must be within the 300M, and
the extra delay is "given" to the DEMPRs and their segments.  That way, you
maintain the correct end to end delay of 57.6us.  I can guarantee that
exceeding these parameters WILL cause more harm than good.
  I design my network with further restrictions - One hub (Cabletron,
Synoptics, etc.) connecting to a router.  One repeater from node to node.  I
have 50 to 78% loading, 2% collision rates, non-existent runt packets,
Engineers getting their money's worth out of their workstations.  If a network
will be lightly loaded (under 35%) then the 5-4-3 rules will apply, and the net
will operate quite nicely.

  Not all rules were made to be broken.  Ethernet, and DEC's, rules may seem
restrictive, but they are there for a reason.  If you're ever unsure about
something, continue to ask questions.  There are many reports, books, and
manuals out there which will help.  I also like worhing with the hub vendors.

  Like someone else's sig states - It's o.k. to make mistakes - just make NEW
ONES!!!

More free information available upon request.  Money back guarantee.
Tom M.
<Send for amusing, long disclaimer>
From: mwh45279@uxa.cso.uiuc.edu (Marc Henkel)
Newsgroups: comp.dcom.lans.ethernet
Subject: LAN Manager mailing list?
Date: 26 Jan 93 21:17:17 GMT
Organization: University of Illinois at Urbana

A few days ago I saw some posts about a LAN Manager mailing list.
Does it exist?  If so, does anybody know who I can contact to get on
it?  Thanks.


Marc


----
Marc Henkel   "There's a fine line between stupid and clever"--\/
University of Illinois at Champaign-Urbana             Nigel--from the band
Internet: mwh45279@uxa.cso.uiuc.edu                           Spinal Tap
Newsgroups: comp.dcom.lans.ethernet,comp.protocols.snmp
From: karl@empirical.com (Karl Auerbach)
Subject: Re: Looking for 10Base2 Hubs with SNMP management
Keywords: 10Base2 SNMP
Organization: Empirical Tools and Technologies
Distribution: inet
Date: Sat, 23 Jan 1993 06:55:16 GMT


>I'm trying to find any user experiences with various 10Base2 Hubs which
>also support SNMP management

Nearly all of the larger 10-base-T hubs (i.e. the ones with removeable 
cards) now support SNMP.  (I implemented a number of them myself, 
including the first shipped SNMP-capable hub in 1989.)

Some of the trade rags have done some so-called "evaluations".  These could 
be useful for a list of vendors, but I wouldn't trust the evaluations 
themselves.  (I saw a number of errors in one weekly's evaluation test's and 
in the author's interpretations of what SNMP is.)

The quality of the SNMP implementations in hubs varies widely.  I've had 
experience with some hubs that had to be reset frequently once SNMP was 
enabled.  And other hubs run SNMP rock solid for months at a time.  And at 
least one major vendor does not do get-next correctly in its agent. 
(However, it is to their credit that they know of the problem and have 
promised to fix it.)

				--karl--
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.dcom.lans.ethernet
Subject: WD8003 detailed register info wanted. 
Distribution: world
Date: Thu, 21 Jan 93 03:13:48 GMT
Organization: Crynwr Software

In article <C159Mq.83r@oceonics.nl> fb@oceonics.nl writes:

   Can somebody point me to some detailed information about the WD8003EB
   ethernet card.

SMC (owners of the WD Ethernet adapter line now) is very helpful with
programming documentation.  I suggest calling your manufacturer's
representative and asking them.

-russ <nelson@crynwr.com> What canst *thou* say?
Crynwr Software           Crynwr Software sells packet driver support.
11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.
From: bloeber@ecst.csuchico.edu (Robert Paul Loeber)
Newsgroups: comp.dcom.lans.ethernet
Subject: Boot PROMs for 3C501...
Date: 24 Jan 93 22:53:10 GMT
Organization: California State University, Chico
NNTP-Posting-Host: cscihp.ecst.csuchico.edu

As the Subject says.... I'm looking for a boot-PROM for the 3-Com 3C501
Ethernet Card.  

bloeber@cscihp.ecst.csuchico.edu
Newsgroups: comp.dcom.lans.ethernet