HDTenEightyP/NetNews huggingface dataset:
From: Vince Fuller <vaf@Valinor.Stanford.EDU>
Subject: Re: Subnetting and class B nets
Usmail: Pine Hall 115, Stanford, CA, 94305-4122
Date: 27 Aug 92 10:08:15 PDT
Office: Spruce Hall F15, (415) 723-6860

        So we choose a subnet  mask of 255.255.255.0 for the  individual
    units  and  for  the  lines  we  would  like  to  use something like
    255.255.255.248.  This  way we  get greater  efficient use  from the
    address space, rather than wasting an entire 256 address range space
    for each leased line.  If we have 120 lines, we could end up wasting
    132.64.1.x-132.64.120.x leaving just about 50% of the address  space
    for real work.  Packing the addresses for the leased lines into  one
    segment of the class B network - such as 132.64.1.x makes sense  and
    should work.  But  for some reason  (perhaps some subnetting  rule),
    the cisco will  to not accept  two *different* subnet  masks for the
    same class B  network.  The cisco  automatically changes the  subnet
    mask for all interfaces with the same class B network address to the
    last subnet mask of the last interface set.
    
    I am sure there must be some config command to bypass this problem.
    Or is everyone wasting oodles of address space on their leased line
    subnets?

While OSPF explicitly allows this (as will RIP-II), cisco's implementation
does not support it until release 9.1. As a field-test site for 9.1, I have
just begun to start exercising this feature - on network 131.119.0.0, we now
have routes with four different subnet masks:

	- 255.255.0.0 for the "default subnet" route
	- 255.255.255.0 for variable-length-subnet "challenged" (a California
	  euphamism for handicapped) systems, i.e. pre-9.1 ciscos as well as
	  for Ethernet subnets
	- 255.255.255.252 for serial links
	- 255.255.255.255 for point-to-point connections (originated by the
	  Proteon OSPF implementation)

We are waiting with baited breath for 9.1 to be released, since variable-length
subnet mask support will *greatly* increase the efficiency of our address space
allocation - for example, instead of using up all space in the address range
131.119.1.xxx through 131.119.134.xxx to support 134 point-to-point links (at
2/254 = <1% efficiency), I'll conceivably be able to squeeze all of these
addresses into the range 131.119.1.0 - 131.119.3.xxx at (2/4 = 50% efficiency;
best you can do, since all-ones and all-zeros are reserved addresses).

	--Vince
From: ivor@occs (Ivor D'Souza)
Newsgroups: comp.dcom.sys.cisco
Subject: Ethernet Interface Reset
Date: 3 Sep 92 13:16:40 GMT
Reply-To: ivor@occs.nlm.nih.gov
Organization: National Library of Medicine, MD
X-Newsreader: Tin 1.1 PL4

I have an AGS+ with 4 ethernet interfaces and high-speed serial interfaces
running 9.0(1).  Two of my newly-activated ethernet interfaces change their
states from "line protocol up" to "line protocol down" without any manual
intervention.  I put a sniffer on the line and notice that the Cisco
keeps sending out loopback packets of Ethertype 9000 to these two ethernet
interfaces.  When I do a "show int eth 3" I notice a high number of 
interface resets.  

Thanks in advance for any suggestions.

 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Ivor L. D'Souza                                      INTERNET:        
    System Administrator                            ivor@occs.nlm.nih.gov 
    National Library of Medicine                    Tel: (301) 402-1742    
Newsgroups: comp.dcom.lans,comp.dcom.lans.ethernet,comp.os.os2.misc,comp.os.os2
From: dlv@cunyvms1.gc.cuny.edu (Dimitri Vulis, CUNY GC Math)
Subject: IBM LAN Server over Ethernet --- please help!
Reply-To: dlv@cunyvms1.gc.cuny.edu
Organization: Computer Center, CUNY Graduate School, New York NY 10036
Date: Wed, 26 Aug 1992 16:13:32 GMT

I'd greatly appreciate help with this:
 
I'm trying to put up Lan Server basic 2.0 on a little Ethernet using SMC
(former Western Digital) cards. The diagnostics program that came with
the card is able to send and receive packets among the machines, so the
cabling is probably OK.
 
The MAC section of the protocol.ini file on the server only has entries
for IRQ, ram window, and I/O port --- the rest is default. 'NET START
SERVER' works with no error messages and I can log in locally. (There's
no local loop and the server doesn't start if, e.g., the Ethernet cable
is disconnected). 'NET ERROR' is empty.
 
