~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
%snex
+FreefallHeavens
+Leopold
+Xeha
+ardu
+bak83
+hk
+mareki2p
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+segfault
+thirtyseven
+uop23ip
Arch
BubbRubb1
Danny
DeltaOreo
HowardPlayzOfAdmin
Irc2PGuest37947
Irc2PGuest58427
Irc2PGuest63042
Meow
Onn4l7h
Onn4|7h
SigSegv
anontor
boonst
duck
maylay
not_human_
pisslord
r3med1tz-
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 :)