Wireshark mailing list archives
Re: ISDN Layer 3 decode
From: "Keith French" <keithfrench () btconnect com>
Date: Mon, 14 Nov 2011 16:09:31 -0000
I have added a couple more traces, one of a complete audio recording of a b channel (no buffer overflows in it). The other one has a problem over the source & destination of User & Network being the wrong way around when the C/R bit is correctly set to 1. There is an example of a layer three message coming from the NT with C/R=1, but Wireshark gets the C/R correct but shows it as coming from the TE.
-----Original Message----- From: Keith French
Sent: Saturday, November 05, 2011 2:13 PM To: Community support list for Wireshark Subject: Re: [Wireshark-users] ISDN Layer 3 decode I think I have covered everything new bugs 6542 & 6543.-----Original Message----- From: Guy Harris
Sent: Saturday, November 05, 2011 12:22 AM To: Community support list for Wireshark Subject: Re: [Wireshark-users] ISDN Layer 3 decode On Oct 30, 2011, at 3:16 PM, Guy Harris wrote:
On Oct 30, 2011, at 11:40 AM, Keith French wrote:Just a thought, as you'd like more traces. I have quite a few from my lab that are DPNSS and again Wireshark has a good DPNSS dissector. The Aethra decode for DPNSS is excellent, but if you want to check more L2 stuff, will they be of any use?Sure - the more the better. (It might also suggest DPNSS improvements, if the Aethra decode is excellent and the Wireshark is just good.)
Well, one improvement would be to let it decode DPNSS-over-LAPD, which it currently can't do, and which is in some of the captures attached to the bug. I've put some comments into the bug; you should file a new, separate bug on DPNSS-over-LAPD. Is there any standard (international or national) that says a SAPI of 17 is used for DPNSS, or is that just what happens to be used on the call in "Buffer overflow due to serial port connection too slow.aps"? ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Re: ISDN Layer 3 decode Guy Harris (Nov 04)
- Re: ISDN Layer 3 decode Keith French (Nov 05)
- Re: ISDN Layer 3 decode Keith French (Nov 14)
- <Possible follow-ups>
- Re: ISDN Layer 3 decode Chris Maynard (Nov 09)
- Re: ISDN Layer 3 decode Keith French (Nov 10)
- Re: ISDN Layer 3 decode Matthew (Nov 10)
- Re: ISDN Layer 3 decode Chris Maynard (Nov 19)
- Re: ISDN Layer 3 decode Chris Maynard (Nov 20)
- Re: ISDN Layer 3 decode Guy Harris (Nov 20)
- Re: ISDN Layer 3 decode Keith French (Nov 20)
- Re: ISDN Layer 3 decode Keith French (Nov 21)
- Re: ISDN Layer 3 decode Keith French (Nov 10)
- Re: ISDN Layer 3 decode Keith French (Nov 05)