~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
+DirtyHarry
+FreefallHeavens
+Xeha
+ardu
+bak83_
+mareki2p
+poriori
+profetikla
+r00tobo
+radakayot
+segfault
+uop23ip
AHON1
Arch2
Danny
DeltaOreo
FreeB
Irc2PGuest53192
Irc2PGuest59581
Irc2PGuest64993
Irc2PGuest70134
Irc2PGuest96449
Meow
Onn4l7h
Onn4|7h
boonst
carried6590
duck
maylay
not_bob_afk
onon_1
phobos
pisslord
qend-irc2p
shiver_1
simprelay
solidx66
thetia
u5657
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 :)