John:
It has happened here with users with faulty, deaf, modems or choked up
computers (bad memory management setup), whenever polling gets spawned
and then becomes very very wasteful of the packet channel capacity.
I think it was Julian, EA4ACL that discussed that on this list around
march or
On Sat, 05 Feb 2000, John Ackermann wrote:
> Terry wrote:
>
> > What do you have your T3 timer set to? (cat
> > /proc/sys/net/ax25/*/t3_timeout).
> >
> > I think that would be what is causing these transmissions.
> >
> > T3 is known as 'CHECK' in some AX.25 implementations. It's an idle poll
>
Terry wrote:
> What do you have your T3 timer set to? (cat
> /proc/sys/net/ax25/*/t3_timeout).
>
> I think that would be what is causing these transmissions.
>
> T3 is known as 'CHECK' in some AX.25 implementations. It's an idle poll
> to ensure the remote end is still there.
Hi Terry --
t3_t
John Ackermann wrote:
> The Linux setup is kernel 2.0.34 with ax25-module-14 and utils 2.1.42a.
> For the 19.2 link, we're running a T1 timer of 2.5 seconds, and T2
> timer of 200ms.
>
> [Fri Feb 4 20:40:00 2000]
> Port pi0a: AX25: N8BJQ->W8APR-3
>
> [Fri Feb 4 20:40:00 2000]
> Port pi0a: AX2
Sorry if this is totally ignorant, but I've had embarassingly little
experience tracing AX.25 protocol issues.
I'm trying to track down some serious performance problems on our
19.2kb network. We're seeing frequent disconnects between a Linux
AX.25 station and a G8BPQ node.
The Linux setup i
