HDTenEightyP/NetNews huggingface dataset:
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.dcom.lans.ethernet
Subject: 3C503 packet driver and SDLC
Date: 23 Aug 92 08:14:51 GMT
Organization: Crynwr Software

In article <DGH.11.714418037@pc01.divinity.yale.edu> DGH@pc01.divinity.yale.edu writes:

   Can anyone suggest some appropriate voodoo to make a 3C503 operated under 
   the Clarkson packet driver co-habitate pleasantly with a Synchronous Data 
   Link Controller?
   
   The SDLC is apparently a pretty nasty piece of work. It insists on Interrupt 
   3 and DMA channel 1. The packet driver addresses the issue of interrupt, but 
   not the DMA channel. Actually, it looks as if the 3C503 packet driver isn't 
   supposed to be using DMA at all.

Right, the 3c503 packet driver doesn't use DMA.  You ought to be able
to use IRQ 2 or 5 with the board.

   There is a particular application that utilizes the SDLC. The network and 
   the application will both start out fine. However, if the SDLC application 
   is running and attempts to access network services, e.g. printing, the 
   system freezes up. If one shells out of the SDLC application and attempts to 
   switch to a network drive, the system freezes.

It mostly sounds like the drivers are banging at each other's hardware.

-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
Crynwr Software            Crynwr Software sells packet driver support.
11 Grant St.               315-268-1925 Voice
Potsdam, NY 13676          315-268-9201 FAX
Newsgroups: comp.dcom.lans.ethernet
From: gary@sci34hub.sci.com (Gary Heston)
Subject: Re: What wire for outdoors?
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Systems, Inc., Huntsville, Al.
Date: Thu, 13 Aug 1992 20:53:11 GMT

In article <sandrock.713224260@leo> sandrock@leo.scs.uiuc.edu (Mark Sandrock) writes:
|henry@zoo.toronto.edu (Henry Spencer) writes:

