~dr|z3d
@RN
@StormyCloud
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%Liorar
%acetone
%mareki2p
+H20
+Onn4l7h
+Onn4|7h
+Over
+Sh0ck
+leopold_
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
+xHarr
Arch2
BubbRubb
Dann
DeltaOreo
Guest99
Irc2PGuest18689
Irc2PGuest57895
Irc2PGuest74254
Irc2PGuest90101
Irc2PGuest95708
Meow
Stormycl1
T3s|4__
ac9f_
anontor
cumlord
duck
floatyfloatilla
gelleger1
halloy13412
mahlay
makoto
n1_
nZDoYBkF_
nilbog-
ntty
onon_
r00tobo[2]
simprelay
solidx66_
thetia
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 :)