~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%cumlord
+Irc2PGuest48514
+Leopold
+Xeha
+ardu
+hk
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+segfault
+uop23ip
AHON1
Arch
BubbRubb
Danny
DeltaOreo
FreeB
Irc2PGuest2799
Irc2PGuest39954
Irc2PGuest57304
Irc2PGuest63604
Irc2PGuest80556
Irc2PGuest86877
Meow
Onn4l7h
Onn4|7h
acetone_
altonen
boonst
duck
maylay
not_human_
pisslord
shiver_
simprelay
solidx66_
thetia
u5657_
weko_
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 :)