~dr|z3d
@RN
@RN_
@Stormycloud
@T3s|4_
@orignal
@postman
@zzz
%ardu
%cumlord
%snex
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Rogueone
+Xeha
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
+wew
AHOH2
Arch2
BubbRubb
C341
Danny
DeltaOreo
DirtyHarry
FreeB
Irc2PGuest24679
Irc2PGuest4053
Irc2PGuest4761
Irc2PGuest54725
Liorar_
Meow
T3s|4
acetone_
carried6590
halloy13412
mareki2p_
maylay
moe_
not_bob_afk
pisslord
poriori_
r00tobo[2]
shaye
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 :)