There are no OS/2 workstations (for now, will be later).
 
The MAC section of the protocol.ini file on the DOS workstations (level
60000) only has entries for IRQ, ram window, and I/O port --- the rest
is default. I also tried setting receive buffer to 256 and 1024 and
various values for queues et al with no effect. The config.sys has the 3
DXM files; the E0 file has a 40K workspace (probably an overkill) and
the T0 file has the default sessions/stations/names and O=N as the
documentation says; I also tried specifying transmit buffer to 1.4K as
the documentation says and 1 or 2 buffers with no effect.
 
What do I mean by 'no effect'? Netbind and 'net start' run with no error
messages (I tried both RDR and RCV in DOSLAN.INI). However, 'net logon
user pw' waits for a very long time and says 'Unable to contact the
domain controller'. Argh! :)
 
I've been successfully running LAN Server with Token Ring on another set
of PCs, have written fairly complex services and utils, am familiar and
very happy with it, and can try to answer questions about that. I'm
confident that that part (IBMLAN.INI / DOSLAN.INI) is fine. My problem
seems to be with Ethernet, which I've installed for the first time in my
life. There's plenty of Ethernet here at GC under Novell and our kind
systems people know nothing about LAN Server.
 
I have all LAN Server documentation, and access to Microsoft and 3COM
documentation from 'previous lives'. No help there, except a few
Etherner notes that I've already tried.
 
I would *greatly appreciate* if some friendly soul _succeffully_ running
the configuration I'm trying to set up (LAN server, DOS LAN requesters,
Ethernet (preferably SMC/WD)) could kindly e-mail me their
configuration: (protocol.ini, config.sys, lanman.ini, doslan.ini) so I
could see what I might be missing there; or otherwise suggest what could
be going wrong or how I could gather more diagnostic information.
 
Many thanks in advance for any responses!

Dimitri
Dimitri Vulis
CUNY GC Math
DLV@CUNYVMS1.BITNET DLV@CUNYVMS1.GC.CUNY.EDU

Disclaimer: my Usenet postings don't necessarily represent anyone's views,
especially my own and/or CUNY's.
Newsgroups: comp.dcom.lans,comp.dcom.lans.ethernet
From: tkorento@vipunen.hut.fi (Tero Korento)
Subject: Re: Need a program to copy from PC to PC over ethernet.
Reply-To: tkorento@vipunen.hut.fi (Tero Korento)
Organization: Helsinki University of Technology
Date: Sun, 23 Aug 1992 16:46:45 GMT

In article <1992Aug23.020914.1533670@zeus.calpoly.edu> jemenake@zeus.calpoly.edu (Joe Emenaker) writes:

>Then it hit me: All of these PCs have Hewlett Packard ethernet cards in
>them and we have gobs of 3ft cables just waiting to be connected to them. I
>figured, it would be great if I could somehow use the ethernet cards to
>talk to each other like a null-modem cable is used for. Because, as I
>understand it, ethernet RIPS! It's like 10 Mbits/sec or so isn't it?

Yupp. allthough other factors limit the speed to less.

If NCSA-telnet has a packet driver for your cards you might want to try
ftp between the machines. Easy to use (if you are familiar with ftp) a
bit harder to set up, but quite speedy.

Can't on straight hand remember any particular site where you can ftp
NCSA-telnet from but if you can't find it on your own throw me with a
mail.

					...tERO, tkorento@vipunen.hut.fi


-- 


							...tERO
