~dr|z3d
@RN
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
%snex
+FreefallHeavens_
+Xeha
+ardu
+hk
+mareki2p
+onon_
+r00tobo
+radakayot
+uop23ip
AHON1
Arch
Danny
DeltaOreo
Irc2PGuest28644
Irc2PGuest4450
Irc2PGuest70966
Irc2PGuest87589
Meow
Onn4l7h
Onn4|7h
SigSegv
altonen
derivative
maylay
not_bob_afk
plap
poriori_
profetik1
qend-irc2p
shiver_
simprelay
solidx66
thetia
u5657
usr001
weko_
woodwose
zer0bitz
dr|z3d
do you have a config option to only use routers with in specified bandwidth tiers, orignal?
dr|z3d
router.excludePeerCaps={netDBcaps}
dr|z3d
This setting determines which peer capabilities will not be used to build your router's tunnels. e.g. router.excludePeerCaps=LMN
mareki2p
Hi, I have another problem... I just updated I2P (Java 24, Windows) from 2.8 to 2.8.1. It is running for one hour already. And I added few info hashes into the built-in i2psnark. I get weird messages from it: Torrent file moved from C:\xxx.torrent to C:\xxx.torrent.BAD what is the reason for flagging torrent as bad?
dr|z3d
try turning on snark debug logging, that may tell you more.
mareki2p
How do I do that?
dr|z3d
> /configlogging
RN
mareki2p_, the message is actually a misfire
RN
it is sayint the torrent is bad, but it really wants to say you are bad.
RN
*** spanks mareki2p_ ***
RN
eat your veg!
RN
*** giggles ***
mareki2p
hmmm )-:
RN
did you make any progress with snark?
RN
*** sends mareki2p some flowers and chocolates ***
mareki2p
Enabled logging and copy & pasted all the torrents from other snark (standalone) that is connected to i2pd.
orignal
No I don't
orignal
and I told you why
dr|z3d
well, that's how you ensure you don't have slow routers in your client tunnels.
orignal
I take RTT from tunnel test
orignal
and if it's more than 250 ms per hop I exclude such tunnel
dr|z3d
that's not going to weed out slow (b/w) routers.
orignal
monkeys publish X for slow routers. so?
orignal
and for client tunnels I picck only O, p and X
orignal
uunless i2p.streaming.profile=2
dr|z3d
so you optionally exclude by b/w tier, and since you're already testing latency, test b/w at the same time.
orignal
not the same
orignal
in my case it's based on real situation rather than published
dr|z3d
ok, so you ARE excluding by tier. that's what I asked.
dr|z3d
in which case, you're performing some b/w tests as well?
orignal
tunnel test
orignal
you send a message with timestamp and get it back
dr|z3d
right, so that's not bandwidth, that's latency.
orignal
you never know real bandidth in advance
dr|z3d
and you don't really care latency with snark, you care about bandwidth.
orignal
because monkeys set X
dr|z3d
*about
dr|z3d
I guess that's where profiling comes in handy.
orignal
I don't have profiling for bandwidth yet
dr|z3d
call yourself a coder?
dr|z3d
*** pokes orignal in the ribs. ***