@RN_
@orignal
@postman
%Liorar
+Onn4l7h
+Over
+marek22k
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
Irc2PGuest21028
Irc2PGuest30010
Teeed
acetone_
f00b4r_
leopold
makoto
nZDoYBkF
not_bob_afk
o3d3_
r00tobo[2]
solidx66
waffles
lol rtp tech tips took my suggestion and made a irc2p video
waffles
all the cool kids r in #righttoprivacy
snex
harry movie trivia starts in 13 minutes in #trivia. winner gets 0.01 monero. i dont think youll even show up
dr|z3d
unfortunately harry was busy doing other things, snex
dr|z3d
RTP!
dr|z3d
sort your system clock out!
dr|z3d
also, address helpers in your addressbook are not for your own use.. zero need for those if you're already looking at the address in your book...
dr|z3d
address helper links there are for sharing with other people.
dr|z3d
re clock, if the sidebar clock skew is printed in red, your clock needs syncing pronto. if not, it may impede the operation of your router, cause slow access to eepsites etc.
RTP
haha I will look at that - thanks must be affecting something - wasn't sure if it was my other machine or not... but will be checking that to disable the service on blog
RTP
I should have chance to disable that on blog server tomorrow - wrapping up some short deadline stuff atm
RTP
THanks for reminder
dr|z3d
re host checker scheduling, that's configurable from the configuration page, as well as concurrent tests, as indicated in options section at the bottom.
RTP
I kind of realized that after but talking off the cuff just end up mispeaking in moments lol
dr|z3d
one thing you missed in your video, possibly because it wasn't in scope, is the new blacklist feature.
dr|z3d
np.
dr|z3d
the blacklist allows you to add hosts to a persistent blacklist, which will prevent 3 things:
dr|z3d
1. they won't appear in the addressbook lists.
dr|z3d
2. they won't be tested by host checker.
dr|z3d
3. if you attempt to visit them via the http proxy, they'll be blocked.
dr|z3d
no biggie. glad you're enjoying the feature. notbob does in fact allow category filters, when his css decides to load correctly. :)
dr|z3d
latest new is the tunnel test status indicators on /tunnels
dr|z3d
tunnels in a pool are periodically tested to ensure they're correctly forwarding traffic.
dr|z3d
now you get to see in realtime how the tests are performing.
dr|z3d
after 2 consecutive test fails, the tunnel will be removed from the pool and replaced.
dr|z3d
you'll see that happening in the UI when it does.
RTP
I'm going to have to check that out - that video was a though on what can help more people use i2p more often. Addressbook is very handy especially with the site status green / red in it. Cool stuff!
dr|z3d
expect a fair amount of churn at router startup.. things stabilize after a while.
RTP
I think users just have trouble finding the sites and thought addressbook is perfect with the status now people can just click what type of sites they want
dr|z3d
right. you get it. instead of just a dump of all known sites, we're trying to do something useful there.
RTP
Definitely SUPER useful IMHO. Great idea integrating notbob stats. :)
dr|z3d
notbob provides the categories, we source our own stats :)
RTP
I can share all the types of sites I want to see, but never will be everyone's cup of tea. Addressbook is very handy and TBH I hadn't played much with it until recently.
RTP
ahh, kewl
dr|z3d
you may see pings indicated in the sidebar under service tunnels.. that's your router testing destinations.
RTP
I noticed that recently! Cool thanks for the info, hadn't explored the links on it yet.
dr|z3d
first we request a leaseset. if there's none returned from a floodfill, no point continuing with the tests. destination is offline..
dr|z3d
if we get a leaseset, then we ping the destination.. if it responds, we're good, site's up.
dr|z3d
if not, we then test with eephead. only if both ping and eephead fail (or no leaseset) do we mark as down.
dr|z3d
if your router's under load and fails to build ping tunnels, we fallback to eephead. if that fails, we don't mark as down because local ping tunnels failed.. we'll test again.
RTP
aha. Makes sense.
dr|z3d
(in the next scheduled cycle)
RTP
I definitely want to make my blog as reliable as possible - so will be turning off the kicksecure related service that messes with time - and will be mentioning that for others as it's not something optimal, and can at least be disabled.
dr|z3d
you could start with some simple css tweaks to remove the discuss links.
dr|z3d
not entirely related, but still.. let me see what you need, 1 moment.
dr|z3d
Blinded message
dr|z3d
(which I can't right now)
dr|z3d
if you're running on Linux, you want to cron timesync frequently so your clock stays synced.
dr|z3d
sudo crontab -e
dr|z3d
*/15 * * * * ntpdate pool.ntp.org
RTP
cool thanks going to add to my notes todo for when I get chance tomorrow
RTP
copying now
dr|z3d
ok, new + build up, with latest (Feb) GeoIP Db.
RTP-bbl
I'm definitely going to be fixing that time thing soon as I get to server tomorrow though - had trouble updating blog and thought it might have been related to something else, but now it's quite apparent!
dr|z3d
yeah, you'll likely fine routers just ignore you if your clock's fucked.
RTP
trying to figure out what is going on with my blog. Turned off / removed the randomization (it was a 180sec give or take, not large amount), turned that off and enabled timesyncd. Everything looks good on the blog server (loads locally there fine b32 which I imagine is local connect), it now showing at 19% tunnel success. Wondering as nothing changed but seemed to just drop off the stats all today :-/ looking into
RTP
it, trying things.
dr|z3d
what build you running, RTP? also, anything in the logs?
dr|z3d
and, just an importantly, did you fix your clock skew?
dr|z3d
if you synced while your router was running, try restarting the router.
dr|z3d
ordinarily it should fixup, but 19% success rate sounds like your router clock is still whack.
dr|z3d
> what build you running, RTP? also, anything in the logs?
dr|z3d
> and, just an importantly, did you fix your clock skew?
dr|z3d
> if you synced while your router was running, try restarting the router.
dr|z3d
> ordinarily it should fixup, but 19% success rate sounds like your router clock is still whack.
dr|z3d
new + dev build uploaded, various job queue related fixed.
dr|z3d
*fixes
RTP
blog currently running I2P+ 2.10.0.28+ steady 1ms skew
RTP
3ms but usually 1ms now
RTP
I'm going to keep trying some things
RTP
as random test changed to 2.10.0-26+ just to see what would happen, and now my blog is back up. Could be a completely random coincidence.
RTP
but up to 38% tunnel creation now