~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
+FreefallHeavens
+Leopold
+Xeha
+ardu
+bak83
+hk
+onon_
+qend-irc2p
+r00tobo_BNC
+uop23ip
AHON1
Arch
BubbRubb1
Dann
DeltaOreo
HowardPlayzOfAdmin1
Irc2PGuest31296
Irc2PGuest35799
Irc2PGuest55055
Irc2PGuest69335
Irc2PGuest87322
Irc2PGuest99002
Meow
Onn4l7h
Onn4|7h
SigSegv
T3s|4__
anontor
boonst
eyedeekay
maylay
not_bob_afk
pisslord
poriori_
shiver_
simprelay
solidx66
thetia
u5657
usr002
weko_
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 :)