[nos-bbs] Raw Packet Stream

[Michael Curry]

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20120521/ffd867c0/attachment.html>