|>For any outdoor run, you should use fiber rather than coax if you possibly
|>can.  If lightning hits nearby, you could suddenly find thousands of volts
|>present on your cable, which could be rather destructive, not to mention
|>potentially dangerous to life and limb.  (Wouldn't last long, but then it
|>doesn't have to...)

|Makes sense, but then how do the cable companies get away with stringing
|coax all over town? (Guess I'll call them and ask, if no one here knows.)

They use equipment designed for the application. 10Base2 cable and cards
aren't designed to handle lightning strikes; they're designed for indoor
use. Cable TV amps include protective circuitry to bypass big spikes to
ground safely. (There are protective devices for thin coax, if you insist.)

Run fiber, through conduit of some kind. 400' of plastic conduit should
cost about $80 or so, and will help protect it.

If you absolutly insist on coax, call Belden and see what they have in
RG58A/U designed for outdoor use. Expect to pay for it.
 
-- 
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.
Hestons' First Law: I qualify virtually everything I say.
Newsgroups: comp.dcom.lans.ethernet
From: gwh@elric.cs.mcgill.ca (Gene W. Homicki)
Subject: Ethernet Frame types.
Keywords: ethernet frame
Organization: SOCS, McGill University, Montreal, Canada
Date: Mon, 17 Aug 1992 17:08:29 GMT


Would anyone have a list of ethernet frame types or know where I may 
find one?  I'm trying to identify the packets that an IBM ethernet card
with RPL (Remote Program Load), in a PS/2, is sending out.  tcpdump 
reports that the following is being transmitted:

12:14:30.24 8:0:5a:a1:e8:77 3:0:2:0:0:0 0056 86: 
			 fcfc 0300 5300 0100 0840 0300 0000 0000
			 1000 0800 0640 0905 ea00 0640 0a00 0100
			 0a40 0608 005a a1e8 7700 0540 07fc 0028
			 0004 0024 c005 0800 f819 0a74 4010 4221
			 027f 3531 3120 2020 2020 0040 4333 3135
			 3039

Any help via post or email would be appreciated. Thanks.

					--Gene
					  gwh@elric.cs.mcgill.ca
					  McGill University
					  School of Computer Science
                                          Montreal Canada
From: anne@maxwell.concordia.ca (Anne Bennett)
Newsgroups: comp.dcom.lans.ethernet
Subject: packet (radio) ethernet
Date: 12 Aug 92 22:09:51 GMT
Reply-To: anne@maxwell.concordia.ca (Anne Bennett)

I have been asked to look into packet ethernet (radio transmission) for
setting up temporary ethernet LANs in hard-to-wire locations, for
demonstrations and special events.

Our network is coax (thick and thin), fiber, serial, and twisted pair,
all connected together with a dozen Cisco routers.  We'd probably want to
hang one "radio transceiver" (I'm guessing at the terminology) off thin
coax near a router, communicating with another "radio tranceiver" on
the isolated LAN, also thin coax.

Does anyone have experience with a product that would perform this
function?  Did you have problems? Names of products and companies would
be appreciated.  If someone has an idea of cost, that would be helpful
too.


The news spool at our site does not currently contain a FAQ for this
group;  if my question is answered in a FAQ, someone please e-mail it to
me.  If not, then please e-mail your suggestions to me; I will be happy
to summarize them to this group.

Thanks!

-- 
Ms. Anne Bennett          anne@maxwell.concordia.ca           (514) 848-7606
Computing Services C-1012, Concordia University, Montreal QC, Canada H3G 1M8
(Administrator for Concordia University mail relay, news transfer, and DNS) 
Newsgroups: comp.dcom.lans.ethernet
From: opus@pioneer.unm.edu (Colby Kraybill)
Subject: Re: Remote access of PC via TCP/IP
Date: Mon, 17 Aug 92 19:04:19 GMT
Organization: Space and Planetary Image Facility

In article <1992Aug17.154357.1@kean.ucs.mun.ca> georger@kean.ucs.mun.ca writes:
>a problem but accessing DOS applications to run the retrieval software for the
>CD-ROMs is a major problem.  Because the applications were designed for the
>DOS environment one gets into terminal emulation problems when accessing via
>non-PC oriented systems.  The applications typically also are quite heavy
>in DOS system requirements so that it is not easy to run the applications
>using DOS emulators on other systems.
>

We have not had a problem thus far with our system of CD-ROM file serving.
Since all of the data on CD-ROM that we deal with is imagery there are 
programs across almost all platforms that can access and manipulate our
data.

If one absolutely had to run a DOS program that utilizies a CD-ROM that needs
to be mounted on a UNIX fileserver, I'd recommend looking into OS/2 2.0.
With an extra networking package comes support for complete TCP/IP 
communications and functionality.  To my knowledge OS/2 2.0 will seemlessly
run DOS applications and of course it's own TCP/IP support software.



-- 
Colby Kraybill
Space and Planetary Image Facility
University of New Mexico
opus@pioneer.unm.edu
From: pb@idca.tds.philips.nl (Peter Brouwer)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Remote access of PC via TCP/IP
Date: 17 Aug 92 10:42:05 GMT
Reply-To: pb@idca.tds.philips.nl (Peter Brouwer)
Organization: Digital Equipment Enterprise B.V.,Apeldoorn,The Netherlands.

X-Disclaimer: This opinion is mine alone

In <1992Aug14.094141.1@kean.ucs.mun.ca> georger@kean.ucs.mun.ca writes:

>In article <Bss3DE.86C@watserv1.uwaterloo.ca>, eengelke@steam.uwaterloo.ca (Erick Engelke) writes:
>> 
>> There is a freeware program called TELNETD which can provide simple
>> TELNET access to PCs.  It is ftpable from sunee.uwaterloo.ca 
>> [129.97.50.50] in pub/wattcp/telnetd.zip.
>> 

>  I am very interested in the TELNETD type application for DOS because it is
>a possible solution for proving access to DOS applications (CD-ROM databases as
>an example) across a TCP/IP network.

If you want file sharing over a network you might consider NFS or the use of a
SMB server.
We have both products in out DECadvantage platform ( 80X86 Unix server and
MSDOS PC as clients ).
The DOS PC has connections to a server based on either TCP/IP or OSI.
On top of this you can use the SMB server.


--
#  Peter Brouwer,                | Digital Equipment Enterprise ,              #
#  NET  : pb@idca.tds.philips.nl | Integration Industry Standard Systems,      #
#  PHONE:ext [+31] [-0]55 432992,| Dept Systems Enginering, Bld V1/B4          #
#  FAX  :ext [+31] [-0]55 432070 | P.O.Box 245,7300AE Apeldoorn,The Netherlands#
Newsgroups: comp.dcom.lans.ethernet
From: chrisc@ramrod.lmt.mn.org (Chris Cox)
Subject: Re: Best way to split a net?
Keywords: repeater router gateway switch
Organization: LaserMaster Technologies, Minneapolis, MN  USA
Date: Fri, 14 Aug 1992 12:56:20 GMT

In article <3178@peking.gdwb.oz.au> was@gdwb.oz.au (Warren Stokes) writes:
>From: was@gdwb.oz.au (Warren Stokes)
>Subject: Re: Best way to split a net?
>Keywords: repeater router gateway switch
>Date: 12 Aug 92 02:02:13 GMT
[..Gone..]
>No it is not a bridge technically, but you are right about the forwarding.
>It does filter local traffic and maintains MAC level "routing tables".  No
>management to speak of.  This isn't such a drawback.  
[..Gone..]

What do you mean by "No management to speak of."?

Kalpana do have some SNMP support.  They have a proxy agent which runs on a 
SPARC-station, and they provide their own MIB.

It is basically a standard BSD4.3 agent with some additional code added that 
is specific to Kalpana.  One agent appears to be able to interrogate several 
etherswitches.

Chris


   Chris Cox  W0/G4JEC                               chrisc@ramrod.lmt.mn.org
   LaserMaster Technologies                          Tel: (612) 944-6069
   7156 Shady Oak Road                               Fax: (612) 944-5544
   Eden Prairie, MN  55344

           ----- For mail of a more social nature, please use -----

     chrisc@moron.vware.mn.org  -or- chrisc@biggus.g4jec.tcman.ampr.org

Newsgroups: comp.dcom.lans.ethernet
From: ttoupin@zephyr.cair.du.edu (Tory Toupin)
Subject: Routing Frame Format
Originator: ttoupin@zephyr.cair.du.edu
Organization: University of Denver
Date: Wed, 19 Aug 92 03:31:42 GMT

comp.os.vms
comp.dcom.lan.ethernet


Below is a sample frame captured off of the ethernet and represents a
routed frame to a router (6d06) from an end node (1c06).  Does anyone
out there in ethernet land have a description of a routing frame
format (Level 2 or so I believe) or can you tell me where a 
description can be found?

Ed Toupin
toupine@casi.cba.du.edu

BACKUP : ttoupin@zephyr.cair.du.edu



DEST: aa 0 4 0 6d 6 / SRC: aa 0 4 0 1c 6 / PROTO: 60-3 / SIZE : 46  

[aa  0   4  0 6d 6][aa  0  4  0       . . . 1 .  . . . 
 1c  6] 60  3  0  0  0  0  0  0      2 . ` . . . . . . . 
[aa  0   4  0 d4  4] 0  0 [aa 0       . . . 1 . . .  . 
  4   0 1c  6] 0  0  0  0  4  3      . . 2 . . . . . ` . 
 20 4d  1  49 8b  0  0  0  0  0        .   2 . 2 . . . .
Newsgroups: comp.dcom.lans.ethernet
From: Mehrtens_T@msm.cdx.mot.com
Subject: Re: Extending ethernet over fiber
Organization: Motorola_Codex
Date: Thu, 13 Aug 1992 17:19:50 GMT

In article <1992Aug13.030738.10186@picker.com> SYSNET@engvax.picker.com
(Leonard A. Visconti) writes:
>We have two buildings connected via 11,000 feet of multimode fiber. 
>  Leonard A. Visconti 

I wouldn't suggest installing a network in this manner.  You have a 3500 meter
link, with bidirectional traffic.  Data will pass by each other on the fibers,
but collisions will occur at the transceivers/repeaters.  I did some simple
figguring (not counting the inherent delays of the electronics), and your
end-to-end delay is over 17 microseconds (us) (3500 M * 5 nanoseconds/M). 
Double that, because the collision has to return to you.  An ethernet preamble
is 0.8 us, leaving 34 us.  This means that you could sense a collision after
one router has sent 40 bytes!  Your collision rate will be high.  Quite high.  

This solution may cost more, but, can you do the following? (you could with a
cisco...)
Have two Ethernet ports connecting the two routers, and send out one port, and
receive into the second port?  This will eliminate any collisions.  Half
duplex, you know.

Have you considered using vanilla fiber transceivers ($350 ea.) instead of
repeaters?  The routers should be happy with just the transceivers.  No need in
regenerating the preamble, just to pop into the router.  Unless, of course, all
of the equipment is not in the same room.

Hope I helped in some small manner.  8 years and 500 devices later, I think I
know what 'm doing now!  You can never know for sure!

All disclaimers apply.  Even the funny ones!
Tom Mehrtens <Mehrtens_T@msm.cdx.mot.com> Motorola Codex
 ////\\
  _  _
 (o)(o)
   .)
 )-_-(


Newsgroups: comp.dcom.lans.ethernet
From: pwb@newt.phys.unsw.edu.au (Paul W. Brooks esq.)
Subject: Ethernet CRC/Alignment errors
Keywords: ethernet CRC errors
Organization: University of New South Wales
Date: Fri, 21 Aug 1992 04:17:09 GMT

I have a piece of the campus ethernet that seems to have an excessive
number of CRC/Alignment errors. I have a Novell LANalyzer, and over an
hour or so reports no late collisions, no illegal long/short packets,
but a rate of CRC/Alignemtn errors sometimes up to 1 per 1000 packets.
These errors become more numerous when the traffic exceeds about 7% of
the ethernet bandwidth. To help in tracking down the source, could
someone tell me whether these errors are propagated through repeaters -
if not, that narrows the source to somewhere on this segment, which
would help a lot!. Also, are they the sort of thing to start panicing
about? Is 1 per 1000 or 1 per 5000 excessive at 10% utilyzation?

Paul Brooks        |Internet: pwb@newt.phys.unsw.edu.au
Uni. of N.S.W.     |If you have trouble sleeping, try lying on the end of
Kensington NSW 2033|   your bed. With a little luck you'll drop off. 
AUSTRALIA          |                              - Mark Twain. 
Newsgroups: comp.dcom.lans.ethernet
From: eengelke@steam.uwaterloo.ca (Erick Engelke)
Subject: Re: Remote access of PC via TCP/IP
Organization: University of Waterloo
Date: Wed, 19 Aug 1992 19:39:23 GMT

 pb@idca.tds.philips.nl (Peter Brouwer) writes:
> georger@kean.ucs.mun.ca writes:
>>  I am very interested in the TELNETD type application for DOS because it is
>>a possible solution for proving access to DOS applications (CD-ROM databases as
>>an example) across a TCP/IP network.
>
>If you want file sharing over a network you might consider NFS or the use of a
>SMB server.
>We have both products in out DECadvantage platform ( 80X86 Unix server and
>MSDOS PC as clients ).
>The DOS PC has connections to a server based on either TCP/IP or OSI.
>On top of this you can use the SMB server.
>

There are several reasons why SMBs may not be acceptable for some sites,
SMB access is only useful for PC clients, some people want UNIX or MAC access
to the CD-ROM applications.  SMB's are crap for scanning over WANs, whereas
TELNET scales nicely. TELNET provides good access through terminal servers, SMB
traffic is too heavy for term servers.   SMB solutions require remote users 
to already have  copies of the CD-ROM applications and licensed copies of
your Pathworks software on all the calling PCs whereas the TELNET based solutions
only require users to have copies of TELNET, and even public domain or other
vendors' TELNETs will work.  

Sure there are advantages for both, but SMB is essentially a PC LAN solution
and TELNET is a (multi-vendor, multi-platform, LAN/WAN) Internet solution.  It
simply depends if you plan to restrict the data to PCs.

Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
Newsgroups: comp.dcom.lans.ethernet
From: dhuber@autelca.ascom.ch (Daniel Huber)
Subject: 10BaseT description...where to find?
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Fri, 21 Aug 1992 11:47:58 GMT

Hi there,

Could somebody please forward me to a document describing the 10BaseT
standard? Is there also such a document available by ftp?

Thanks a lot

Daniel

-- 
Daniel J. Huber, AIN1 / Ascom Autelca AG / CH-3073 Guemligen / Switzerland
SMTP: dhuber@autelca.ascom.ch / Voice: +41 31 9996664 / Fax: +41 31 9996751 
X.400: /G=Daniel/S=Huber/OU=Autelca/O=Ascom/P=EUnet/A=Arcom/C=ch/
Newsgroups: comp.dcom.lans.ethernet
From: bbaskett@post.RoyalRoads.ca (Bill Baskett)
Subject: Max Repeaters/multiport repeater wiring questions 
Organization: Royal Roads Military College, Victoria, B.C.
Date: Fri, 21 Aug 1992 17:28:13 GMT


These are probably FAQs but I couldn't find a FAQ list.
There are basic questions, I'm sure, but if I don't ask, I'll
never know!

1) I find conflicting information (mostly from salespersons) about 
   how many repeaters I can have in my network. One source says
   2 another says 3 and yet another says 4. Which is correct?
   (I should say, how many can I have between to communicating
   systems on the same ethernet (i.e. not broken by a non-repeating
   apparatus such as a bridge or gateway?)

2) Is a repeater effectively two transceivers? If so, then do
   the thin to fiber converters (one at each end of fiber) count
   as one repeater?

3) Which is the correct way to wire a thinnet segment into a 
   multiport repeater?
  
   a)                                  b)
  
    .------------.                       .--------------.
    | mpr box    |                       | mpr box      |
    `---.--------'                       `----.---------'
        |                                     |
    |---T--------------|                      |
                                              |
                                              -     <-terminator
    (two terminators, t-connection        (one terminator, direct bnc
     to multiport repeater)                connection to multiport repeater)

    I'm 99% sure it's (b), but I have to resolve this issue to the
    satisfaction of all. (BTW would (a) be correct for a bridge?)

