@orignal
@postman
@zzz
%Liorar
+Onn4l7h
+Over
+f00b4r
+leopold
+marek22k
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
Arch
BeepyBee
Irc2PGuest30010
Irc2PGuest51117
Irc2PGuest65656
Irc2PGuest74235
MatrixBot
Meow
RN_
T3s|4
T3s|4_
Teeed
acetone_
ahiru
anontor
cims
dr|z3d
eyedeekay
mahlay
makoto
n2_
nZDoYBkF
nilbog
noidea
not_bob_afk
o3d3_
r00tobo[2]
solidx66
stormycloud[m]
user_
T3s|4
dr|z3d: thanks. Never thought to look at my weechat settings, because I also use weechat to connect to a 'torified' IRC server using a separate instance of weechat. That torified IRC connection connects within 3 seconds, max, everytime. That is why I assumed my ^connection issue lay with the i2prouter settings, not with weechat. In any event, I can tweak some weechat
T3s|4
'autoreconnect' settings to see if they have any impact
T3s|4
that was a quick bounce-back on my end :D I'll keep an eye on it dr|z3d :)