Skip to contentSkip to conversation

ax25 t1_timeout

DISCUSSION jarmo 2 participants 2 messages Mar 6, 2005 – Mar 7, 2005

lore
Share & tools
lore

jarmo

author
#0 lore raw

Hi
Withs kernel 2.6.11 ax25 t1_timeout is working badly... Expl. I have set t1_timeout to 10s (10000).Now testing.. Taking radio of,set connection to somewhere,first try then 10s time second try...But then 20s and try next 30s and try... So t1_timeout is increasing?In 2.6.10 timeout is 10 and it does not increase...Possible bug?

Jarmo

Signature · 3 lines
Linux is the answer.
What was your question?
(Brian Lane)
#1 lore raw
Quoted 6 lines · jarmo

Withs kernel 2.6.11 ax25 t1_timeout is working badly... Expl. I have set t1_timeout to 10s (10000).Now testing.. Taking radio of,set connection to somewhere,first try then 10s time second try...But then 20s and try next 30s and try... So t1_timeout is increasing?In 2.6.10 timeout is 10 and it does not increase...Possible bug?

No, pilot error ;-)

Linux supports three different backoff types which can be configured via /proc or sysctl. This is how to display the backoff type of interface sp0, for example:

[root@dl5rb] sysctl net.ax25.sp0.backoff_type
net.ax25.sp0.backoff_type = 1
[root@dl5rb]

1 in this example stands for linear backoff which is the default and what you've been observing. 0 would be no backoff which generally in a shared RF environment is probably unfriendly and can mathematically be shown to cause network meltdowns. Finally 2 would means exponential backoff, which would use t1, 2*t1, 4*t1, 8*t1 for the waiting time, but never goes worse than 8 * t1.

You can change the value with sysctl also but generally linear backoff is quite reasonable.

73 de DL5RB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21