[nos-bbs] Raw Packet Stream

[Michael Fox - N6MEF]

If you redirect the trace to a file, then it won't be in the F9 screen.

As I put in my email below, use "tail -f" to view the file in linux.

Michael
N6MEF

-----Original Message-----
From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf
Of Brett Friermood
Sent: Monday, May 21, 2012 6:28 PM
To: TAPR xNOS Mailing List
Subject: Re: [nos-bbs] Raw Packet Stream

No go on F9. Just a blank screen. I tried it both during and after hearing
packets and nothing. Switch back to the console and those stations are in
the heard list.

I'm currently upgrading my laptop so I can't try using tracing at the
moment.

Brett
KQ9N


On Mon, May 21, 2012 at 11:35 AM, Michael Fox - N6MEF <n6mef at mefox.org>
wrote:
> We've tested down to a quarter second (value of 250 at the end of the 
> trace
> command) with 3 ports running at the same time - no problem on a 
> little Atom
> 530 processor.  We normally have ours set to 1000 (1 second).  Then 
> just tail -f from linux.  We also logrotate the trace files so we can 
> go back days later and analyze a problem.
>
> Michael
> N6MEF
>
> -----Original Message-----
> From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On 
> Behalf Of Brett Friermood
> Sent: Monday, May 21, 2012 9:14 AM
> To: TAPR xNOS Mailing List
> Subject: Re: [nos-bbs] Raw Packet Stream
>
> Thanks, guys. I'll try the F9 key the next time I'm on packet.
>
> But Michael's method seems useful also.
>
>
> On Mon, May 21, 2012 at 11:00 AM, Michael Curry <dgspotman at gmail.com>
wrote:
>> Ergh, sorry, I should have said "tracing", not "logging". And the 
>> command is "trace", not "ax25 log". I should have looked at my 
>> autoexec.nos before responding, rather than trying to do it from memory.
>>
>> The line from my autoexec.nos is:
>>
>> trace tnc1 4211 tnc1_trace 10000
>>
>> Where tnc1 is the AX.25 interface to be traced, 4211 is the flag set, 
>> tnc1_trace is the name of the output file, and the 10000 means "flush 
>> the buffered trace output to the file every 10 seconds".
>>
>> Sorry for any earlier confusion.
>>
>> KI6TYV, Michael
>>
>>
>>
>> On Mon, May 21, 2012 at 8:42 AM, Michael Curry <dgspotman at gmail.com>
> wrote:
>>>
>>>
>>>> If you built with axui enabled, you can watch from the jnos console 
>>>> window.
>>>
>>>
>>> Hmm... shouldn't axui only show UI ("unnumbered information") frames.
>>> I wouldn't expect it to show any frames from connected-mode AX.25
> exchanges.
>>>
>>> Actually, in my experience, axui doesn't even reliably show all the 
>>> UI-frames. Please see 
>>> http://www.tapr.org/pipermail/nos-bbs/2012-May/003636.html (and if 
>>> you have any insight on why the problem I describe there may be 
>>> happening, I'd love to hear it).
>>>
>>> My solution to the OP's problem, also documented in the thread 
>>> referenced above, is to turn on logging for the AX.25 interface in 
>>> question, and then run "tail -f" against the output file. A caveat 
>>> here is that you need to know about the undocumented fourth 
>>> parameter to "ax25 log", which is the rate at which JNOS flushes 
>>> buffered log entries to the output file (expressed in milliseconds,
IIRC).
>>>
>>> Hope this helps.
>>>
>>> KI6TYV, Michael
>>
>>
>>
>>
>> --
>> This cat is pushing a watermelon out of a lake. Your argument is invalid.
>>
>>
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs

_______________________________________________
nos-bbs mailing list
nos-bbs at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs