On Wed, 15 Sep 1999, Jan Wasserbauer wrote:
> Jan Wasserbauer <[EMAIL PROTECTED]> wrote:
> > > IMHO TNT is broken in this case. Why does it need to read it so often?
> > TNT periodically reads channel status. I am trying to get it working using
> > ioctl but can't find any way how to get number of unacked frames. Normally TNT
> > counts unacked frames using vs&va but those are not in ax25_info_struct.
> > Is there some other way to get those counters ?
>
> I got no reply to my mail so I assume the only way to get number of
> unacked frames is using VS&VA counters in /proc/net/ax25.
>
> So .. could someone update ax25_info_struct (and kernel ioctls) to include
> VS and VA (or just # of unacked) and maybe some other values too
> (window, paclen, device ..) ?
>
> In current state the software HAS TO be broken.
Sorry. I meant to send a reply but forgot...
Anyway, there are two issues here. First: you say software has to be
broken. Well, in my opinion the notion that a piece of software needs to
know what happens underneath it (with 300ms granularity) is _completely_
broken. Unless of course if the whole idea of AX.25 networking is not the
information transfer but to see if the information can be transferred...
But then again, reading the amateur radio legistlation, the latter
actually seems to be the point. :)
The /proc interface we will not be able to change. The way I have
understood it, in Linux stability just goes above functionality. And
functionality that requires unstability is concidered broken. This is what
differs us from the products of Redmond...
But the issue of ax25_info_struct is another thing in my opinion. Offhand
I cannot see a reason why the vs/va info or for that matter any info in
the control block couldn't be passed from the kernel to the user. I will
look into that problem and see if I can make a patch fix the situation.
--
--... Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ...--