4) Can a transceiver be plugged directly into the workstation, or
   is there some reason that you must use the tranceiver cable?

5) Are thinnet segments supposed to be grounded somewhere?

Thank you kindly for your assistance!
-- 
Bill Baskett, Network Manager       vx: 604 363-4635 fx: 604 363-4513
Royal Roads Military College        em: BBaskett@post.RoyalRoads.ca
Victoria, B.C.                      "this space for hire"
Newsgroups: comp.dcom.lans.ethernet
Subject: 10baseT crossover cable
From: bartont@next2.msci.memst.edu (Tom Barton)
Date: 20 Aug 92 18:57:59 -0600
Followup-To: bartont@hermes.msci.memst.edu
Distribution: world
Organization: Mathematical Sciences, Memphis State University
Keywords: 10baseT, crossover
Summary: What's the correct way to wire a crossover cable?

What's the correct way to wire a 10baseT crossover cable? I'd like to make a
two station lan using twisted pair and no hub. The ethernet adapters I'll use
have an RJ45 connector. Also, is it necessary to wire the RJ45's with all 4
pairs?

Thanks.

-- 
Tom Barton			       Internet: bartont@hermes.msci.memst.edu
Department of Math Sciences	       Internet: bartont@next2.msci.memst.edu
Memphis State University	         Bitnet: bartont@memstvx1
Memphis, TN 38152			  Phone: 901/678-2527
Newsgroups: comp.dcom.lans.ethernet
From: gary@sci34hub.sci.com (Gary Heston)
Subject: Re: Problem with thin wire and terminated T connectors.
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Systems, Inc., Huntsville, Al.
Date: Fri, 21 Aug 1992 13:55:09 GMT

