Re: 2.1.103 and IPX

["Gilbert Ramirez Jr." <gram@verdict.uthscsa.edu>]

As Paul Norton said:
> 
> Ok, I'll assume that IPX 802.2 was working and now is not.  I'll look
> into it tonight.

I ran an ipx_configure --auto --auto on 2.1.103, with the MTU patch.
It could not configure itself.

I then set my IPX interface to what it should be:

ipx_interface add -p tr0 802.2TR c0a82c00

(
which is what it should be. /proc/net/ipx_interface under 2.0.30 shows:
Network    Node_Address   Primary  Device     Frame_Type
C0A82C00   08005A68F02C   Yes      tr0        802.2TR
)

I then ran an 'slist' command while running a sniffer (LanAlyzer)
on the same ring. Here's the analysis of the packets, filtered on
my linux machine's MAC address. There were 2 non-IP packets leaving
my machine (08-00-5a-68-f0-2c) after I typed 'slist' and press ENTER.
One was just a "Standby Monitor Present" packet, the other is a packet
which is almost IPX:

Packet Number : 3           5:17:52 PM
Length : 57 bytes           
802.5: =================== IEEE 802.5 Datalink Layer ===================
       AC: Frame, Priority=0, Monitor Count=1, Priority Reservation=0
       FC: LLC Frame, Attention Code=0
       Station: 08-00-5A-68-F0-2C ----> Broadcast
       Source Routing Information:
         Length: 2 bytes
         Broadcast: Single-route brdcast, all routes  return
         Direction: From originating station
         Largest Frames: 2052 bytes (LF=2)
802.2: ================ IEEE 802.2 Logical Link Control ================
       SSAP: SNAP     DSAP: SNAP
       Unnumbered Command: Unnumbered Information (UI)
       SNAP Organization Code: 00 00 00
       SNAP Protocol Type: 0x0001 
Data:
   0: E0 E0 03 FF FF 00 22 00 FF FF FF 04 52 C0 A8 2C |......".....R..,
  10: 00 08 00 5A 68 F0 2C 40 00 00 03 00 04          |...Zh.,@.....   


Here is the hex dump of that packet:

Packet Number :       3
   0: 18 40 FF FF FF FF FF FF 88 00 5A 68 F0 2C C2 20 |.@........Zh.,. 
  10: AA AA 03 00 00 00 00 01 E0 E0 03 FF FF 00 22 00 |..............".
  20: FF FF FF 04 52 C0 A8 2C 00 08 00 5A 68 F0 2C 40 |....R..,...Zh.,@
  30: 00 00 03 00 04                                  |.....           

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?

--gilbert

-- 
Gilbert Ramirez                Voice:  +1 210 358 4032
Technical Services             Fax:    +1 210 358 1122
University Health System       San Antonio, Texas, USA