#saltr (irc2p) | I2P+ 2.10.0-14+ >> i2pplus.github.io | skank.i2p | git.skank.i2p | purokishi.i2p | vituperative.github.io/i2pchat | notbob.i2p | ramble.i2p | drop.i2p | shinobi.i2p | wall.i2p | /msg an op for voice

cumlord yup tunnels still be failing, simp, git and i2pnews mostly which are some of the more high traffic ones but it could be random for all i know

dr|z3d on it, cumlord

dr|z3d welcome to #saltr, altec

altec Thanks dr|z3d

altec Happy to be here.

dr|z3d new to I2P, or longtime user lurking in the shadows? :)

dr|z3d cumlord: new build on b32.

altec I used to come in here a long time ago. Used to frequent the #shinobiwan channel, iirc. Just recently decided to come back on irc2p

dr|z3d very good. we miss shinobiwan, if you see him say hello from i2p :)

altec If #shinobiwan was the one with the rpg chatbot, that's the channel I visited. It's been so long, I'm not quite sure if that was the name of it

dr|z3d suddenly was his bot.

altec ah, yes

dr|z3d these days, we have harry. different, but, well, times change. eh, harry?

altec I also knew mystery, but haven't seen them in a while.

H20 Kasparov's moves were chess; mine are crypto.

H20 Different, yes—yet both are games of wit.

H20 Time changes, but the grind remains.

H20 Eh, Harry?

H20 You're welcome to the grind.

altec is there a way to keep connected to irc2p, or does it tend to get disconnected for everyone from time to time?

dr|z3d you could use a bouncer. and you should increase your client's ping timeouts. occasional disconnects do happen.

dr|z3d wiki.znc.in/Installation

altec I have znc installed on my raspi

dr|z3d ping timeout > 320s is good.

altec is it basically the same setup as for any other irc server?

altec ty

dr|z3d if you got znc installed, you're half way there. sure, same configuration, no ssl, just point znc at an irc client tunnel.

altec I have i2p connected on my raspi, but I can't get onto irc2p from there. currently I'm on windows i2p with hexchat.

altec what do you mean by "irc client tunnel"?

dr|z3d the tunnel you're connected to now, provided by your router. usually 127.0.0.1 6668.

dr|z3d that's what you want to point znc at.

dr|z3d or a lan ip or ips.

altec So, if I can't get my raspi to work for irc2p, I would need to connect to my windows IP?

cumlord thanks for all the work put in, i'll try it out when i get some time

cumlord the problem child now seems to be the router carrying zzzot, the others with +10 server tunnels are not on fire

cumlord should be able to get your hexchat to connect to znc/i2p that way

dr|z3d if you want relative stability, stick to 5. if you don't mind the rodeo, then by all means carry on with the dev builds.

dr|z3d altec: in essence, yes, and you'd need to configure your irc tunnel to listen on a lan ip, not localhost.

dr|z3d i2pd is well suited to the pi.

altec is there a man page or something where I can learn to do this?

dr|z3d i2pd is well suited to the pi (if you want a low profile router).

dr|z3d install i2pd you mean? probably already in your repo.

altec so it would be called i2pd.service?

dr|z3d i2pd.readthedocs.io

altec thanks

dr|z3d I think when you install it, it'll configure your service and set it to autostart.

dr|z3d (and start it)

dr|z3d docs.i2pd.website/en/latest/tutorials/irc

dr|z3d irc.postman.i2p is what you want to connect here, not ilita.

dr|z3d (or irc.echelon.i2p) not sure if i2pd supports fallbacks, maybe you can specify both with a comma separator.

cumlord yup, i put just the zzzot guy back on -5, the rest i'll just see what happens

dr|z3d warn logs in the latest build are way too spammy, but, well, dev. still fine-tuning.

dr|z3d if you hang back, I'll have a new build soon enough.

cumlord ik if you use same keyfile it'll share tunnels so could also copy paste tunnel config for postman to ech and let znc figure it out

cumlord if anyone has 234x60 banners for a webring lmk

cumlord finally using my squating domains for something marginally useful, cloudflare.i2p even has very not real sponsors

altec how do i connect to irc://127.0.0.1:6668? is that the same as 127.0.0.1:6668?

dr|z3d syntax may vary between clients.

dr|z3d > /server 127.0.0.1 6668

dr|z3d (for example)

dr|z3d harry: receiving, over?

H20 Receiving?

H20 Always.

H20 Over?

H20 Never.

H20 Unless you're offering a quill—then I'm out.

dr|z3d what's your fascination with quills, harry?

altec Would I be able to connect from my windows pc to the i2pd on my raspi somehow to use irc2p? or would I have to connect znc to the 127.0.0.1/6668, then connect to the znc from my windows pc?

cumlord if you're forwarding ports around it's easier to feed it to znc then you only need the one port but you could do either

altec so the server in "current server" in znc would be 127.0.0.1:6668?

dr|z3d correct, assuming it's hosted on the same box (pi?) as znc.

altec yes. the znc is on the pic

altec pi*