In article <13AUG199210030803@mivax.mc.duke.edu> jim@mivax.mc.duke.edu (James D Dryfoos - Systems) writes:
|A long time ago when we started putting in thire wire segments to connect
|groups of terminal servers in one closet we decided it was convenient to leave
|one or two blank T connectors for later connections without disrupting the net. 
|We were concerned about this as we have heard that these T connectors could
|pick up transient signals and maybe cause problems.  It was advised that they
|have a terminator stuck in them.

Whoever advised you of this is an idiot who knows nothing about how
transmission lines work.

|                                  So, a barrell connector and terminator were
|connected to each empty T connector.  The thin wire worked so it was left that
|way.  I recently was involved in troubleshooting the poor performance of
|terminal servers on these thin wire nets.  I saw the terminators and thought
|that I had not seen that done before, so removed them.  Sure enough, the
|terminal servers began responding flawlessly.  The terminators caused the
|servers to retransmit packets now and then.  I assume some packets were being
|destroyed by a signaling problem that the terminators must have created?

The extra terminators were loading the output of the transceivers so
badly that the transceivers' input couldn't read the signal. There were 
possibly some reflection problems too, depending upon the length of the
segement, from the impedance mismatch.

If there are any other segements around your network that were "fixed" in
this manner, un-fix them. Your users will appreciate the improvement in
reliability.

