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
> > to ensure the remote end is still there.
>
> Hi Terry --
>
> t3_timeout is set to 3000 (5 minutes, if I did the conversion
> correctly) on the linux machine. That oughtn't cause any problems. I
> don't know what the equivalent setting on the G8BPQ system is, but I'll
> find out.
>
> What's interesting is that both ends seem to be initiating the
> sequence, or perhaps one end is responding to the poll with both a
> final, and a new poll of its own?
If it is of any interest, i too have seen this happen on our local
lan here.
It seems only to happen when the remote stn, is using a dos based
program. I seem to remember writing about this to the list a long time
ago, however i dont worry about it as i have never seen it between 2
linux macines and further more we dont have many ax25(dos) users here
on our lan, it 95% IP with linux.
BTW, the system concerned uses;
2.0.36
ax25 utils 2.1.42a
PA0HZP scc card,
z8530drv version 2.4c.dl1bke
scc.c = scc.c,v 1.67
t3 = 3000 also.
If i can be of any help let me know.
> 73,
> John
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