Newsgroups: comp.dcom.lans.ethernet
From: schwartz@ipx08 (Privataccount Roman Schwartz)
Subject: Re: Ethernet Analyzer/testing devices/software
Organization: PPG Hellige, Freiburg, GERMANY
X-Newsreader: Tin 1.1 PL4
Date: Fri, 28 Aug 1992 10:19:01 GMT

aep@world.std.com (Andrew E Page) writes:
: 
:    What is currently available for hardware that would allow you to
: test hardware/protocols for ethernet hardware?  I'm looking for something
: that would let me anaylze activity/transactions that are occuring during
: operations.  The ability to save and analyze the data in relation to various
: protocols would help enourmously too.  
:    Essentially I'm looking for something that 'plugs into' the network
: directly to allow you to see what's going on.   
: 
We buyed a Protocol Analyzer by HP: HP4972A. Its very good. It's expensive.
In the meantime we got a second. (price ~35.000 DeutschMarks)
--

Roman Schwartz                       email: schwartz%ppgfr.uucp@Germany.EU.net  
Newsgroups: comp.dcom.lans.ethernet,comp.dcom.lans.misc,comp.protocols.novell
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Subject: Re: 802.3 Non-Compliance (?)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Thu, 3 Sep 1992 03:47:19 GMT

In article <1992Sep2.214854.28999@samba.oit.unc.edu>, shava@hermes.oit.unc.edu (Shava Nerad Averett) writes:
> ...
> Well, for one thing, they probably wouldn't have the option.  They use boards
> that use chips that have that layer in silicon, and nothing they did would
> probably be able to mess with it from a driver standpoint.....


There are ethernet chips that allow you to change the way collision
backoff works.  I think they're broken by design, but then I'm
prejudiced about a lot of things.

It seems unlikely in the extreme that any PC software which is forced
by hard necessity to be as portable as possible would do anything with
those features of any board that happens to use those chips.

Also note that Silicon Graphics has never used those chips nor a board
with those chips during my tenure at SGI, and to the best of my more
limited knowledge, neither has Sun.



Vernon Schryver,  vjs@sgi.com
From: nason@pa881a.inland.com
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Max Repeaters/multiport repeater wiring questions
Date: 2 Sep 92 14:57:39 GMT
Organization: Inland Steel Company, East Chicago, IN

In article <id.JIUS.UG6@ferranti.com>, kunkee@ferranti.com (randy kunkee) writes:
> 
> Wouldn't you still count this as a repeater when calculating distances
> between systems?  Eg.:
> 
> VMS----DELNI---transceiver===coax===transceiver---DELNI---VMS
> 
> The two VMS systems above should be counted as having two repeaters
> (the DELNIs) between them, yes?
> 
NOOOOOOO!  A DELNI is not a repeater in any stretch.  It is just a box that
allows you to connected eight devices in close proximity without having to use
a cable.  A DELNI forwards SQE to its connected devices in global mode,
provides SQE-Test and forwards SQE to its connected devices in local mode.
A DELNI does not perform any of the tasks normally attributed to a repeater.
A repeater:
	Amplifies the signal,
	Retimes the signal, and ensures that symmetry is within tolerance
	Sends it out on the next segment with a new preamble,
	Provides a Jam if a collision is seen on its one of its segments.

A DELNI can do none of these things.
	  
-- 
My opinions are my own and not those of my company.  
Free advice is worth its cost.  
--- John M. Nason - NA9U ---|--------------------------------------------|
Inland Steel Company        |  -- nason@pa881a.inland.com                |
Process Automation MS 2-464 |  -- Fax:   219-399-7856                    |
3210 Watling Street         |  -- Voice: 219-399-2450                    |
East Chicago IN 46312       |"Ya can't shoot em till they stop sparklin" |
----------------------------|--------------------------------------------|
Newsgroups: comp.dcom.lans.ethernet,comp.dcom.lans.misc,comp.protocols.novell
From: Mehrtens_T@msm.cdx.mot.com
Subject: Re: Max Repeaters/multiport repeater wiring questions
Organization: Motorola_Codex
Date: Tue, 1 Sep 1992 11:53:06 GMT

