&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest33976
Irc2PGuest51880
Irc2PGuest97218
Irc2PGuest99581
Onn4l7h
Sisyphus
Sleepy_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m
bak83_
duanin2
duck
elthommy
john231
leopold_
makoto
nilbog-
not_bob_afk
ntty
poriori_
profetik1
r00tobo_BNC
rapidash
shiver_
sidereal
solidx66
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
orignal
zzz, small question about SAM
orignal
when a command session gets diconnected and reconnects back immeditely you assign old session, right?
orignal
my question is for how long do you keep a session after diconnect
zzz
orignal, session is torn down immediately, there is no "grace period"
orignal
why?
orignal
so user has a wifi glitch and have to create session/destination from scratch?
orignal
it seems wrong
orignal
what do you think if I try to implement this?
orignal
to improve stability
zzz
sounds like more trouble than it's worth
orignal
what kind of troubles?
orignal
if you reconnect quickly during grace period
zzz
sounds to me like it would be complex to implement, saving all the state
zzz
would individual sockets stay up? how do you know it's the same endpoint? doesn't sound fun
zzz
to me anyway
orignal
I don't need to know same endoint I only need to know session id
orignal
if I see SESSION CREATE with existing session id during grace period I don't decline but assign onld one
zzz
doesn't sound great to me, but it's up to you
orignal
how about dest?
orignal
not session
orignal
e.g. session dies right a way while assiciate dest doesn't
zzz
we tear it all down immediately
orignal
that's really wrong
orignal
you have to recreate tunnels again
orignal
immediately
zzz
it's a corner case not worth worrying about imho. fine if you want to