@RN_
@StormyCloud
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%acetone
%snex
+FreefallHeavens
+NiceBoat
+Onn4l7h
+Onn4|7h
+Over
+marek22k
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+r00tobo
+sidereal
+uop23ip
AlV5tGf7
Arch
Danny
Holmes
Irc2PGuest18834
Irc2PGuest28384
Irc2PGuest34440
Irc2PGuest58692
Irc2PGuest6967
Irc2PGuest80220
Liorar_
OfficialCIA
RTP_
ahiru
anontor
cims
eyedeekay_
leopold
mahlay
makoto
n2
nilbog
not_bob_afk
pory
r00tobo[2]
r00tobo[2]_
sahil
sektorchef
not_bob
zzz: Only 50!?
not_bob
I can't say for sure, but I may have more than 50 SAM sessions running at a time. But, they are very short lived.
not_bob
Transient tunnels are way up in the last 7 days. What's up with that?
zzz
50 for canon. no idea about plus
zzz
re: part. tunnel count, don't see that in my data
not_bob
Curious.
zzz
do you have any insight into the group of encrypted leasesets we're seeing?
not_bob
I do not.
zzz
probably some botnet got creative
not_bob
I don't collect data on those, so they are pretty much invisible to me.
not_bob
Likely, yes.
not_bob
Anyway, I group each tunnel into one off three groups.
not_bob
1. Has been around more than 1 months.
not_bob
1. Has been around for more than 7 days.
not_bob
2. Anything else (short lived).
not_bob
About 5 days before the feb "attack" I noticed the transient tunnles grow like crazy in percentage.
not_bob
I noticed that post atttack.
not_bob
So much data, hard to tell what signals might be key.
nyaa2pguy
could the transient tunnels also just be a sign of an in-network ddos?
not_bob
nyaa2pguy: I have no idea what they are other than short lived tunnels.
not_bob
It's my floodfill view of the world.
nyaa2pguy
interesting. unrelated: is there a way to 'name' sam clients?
nyaa2pguy
can get a little vague in the java console when you have lots of them
nyaa2pguy
ah i think i found it: inbound.nickname
zzz
yup
dr|z3d
ok, minor headsup. latest + builds (release/dev) now have a simplified local tunnel replacement strategy which shiuld result in more robust local tunnels, more redundancy, less chance of failure.
dr|z3d
you'll see more tunnels per dest/exploratory on /tunnels which is the new normal. once a tunnel has less than 5 minutes to expiry, we build a new one. we also keep around a couple of extras beyond whatever you have configured, with a minimum of 4.
dr|z3d
your router may work marginally harder to build tunnels, but you'll have greater redundancy should any fail, or if the network starts misbehaving.
dr|z3d
ok, more new stuff for tunnel pools in the latest build. we now check each tunnel in each pool and compare against the global average latency.
dr|z3d
if any tunnel that's been tested is >=150% of the global average, we'll nuke it from slowest up until we're at configured number of tunnels. nuked tunnels will rebuild.
dr|z3d
what this should mean, assuming it doesn't shit the bed, is that for any given service, client or server, laggy tunnels will get automatically removed and you should have lower latency tunnels for both client and server.
dr|z3d
available in dev builds only for now.
dr|z3d
you can keep an eye on things on /tunnels ... you'll regularly see tunnels reporting high latency disappearing.. *poof*
dr|z3d
also, for tables in the console that support dynamic sorting, you may notice faster sorting courtesy of a worker thread that runs the sort off the main thread. should keep things a bit more responsive for larger tables.
not_bob
dr|z3d: I'm using a recent build and it's working much better now.
dr|z3d
great, not_bob_afk.. thanks for the feedback.. it's been a bit of a rodeo.. you may want to make sure you're on the latest build if you haven't updated in the last 1/2 hour for maximum goodness :)
sidereal
would this have anonymity implications by tunnels eventually not being able to repeatedly jump halfway across the globe?
dr|z3d
?
dr|z3d
if you're asking what I think you're asking, the answer is "no".
dr|z3d
latency is the RTT, the time to send a message and get a response from a tunnel. while geographical location may have a minor influence on latency, it's not the main reason tunnels are laggy. overloaded routers, routers running on potatoes.. only needs to be one between you and the destination that's laggy to bring the latency up.
sidereal
ah, I see. thanks!