In article, Dave Hammond ashs:
>how do I ground my thin-wire ethernet?
>

I purchased some thin ethernet terminators with small tabs attached to them.  I
then solder some small solder-wick (braided wire) to the tab.  The cable is
then connected to earth ground (In my case, all of our equipment racks are
earth grounded (I tried moon grounded, but the cable kept spinning off)).  This
helps eliminate inductive noise on the cable at high transmission rates (bursts
over 35 - 50%) or in electronically noisy environments.

I know how you feel - most terminators do not provide any means of grounding,
unless you sneak in solder-wick when a BNC cable is assembled (not an easy
task).

I purchased the terminators from Anixter, Corp (major outlets in every major
city).  

Cheers

Tom

8-{)
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Subject: Re: 802.3 Non-Compliance (?)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Sat, 29 Aug 1992 08:35:12 GMT

jrd@cc.usu.edu writes:
+---------------
| 	So far as I am aware NW board drivers do NOT reprogram the board
| to modify the exponential backoff algorithm. The vendors usually accused
| of this are Sun and or SGI; proof is not in my hands.
+---------------

Nor in anyone's, since it's not true. At least, not for SGI. We use only
standard Ethernet chips with the standard backoff hard-coded in the chips
(AMD LANCE or Seeq 8003). Sun and the other workstation vendors do the same.
(Well, while it is technically *possible* to program the Intel 82586 chips
used in some Sun workstations to do non-Ethernet backoff, Sun doesn't do that.)

+---------------
| Goodness, the conventional Sun/SGI/DEC/whatnot high performance workstations
| already beat PC Ethernet boards into the ground while following the rules.
+---------------

Exactly. This is usually the source of the accusations: "You *must* be
violating the rules, because you use more of the net than I do." Wrong.
Any single station may use 100% of an Ethernet within "the rules" if
no-one else wants to send, and if a bunch of high-performance stations
want to send at once, they will share the bandwidth approximately fairly.

What *is* true is that if your station cannot queue multiple packets for
transmission, cannot transmit immediately after receiving, or cannot receive
multiple packets back-to-back, you will have trouble getting your "fair share"
of bandwidth on a net with one or more high-performance stations on it.

There exist reasonably-priced cards (e.g., the AMD LANCE 16-bit 1st-party
DMA "half-card", or equiv.) for the PC environment that can stand up to any
high-performance workstation. In fact, with one of these cards (and the right
software), a cheap 486 clone system *is* a "high-performance workstation".


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)390-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94043
From: shah@angelo.amd.com (Amit Shah)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Fiber speed
Date: 25 Aug 92 23:28:19 GMT
Organization: Advanced Micro Devices, Santa Clara, CA

In article <1992Aug19.162023.16390@awdprime.austin.ibm.com> jeffry@ashanti.austin.ibm.com writes:
>
>In article <1992Aug18.181507.14439@picker.com>, SYSNET@engvax.picker.com (Leonard A. Visconti) writes:
>> Does anyone know the speed of a signal through fiber? For example, through
>> thick wire ethernet cable the propagation speed is about 77% of the 
>> speed of light. We are using 62.5/125 multimode fiber at 850 nm. 
>
>In my work with FDDI, using 62.5/125 multimode fiber at 1350 nm, I use
>3ns/meter as the propagation delay.  
>-- 
>JEff Russell                jeffry@browncow.austin.ibm.com  OR
>                            AUSVMQ(JEFFRY)

The FDDI standards use 5.085 ns / meter.  That is what most cable companies
specify too.

--
Amit Shah
Sys. Engg. & Prod. Planning Engineer		Ph.:(408)987 2479
High Speed Networking   			Fax:(408)987 2814
901 Thompson Place, M/S 70			email:amit.shah@amd.com
From: erik@yarra.pyramid.com.au (Erik Lecis)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Null Modem on EtherNet
Summary: Ethernet Transceivers
Date: 31 Aug 92 02:26:49 GMT
Organization: Pyramid Technology Corp PL, Melb., Australia

