~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4_
@eyedeekay
@postman
@zzz
%Liorar
%ardu
%cumlord
%mareki2p
+FreefallHeavens
+HowardPlayzOfAdmin
+Onn4l7h
+Onn4|7h
+Over
+Rogueone
+Sh0ck
+Xeha
+hk
+onon_
+profetikla
+qend-irc2p
+r00tobo
+romer
+uop23ip
+waffles
+wew
+xHarr
Arch
BravoOreo
BubbRubb
Danny
FreeB
Irc2PGuest32761
Irc2PGuest59861
Irc2PGuest77400
Meow
T3s|4__
Xel-Ruun
acetone_
aisle
anontor2
maylay
moe_
nilbog
not_bob_afk
orignal
pisslord
poriori_
pory
r00tobo[2]
shiver_
simprelay
solidx66
thetia
weko_
woodwose
zer0bitz
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 :)