~dr|z3d
@RN_
@StormyCloud
@T3s|4
@not_bob
@orignal
@postman
@zzz
%RTP
%cumlord
%snex
+BeepyBee
+FreefallHeavens
+H20
+Onn4l7h
+Onn4|7h
+Over
+dollarthief
+leopold_
+onon_
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
+waffles
Arch
BubbRubb
Danny
DeltaOreo
Guest99
Irc2PGuest21940
Irc2PGuest3188
Irc2PGuest41816
Irc2PGuest49393
Irc2PGuest6140
Irc2PGuest74254
Meow
Stormycloud_
ac9f_
acetone_
anontor
floatyfloatilla
gellegery
halloy13412
mahlay
makoto
mareki2p_
n1
nZDoYBkF
nilbog
ntty
poriori_
r00tobo[2]
shiver_
simprelay
solidx66_
thetia
u5657
vivid_reader56
wtfman
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 :)