On 3/18/07, Bernard Pidoux <[EMAIL PROTECTED]> wrote:
Chuck Hast wrote: >...What listen does > not show is the GFI, it does show the LCI and in the call request packet > the > random number (NbAlea) which is used to assign the LCI. Nor does it show > the cause/diag code data when there is a error or a disconnect. > > So any work you do in this direction will be a big help for us. > > Actually, listen provides some error diagnostic including the point where the link failed as shown here : 0: fm KP4DJT-9 to F6BVP-11 ctl I72^ pid=1(X.25) len 26 X.25: LCI 031 : CLEAR REQUEST - Cause DTE Originated - Diag 0 at N3PPC-9 @3100,386335 0: fm KP4DJT-9 to F6BVP-11 ctl RR0v Not so bad.
Yes, that is how I knew that we were getting the error location information, I was watching it in Listen and observed that on the fpac console it did not match. But being able to have a full set of tools in WireShark (was Etherreal) for data collection and analysis would be a very good thing, so I encourage him to get as much info as possible to integrate X.25 PLP so we have one more tool to use. -- Chuck Hast -- KP4DJT -- To paraphrase my flight instructor; "the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal." - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