|I would like to hear anyone's thoughts on this.  Also, is leaving unconnected T
|connectors on the wire really a problem?

One terminator at each end of the segement, period. That's what the spec 
calls for. *No* terminators at intermediate points.

I have a net with about 150 Tees installed, and about 45 actually connected.
I have *zero* problems with noise. (I've got an intermittant connector
somewhere in one segement, though. :-( ) I connect and remove devices all
the time with no network disruption.

The only consideration about unconnected Tees is that they do count in 
the total allowd connections per segement (30) with thinnet.

-- 
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.
Hestons' First Law: I qualify virtually everything I say.
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.dcom.lans.ethernet
Subject: Help with AE2 ethernet cards 
Distribution: world
Date: Wed, 12 Aug 92 02:19:45 GMT
Organization: Crynwr Software

In article <1992Aug10.013233.487@ccsvax.sfasu.edu> a_millsbs@ccsvax.sfasu.edu writes:

   I have aquired 2 Lantastic  AE2 16-bit Ethernet adapters.  I have no docs, no
   software, nothing but the cards.

   Can anyone out there give me any informations on them?  Does Artisoft have a
   BBS?  Are there packet drivers available for them.  Any help appreciated.

The cards have a NE-2000 compatability mode, and the Crynwr
NE2000.COM packet driver works on them.  Send me mail for more info
on packet drivers...

-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
Crynwr Software            Crynwr Software sells packet driver support.
11 Grant St.               315-268-1925 Voice
Potsdam, NY 13676          315-268-9201 FAX
From: relee@acpub.duke.edu (Robert Lee)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Sytek
Date: 17 Aug 92 14:29:48 GMT
Distribution: na
Organization: Duke University; Durham, N.C.

Sytek was purchased by GM's Hughes Electronics division and is now
called Hughes Lan Systems. They are still at their previous address:
1225 Charleston Road, Mountain View, CA 94043. Their phone number is
(415) 966-7400. 

The card you have is probably an IBM PC LAN adapter. It is a 2Mb/sec
Radio frequency broadband adapter that runs on 75ohm (CATV) coax. The
typical application is for use with the IBM PC LAN Program, but drivers
are available for other networks.

----------------------------
Robert Lee
relee@raphael.acpub.duke.edu
From: mosbrook@beach.csulb.edu (Brent Mosbrook)
Newsgroups: comp.dcom.lans.ethernet
Subject: Sytek
Date: 16 Aug 92 02:03:30 GMT
Distribution: na
Organization: Cal State Long Beach


I just got a couple cards, 8 bit, which are some sort of RF LAN type cards for
the IBM.. they have a coax, type F connector, like a VCR.


the bios and everything else is stamped Sytek, with a part # of A004087-01

I have no clue as to what these are, as you can probably guess by now.

anyone know?, or does anyone know where I can reach Sytek?


-- 
+--------------------------------------+
|  Brent Mosbrook    KC6MWK            |
|         mosbrook@beach.csulb.edu     |
+--------------------------------------+
Newsgroups: comp.dcom.lans.misc,comp.dcom.lans.ethernet