In article <Bttn2o.7zr@comp.vuw.ac.nz>, Andy.Linton@comp.vuw.ac.nz (Andy Linton) writes:
> 
> I've just looked in the New Zealand catalogue for this device and it costs more
> than buying a couple of 10BaseT transceivers, attaching them to the AUI ports
> and making up a 10BaseT crossover cable. Your mileage may vary!

Hey? The Australian Black Box catalogue lists vanilla ethernet transceivers
at $399, whilst 2-Port direct connect transceivers are $490 and 4-Port models
are $731. NZ prices are bound to be higher, but the relative cost should be
still the same.

ANC retail a 2-Port version for about half the price.

> The other limitation is that the Black Box device "Cannot be connected to the
> network backbone" (Black Box Catalogue - NZ Edition 1992) so that when this
> little "network" expands as these things inevitably do the box becomes
> redundant.

Agreed, but they are great for dedicated LANs.

For instance we have a customer with two machines, each with six ethernet cards.
Two cards are connected to the main network, with the remaining four used 
for dedicated file transfer. The direct connect transceivers are ideal
for this application.

The only disadvantage I see, is that it is impossible to resolve network
problems by "tapping" into the Ethernet with an analyzer - you then need
a couple of ordinary transceivers and a short length of cable.

- Erik. 
Newsgroups: comp.dcom.lans.ethernet
From: schwartz@ipx08 (Privataccount Roman Schwartz)
Subject: ethernet-adapter for pc
Organization: PPG Hellige, Freiburg, GERMANY
X-Newsreader: Tin 1.1 PL4
Date: Fri, 28 Aug 1992 10:26:09 GMT


Hi netters,
I'm looking for an ethernet-card (Ethernet lan adapter) with a
M68000 processor for PC.

Please email any product hints, email/smail-addresses. Thanks in advance.
--

Roman Schwartz                       email: schwartz%ppgfr.uucp@Germany.EU.net
From: nason@pa881a.inland.com
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: en596 late collision detected
Date: 26 Aug 92 15:32:06 GMT
Organization: Inland Steel Company, East Chicago, IN

In article <1992Aug24.180247.6619@lmpsbbs.comm.mot.com>, vittallo@ssd.comm.mot.com (John Vittallo) writes:
> We have a number of 147 and 167 VME systems.  All of a sudden the message 
> "en596 late collision detected" keeps showing up on the screen.(about 1 every 
> 30 minutes)  What is this message really trying to say?
-- 
I am not using these systems.  I have seen and read about this type of error. 
I think what its trying to tell you is that a collision has been detected after
a time that media should have been acquired. In other words your colliding
after the 51.2 us slot time.  This could mean that you have too many repeaters,
you segments are too long, you may have a branched thin-wire segment or a
branched TP line.

Look around, what has changed?  Did somebody add something recently?  This
needs to be corrected ASAP.  If there is more than one node giving this
message, IMHO you have a topological problem.  

My opinions are my own and not those of my company.  
Free advice is worth its cost.  
--- John M. Nason - NA9U ---|--------------------------------------------|
Inland Steel Company        |  -- nason@pa621a.inland.com                |
Process Automation MS 2-464 |  -- Fax:   219-399-7856                    |
3210 Watling Street         |  -- Voice: 219-399-2450                    |
East Chicago IN 46312       |"Ya can't shoot em till they stop sparklin" |
----------------------------|--------------------------------------------|
From: kcone@ncrclm.ClemsonSC.NCR.COM (Kevin Cone)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: 802.3 Non-Compliance (?)
Date: 2 Sep 92 19:28:44 GMT
Reply-To: kcone@ncrclm.ClemsonSC.NCR.COM (Kevin Cone)
Organization: NCR E&M CLEMSON Liberty, SC


