~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@orignal
@postman
@zzz
%Liorar
%acetone
%ardu
%cumlord
+FreefallHeavens
+HowardPlayzOfAdmin
+Onn4l7h
+Sh0ck
+Xeha
+bak83
+profetikla
+qend-irc2p
+r00tobo
+romer
+uop23ip
+wew
+xHarr
AHON1
Arch
BravoOreo
BubbRubb1
C341
Danny
Irc2PGuest10122
Irc2PGuest27560
Irc2PGuest32123
Irc2PGuest5836
Irc2PGuest61213
Irc2PGuest82196
Irc2PGuest8647
Irc2PGuest9389
Meow
Over1
SigSegv
anontor
bpb
makoto
mareki2p_
maylay
nZDoYBkF
nilbog-
poriori_
pory
shiver_
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 :)