~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
%mareki2p
+BeepyBee
+FreefallHeavens
+H20
+Onn4l7h
+Sh0ck
+bak83_
+leopold
+poriori
+r00tobo_BNC
+uop23ip
+xHarr
Arch
BubbRubb
Danny
DeltaOreo
Irc2PGuest16752
Irc2PGuest61924
Maylay
Meow
ac9f_
anontor
duck
halloy13412
john231
makoto
nZDoYBkF
nilbog
not_bob_afk
ntty
profetik1
r00tobo[2]
shiver_
simprelay
solidx66
thetia
u5657
vivid_reader56
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 :)