~dr|z3d
@RN
@RN_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%ardu
%cumlord
%mareki2p
+FreefallHeavens
+HowardPlayzOfAdmin
+Onn4l7h
+Sh0ck
+Xeha
+bak83_
+leopold_
+marek22k
+onon_
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+romer
+uop23ip
+waffles
+xHarr
Arch
BubbRubb
Danny
DeltaOreo
Irc2PGuest10122
Irc2PGuest93285
Maylay
Meow
Over1
Stormycloud_
T3s|4__
T3s|4___
ac9f
acetone__
anontor
coolbuddy799
duck
halloy13412
makoto
nZDoYBkF
nilbog
not_bob_afk
pory
r00tobo[2]
shiver_
simprelay
solidx66
thetia
u5657
vivid_reader56
woodwose
zer0bitz
T3s|4
o/ dr|z3d - it was a real PITA to re-install protonVPN on Arch (many missing dependencies) from their AUR, but I did transition to an X router. Still horrible connectivity problems between that VPN and when running tor as a concurrent service. If you have ideas. please let me know
mesh
has anybody else seen their router performance (in terms of bandwidth in/out) go significantly down in 2.2.0?
mesh
I wonder if something is wrong or if this is part of the design of 2.2.0... to better distribute the load across the routers in the network
mesh
uop23ip_: you also experienced a signifciant decrease in bandwidth usage when you upgraded?
mesh
uop23ip_: I'm having the same problem. I actually just mentioned it right before you brought it up on #i2p. When I upgraded to 2.2.0 I saw a significant (70%) reduction in bandwidth usage.
mesh
It's unexpected. But some people have suggested this is the purpose of the 2.2.0 upgrade... to better spread the load across routers
mesh
dragonheart: did anybody figure it out?