In article <p2hn!w#.seifert@netcom.com> seifert@netcom.com (Rich Seifert)
writes:
>
>In any case, current releases of NetWare (2.2, 3.11, etc.) fully
>support 802.2.
> 

Curious.  Wasn't aware of 802.2 support.  Does that also mean that instead
of using the Ethernet TYPE field, Novell instead uses it as a true 802.3
LENGTH field?  It would seem that 802.2 conformance would imply the latter,
but I was under the impression that Novell implemented the former.
-- 
Kevin A. Cone                           e-mail:  Kevin.Cone@ClemsonSC.NCR.COM
Consultant Engineer                     s-mail:  7240 Moorefield Hwy.
NCR Workstation Products Div.                    Liberty, SC  29642
phone:  803-843-5085 (VP 624-5085)      fax:     803-843-1793 (VP 624-1793)
From: coexbgw@state.systems.sa.gov.au
Newsgroups: comp.dcom.lans.ethernet
Subject: Sharp PC-3000 and LAN connectivity
Date: 2 Sep 92 14:00:41 GMT
Organization: State Systems, South Australia

I am hoping that someone can help me with a problem which I am having: namely
connecting a Sharp PC-3000 (palmtop) computer to our LAN.  The connection to
the LAN is through a pocket (parallel) adaptor, which the system just doesn't
seem to recognise.  We have an Ethernet system, Novell IPX/SPX v3.01 running
the Netware v3.02 workstation shell.  The adaptor is a Longshine unit.

The whole setup works fine with a Sharp PC-6200 laptop, but returns an "adapter
not found message" with the PC-3000.

Can any LAN expert (which I am not!) offer any possible solutions?

Many thanks in advance.

Brenton Wright
Adelaide, South Australia
From: bennett@dstos3.dsto.gov.au
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Null Modem on EtherNet
Date: 3 Sep 92 15:04:25 GMT
Organization: Defence Science and Technology Organisation

In article <TR27PB1w164w@Control.Com>, ics.jjmc@Control.Com (J. J. McCarthy) writes:
> fk03+@andrew.cmu.edu (Frank Eugene Kietzke) writes:
>>you can't just connect two
> ethernet cards together with a "null modem" and get it to work. 
> 
> Maybe you can, if you don't understand the problem. For the IEEE
> Conference here this Spring, we hooked an AT and an XT together
> with 10 feet of coax. Both ends had terminators and Ethernet Cards

I think in this case he is referring to ethernet cards which don't have 
transceivers.

There is a "null transceiver" (my terminology) which connects 2 AUI ports, 
called an NC-10, made by Netcor - others may be available also.

Regards,

John Bennett                                E-mail: bennett@dstos3.dsto.gov.au
Head, Networks Group                        Phone : +61 8 259 5292
Corporate Information Systems               FAX   : +61 8 259 5537
DEFENCE SCIENCE AND TECHNOLOGY ORGANISATION Postal: Bld 73 Labs Area
AUSTRALIA                                           PO Box 1500 Salisbury 
            "Lord Warden of the Sync Ports"         South Australia  5108
                (DSTO Network Manager)              AUSTRALIA
Newsgroups: comp.dcom.lans.ethernet
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Subject: Re: what is SQE  (DUMB QUESTION!)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Fri, 4 Sep 1992 13:31:09 GMT

nason@pa881a.inland.com writes:
+---------------
| ccewch@nuscc.nus.sg (Wong Chee Heng) writes:
| > Why SQE must be turned off when connecting to Ethernet V2 device?
|
| Ethernet V2 devices(no 802.3 conformance) cannot accept the 802.3 SQE-test.
+---------------

WRONG-O! The Ethernet v.2 spec contains the "Collision Presence Test"
(see Section 7.4.7), which is exactly the same as 802.3 SQE-test.

It's Ethernet v.1 that can't hack the SQE test...


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)390-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94043

Xref: sparky comp.dcom.lans.ethernet:1728 comp.sys.dec:4758