[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.1.103 and IPX

To: linux-tr@emissary.aus-etc.com
Subject: Re: 2.1.103 and IPX
From: Paul Norton <pnorton@ccnvhi.com>
Date: Tue, 09 Jun 1998 16:27:10 -0700
In-reply-to: <199806092226.RAA11952@verdict.uthscsa.edu>
References: <199806092112.OAA01220@grumpy.ccnvhi.com><199806092226.RAA11952@verdict.uthscsa.edu>
Reply-to: linux-tr@emissary.aus-etc.com
Sender: owner-linux-tr@emissary.aus-etc.com

Gilbert Ramirez Jr. writes:
 > Analysis:
 > We still have the RIF that contains no bridge-ring info (C2 20).
 > The LLC is SNAP, but shows protocol code "00 01". I don't have my book
 > handy; what is IPX's SNAP code? I see "E0 E0" after the SNAP LLC, which
 > are the DSAP and SSAP codes if this were a non-SNAP LLC. The rest,
 > "FF FF" and on, is the IPX packet.
 > 
 > So, perhaps 2.1.103 is trying to put SNAP __and__ non-SNAP headers on these
 > packets?

It certainly looks that way.  I have no idea what a SNAP code of 0001
is.  IPX is 8137.

Follow-Ups:
- Re: 2.1.103 and IPX
  - From: "Gilbert Ramirez Jr." <gram@verdict.uthscsa.edu>

References:
- Re: 2.1.103 and IPX
  - From: Paul Norton <pnorton@ccnvhi.com>
- Re: 2.1.103 and IPX
  - From: "Gilbert Ramirez Jr." <gram@verdict.uthscsa.edu>

Prev by Date: Re: 2.1.103 and IPX
Next by Date: Re: 2.1.103 and IPX
Previous by thread: Re: 2.1.103 and IPX
Next by thread: Re: 2.1.103 and IPX
Index(es):
- Date
- Thread