According to Julian =?ISO-8859-1?Q?Mu=F1oz?= =?ISO-8859-1?Q?Dom=EDnguez?=: While
burning my CPU.
>
> Hello Richard,
>
> >Firstly one would imagen a t_2 timer time of 1.5 seconds far to short for a
> >1k2 link.
>
> I am using this value long time with jnos, and that worked perfectly. It was
> e
Hello Richard,
>Firstly one would imagen a t_2 timer time of 1.5 seconds far to short for a
>1k2 link.
I am using this value long time with jnos, and that worked perfectly. It was
enough to piggy-back and to concatenate acks. In fact, it seems not to be the
problem, because if t2 expires it shou
According to Julian =?ISO-8859-1?Q?Mu=F1oz?= =?ISO-8859-1?Q?Dom=EDnguez?=: While
burning my CPU.
>
>
> If the t2 timer expired before sending the I packet, the RR would be before it,
> not after.
>
> I don't find any explanation. This happens sometimes. t2 is 15 (1,5 seg), at
> 1200 bauds.
>
Hello, I'd like to ask for help to the programmers of ax25.
I am ananlyzing the behaviour of ax25 protocol in Linux, and I am seeing things
that I am not able to understand, even looking the sources:
Here an example, maybe related with ax25 timers. The remote station
(ea4rct, running Linux) is s
