Re: IPX, 2.2, and collisons [was: 2.2.* on slink]

To: Mirek Kwasniak <mirek@zind.ikem.pwr.wroc.pl>
Cc: Debian User List <debian-user@lists.debian.org>
Subject: Re: IPX, 2.2, and collisons [was: 2.2.* on slink]
From: "Richard E. Hawkins" <hawk@hawkins.cba.uni.edu>
Date: Mon, 13 Sep 1999 07:44:09 -0500
Message-id: <[🔎] m11QVT3-000QjHC@hawkins.cba.uni.edu>
In-reply-to: Message from Mirek Kwasniak <mirek@zind.ikem.pwr.wroc.pl> of "Sat, 11 Sep 1999 12:59:43 +0200." <[🔎] 19990911125943.F19879@zind.ikem.pwr.wroc.pl>

mirek mentioned,
 > > But can someone tell me what causes IPX collisons?  I get lots of 
> > 
> > Sep 10 12:49:53 hawkins kernel: IPX: Network number collision 24899 
> > Sep 10 12:49:53 hawkins kernel:         eth0 802.3 and eth0 802.2 
> > 
> > messages.  Is this me, or is there something wrong on the network?  [Our tech support *barely* tolerates me using linux, so i can't ask them]

> Colisions generated by misconfigurated W'95 stations that have settings
> frame->auto.


Ahh, so then it's not my fault, and I can tell them about it :)

Thank you

rick


--

Reply to:

References:
- Re: IPX, 2.2, and collisons [was: 2.2.* on slink]
  - From: Mirek Kwasniak <mirek@zind.ikem.pwr.wroc.pl>

Prev by Date: Re: mc not working (?) now smb.conf failure
Next by Date: make-kpkg doesn't make different kernel source revs.
Previous by thread: Re: IPX, 2.2, and collisons [was: 2.2.* on slink]
Next by thread: Re: 2.2.* on slink
Index(es):
- Date
- Thread