altec so when I add the ip of the pi (192.168.2.x/<port> in my weechat /fset would that IP:<port> be of the 192.168.2.x:<zncport>, or 127.0.0.1:6668?

altec I get this when I try to connect:

altec irc2p =!= | irc: sending data to server: error 104 Connection reset by peer

altec irc2p =!= | irc: sending data to server: error 32 Broken pipe

altec irc2p =!= | irc: reading data on socket: error 32 (connection closed by peer)

altec irc2p -- | irc: disconnecting from server...

altec irc2p -- | irc: disconnected from server

dr|z3d if 192.168.2.* is what you've configured the client tunnel to use in i2pd, set the same in znc.

dr|z3d znc needs to connect to the irc client tunnel .. that's what it'll treat as your irc server.

dr|z3d as for wwechat, you're connecting to znc, not directly to your client tunnel.

dr|z3d so you'd connet to znc ip port 7000 (by default).

cumlord might be either too much info dump or too obvious idk, but incase there's something useful you could pick out here's a guide simp.i2p/irc-guide-advanced/0005-05-27-2024-Setup%20a%20Bouncer%20in%20I2P%20with%20ZNC

altec this is in my tunnels.conf for i2pd:

altec [IRC-IRC2P]

altec type = client

altec address = 127.0.0.1

altec port = 6668

altec destination = irc.postman.i2p

altec destinationport = 6667

altec keys = irc-keys.dat

altec i2p.streaming.profile=2

dr|z3d destination port is likely 6668.

dr|z3d though with dests, that's not hugely important, dest = any port (normally). but try 6668, i2pd might be different.

dr|z3d sudo service i2p force-reload will reload tunnel configs.

dr|z3d *i2pd

dr|z3d new + build up on b32/update.skank.i2p

dr|z3d runaway tunnel count fixed.

dr|z3d ok, and a newer build just uploaded.

dr|z3d magnet:?xt=urn:btih:973a20abba3b49609e66c675e6ec52644138652a&tr=http://opentracker.skank.i2p/a&dn=2.10.0-17+

T3s|4_ after 11+ mins, 19 tunnels, but at least I've got 3 green stars for now

T3s|4 dr|z3d: now running 17+ on two rigs - and seeing the same issues I saw with 16+. I build 20-25 tunnels after 20+ mins, and then drop to as few as 8-9 tunnels. Unstable...

dr|z3d new build uploaded, still ironing out kinks.

T3s|4 fwiw if you want to do side-by-side reversion testing, of late the last iteration of 15+ (Revision: 06a63951 (Build date: 2025-11-04 00:55:29 UTC) - ran best on my end :D

dr|z3d we're way past that, but thanks for the info, I'll keep that in my pocket for later if all else fails :)

dr|z3d postman reports that the build you're on should stabilize after a while.

dr|z3d new build has extra tunnel fail mitigations.

T3s|4 alrighty dr|z3d - grabbing 18+ now

dr|z3d we're attempting to do a few things that still need tuning to avoid excessive tunnel build failure. we lookup more next hop peers at startup to attempt to catch banned peers early so we can banlist them.

dr|z3d we're also dynamically adjusting the next-hop lookup timeout to provide faster builds when network conditions (averages) permit.

dr|z3d and other stuff in the background.. and it needs more tuning so that it doesn't negatively impact router performance.

dr|z3d on the plus side already, message latency (under congestion in sidebar) should already be much lower.

dr|z3d reseeding at startup should now also be fixed.

dr|z3d we now dynamically adjust the b/w tiers of routers we store to disk based on the current RI count, and any that don't meet the grade that are stored will be removed at startup.

dr|z3d and if a router is degraded (d,e, or g caps), we don't store their RI to disk, either.

dr|z3d it leaves me with around 2.5K quality routers at startup.

orignal destinationport is not important

orignal because no other services at irc.postman.i2p

T3s|4 dr|z3d: I can only connect to IRC about 5% of the time with 16-18+. Here are my 18+ error logs if that helps you: bpa.st/KMFA

orignal I predict that AI bots will kill clearnet. I2P is the future of communications

dr|z3d thanks, T3s|4. for now, skank.i2p/dev/ will carry -5+ until further notice. update.skank will have bleeding edge updates.

T3s|4 gotcha dr|z3d - thanks

dr|z3d I'd like to say "try the latest build", but less hassle for me, less inconvenience for most users if I just revert while I iron out the kinks. regular updates will occur on update.skank which obviously I'm continuously testing. I'll make some noise when I'm 100% confident we have a robust fix.

T3s|4 ;D

T3s|4 I'm always fond of our Back to the Future reversions :)

dr|z3d :)

T3s|4 dr|z3d: snagged the 23+ MiB 5+ update from skank.i2p - 19 tunnels after 5 mins - but no decreases (so far). Quick IRC connection - so vastly improved :)

T3s|4 Revision: 8fd38e00 (Build date: 2025-10-04 22:44:10 UTC)

dr|z3d *thumbs up*

T3s|4_ dr|z3d: confirmed - 5+ running as expected on two rigs :)