> From: Leif Johansson <leifj@xxxxxxxx>
> I have one that shot down my ssh sessions after 5 minutes of aparent
> inactivity .. This is a *major* supplier of soho equipment. Moreover it
> was clear from the support-forum that this was a concious choice.
It's not at all clear to me that this was the wrong engineering choice on
their part. If they didn't GC dead connections after some sort of timeout (and
would it make any significant different whether it was 5 minutes, or 1 hour)
it would consume resources and perhaps lead to problems.
Although I suppose they could impose an LRU algorithm on state blocks,
instead. I'd have to think about it for a while, to see if there were other
problems caused by not GC'ing inactive mappings.
Furthermore, it's relatively easy to avoid the SSH session problem - my
default login on Unix boxes has for many years now included starting this
shell script in the backgound:
while 1
echo " "
sleep 600
end
precisely to avoid having them shut down due to NAT timeouts (no matter how
long I go without typing on them).
Noel
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf