Ethereal-users: [ethereal-users] Problems with LLC1 and OSI
Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.
From: Denis GARCIA <denisgca@xxxxxxxxxxxxxxxx>
Date: Sun, 09 Apr 2000 14:06:36 +0000
First, i'd like to say that Ethereal is an excellent tool. Thanks to author and all contributors. I use Ethereal 0.8.4 and next 0.8.6, and I have two problems with LLC1 and OSI. 1) LLC 1. -------- In frame 185 and 186, i have a trouble with summary line, protocole display and filters. The info say 'response' for command' and 'command' for 'response'. If you try to make a 'match selected' after selected Data in protocole window, the filter take also DSAP, SSAP, Control field and data ( 6 bytes instead of 3 ). Frame 185 (60 on wire, 60 captured) IEEE 802.3 Destination: 00:80:02:00:00:03 (SATELCOM_00:00:03) Source: 00:80:02:00:00:09 (SATELCOM_00:00:09) Length: 6 Logical-Link Control DSAP: Ungermann-Bass (0xfa) IG Bit: Individual SSAP: Ungermann-Bass (0xfa) CR Bit: Command Control field: U, func = TEST (0xE3) 111. 00.. = Test .... ..11 = Unnumbered frame Data (6 bytes) 0 0080 0200 0003 0080 0200 0009 0006 fafa ................ 10 e353 4154 0000 0000 0000 0000 111c 4eff .SAT..........N. 20 0420 bc4b 010c 04d8 4077 84a8 0396 5056 . .K....@xxxxxxx 30 6b76 03c0 5dba 02b2 02a8 4075 kv..].....@u ********* Frame 185 ********* Bugs ? ********* Data = 3 bytes = 'SAT' ( not 6 bytes ) ********* The Info in the first window say : ********* SSAP Ungerman-Bass Response ********* but I think thas it was SSAP Ungerman-Bass Command ? Frame 186 (60 on wire, 60 captured) IEEE 802.3 Destination: 00:80:02:00:00:09 (SATELCOM_00:00:09) Source: 00:80:02:00:00:03 (SATELCOM_00:00:03) Length: 6 Logical-Link Control DSAP: Ungermann-Bass (0xfa) IG Bit: Individual SSAP: Ungermann-Bass (0xfa) CR Bit: Response Control field: U, func = TEST (0xE3) 111. 00.. = Test .... ..11 = Unnumbered frame Data (6 bytes) 0 0080 0200 0009 0080 0200 0003 0006 fafb ................ 10 e353 4154 0000 0000 0000 0000 111c 4eff .SAT..........N. 20 0420 bc4b 010c 04d8 4077 84a8 0396 5056 . .K....@xxxxxxx 30 6b76 03c0 5dba 02b2 02a8 4075 kv..].....@u ********* Frame 186 ********* Bugs ? ********* Data = 3 bytes = 'SAT' (not 6 bytes) ********* SSAP = 0xfb ( not 0xfa ) ********* The Info in the first window say : ********* SSAP Ungerman-Bass Command ********* but I think thas it was SSAP Ungerman-Bass Response ? 2) OSI ------ Here, i have a trouble with the protocole decode. In the PDU here 17 bytes, there is, if i don't mistake, another PDU, after Ak's PDU ( 0x06 ), i see a DT's PDU ( 0xf0 ). Frame 29 (96 on wire, 96 captured) IEEE 802.3 Logical-Link Control ISO CLNP ISO COTP Length indicator: 4 TPDU code: Ox6 (AK) Credit: 5 Destination reference: 0x7203 Your TPDU number: 0x59 Data (17 bytes) 0 0800 09f0 d344 0800 0bc3 e121 0052 fefe .....D.....!.R.. 10 0381 3901 13bc 004f 0000 1447 0027 8146 ..9....O...G.'.F 20 5241 0041 5443 00c3 0012 00c3 0006 2114 RA.ATC........!. 30 4700 2781 4652 4100 4154 4300 c300 1200 G.'.FRA.ATC..... 40 c300 0321 1411 0000 004f 0465 7203 5904 ...!.....O.er.Y. 50 f072 03b0 434f 4e4e 4558 494f 4e20 4f4b .r..CONNEXION OK Take a look on the data : ------------------------- 40 04 . 50 f072 03b0 434f 4e4e 4558 494f 4e20 4f4b .r..CONNEXION OK Here, what i suppose to be in the data (17 bytes) : --------------------------------------------------- 40 04 Length indicator : 4 50 f0 TPDU code : 0xf0 (DT) 51-52 7203 Destination reference : 7203 53 b0 TPDU number : 30 (complete) 54-5f data 'CONNEXION OK' ( In OSI protocole, you can transmit an DT after an ACK in the same frame.) Thanks...
- Follow-Ups:
- Re: [ethereal-users] Problems with LLC1 and OSI
- From: Guy Harris
- Re: [ethereal-users] Problems with LLC1 and OSI
- Prev by Date: [ethereal-users] how stopp a suspect session
- Next by Date: Re: [ethereal-users] Problems with LLC1 and OSI
- Previous by thread: [ethereal-users] how stopp a suspect session
- Next by thread: Re: [ethereal-users] Problems with LLC1 and OSI
- Index(es):