@RN_
@StormyCloud
@T3s|4_
@orignal
@postman
@zzz
%Liorar
%mareki2p
%snex
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+leopold_
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
AlV5tGf7
Arch
Danny
Holmes
Irc2PGuest17692
Irc2PGuest28384
Irc2PGuest57339
Meow
OfficialCIA
Over1
U1F642
acetone_
ahiru
cims
floatyfloatilla
mahlay
makoto
n2_
nilbog
not_bob_afk
pory
r00tobo[2]
rednode
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 :)