@RN_
@StormyCloud
@T3s|4_
@orignal
@postman
@zzz
+FreefallHeavens
+Gully
+NiceBoat
+Onn4l7h
+Onn4|7h
+altec
+leopold
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+quack
+r00tobo
+uop23ip
+waffles_
Arch
Danny
Irc2PGuest3774
Irc2PGuest56290
Irc2PGuest71529
Irc2PGuest77921
Liorar
MatrixBot
Meow
Over
T3s|4
U1F642
WaAmH
acetone_
ahiru_
anontor2
cims
floatyfloatilla
mahlay
makoto
n2
nZDoYBkF_
nilbog
not_bob_afk
o3d3_
r00tobo[2]
rednode
solidx66
stormycloud[m]
vivid_reader56
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 :)