~dr|z3d
@RN
@RN_
@Stormycloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%ardu
%cumlord
%mareki2p
%snex
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Xeha
+bak83_
+hk
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
+weko
+wew
AHON1
Arch
BubbRubb
Danny
DeltaOreo
FreeB
Irc2PGuest57893
Irc2PGuest68785
Irc2PGuest71171
Irc2PGuest85022
Meow
WaAmH_
anontor2
idontpee
maylay
moe
not_bob_afk
poriori_
r00tobo[2]
rascal
shaye
shiver_1
simprelay
solidx66
thetia
u5657
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 :)