@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+RN_
+dr|z3d
+hk
+orignal
+postman
+weko
+wodencafe
An0nm0n
Arch
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest21881
Irc2PGuest5995
Irc2PGuest88897
Irc2PGuest95630
Nausicaa
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
Soni
T3s|4_
T3s|4__
aargh2
acetone_
anon2
b3t4f4c3
bak83
boonst
cancername
cumlord
dr4wd3_
eyedeekay_bnc
hagen_
khb_
not_bob_afk
plap
poriori
profetikla
r3med1tz-
rapidash
shiver_
solidx66
u5657
uop23ip
w8rabbit
x74a6
weko
Network under "attack" (or very big usage). I have very big transit speed with some big transit tunnels (50-300mb), sometimes my internet connection on full loading.
dr|z3d
weko: what router version are you running?
weko
I use i2pd compiled from git
dr|z3d
ok, so you won't have the java mitigations that go some way to fixing the excessive b/w and transit tunnel requests.
dr|z3d
in any event, we've been observing some high traffic / part tunnel requests lately. they seem to spike. hard to say what's causing that.. could be a poorly configured / old retroshare using BOB and not SAM. or something more malicious.
weko
Loading have "waves". For now, 500kB/s, but 5 minutes ago were 3000kB/s
dr|z3d
yeah, that'll be the spikes. I've seen up to 42MB/s
weko
It is my opinion
weko
Average loading transit 6-40 Mbit/s
dr|z3d
you can get some idea of the behavior over a few routers here: stormycloud.org/i2p-stats
dr|z3d
those routers now have mitigations.
weko
My opinion what this is attack, because I have 50-30 mb transit tunnels and this is main loading
weko
50-300*
dr|z3d
it's possible, but it's equally possible we've got a couple of retroshare/BOB users on the network causing mayhem
weko
Maybe but this is very big coincidence
weko
What many users have old routers at one time
dr|z3d
not routers, retroshare.
dr|z3d
retroshare has a bug with older versions using SAM that causes a huge number of tunnel requests, presumably one per file, until ram and swap is exhausted on the host system.
dr|z3d
*using BOB
weko
Oh, RetroShare
dr|z3d
java i2p clamps the max number of tunnel requests which largely fixes the issue.
dr|z3d
and it also has router bans for persistent offenders.
weko
But problem in large traffic on tunnels, not the number of tunnels request
weko
3.5 Mbit/s for some tunnels
weko
And this just not one tunnel
dr|z3d
weko: feel free to /join #ls and tell orignal :)
weko
I talk with orignal already many times )
dr|z3d
I don't know whether a cap on b/w per tunnel is the next thing to consider.
weko
He also have many traffic, and R4SAS have
dr|z3d
and yeah, I've seen the same re tunnel usage. up to 2MB/s per tunnel.