@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+T3s|4
+acetone
+cims
+eche|off
+hagen
+mareki2p
+mesh
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+red
+snex
+wodencafe
Arch
Danny
Holmes
Irc2PGuest28384
Irc2PGuest84270
Irc2PGuest92627
NiceBoat_
OfficialCIA_
Onn4l7h
Onn4|7h
Over1
SilentWave
Sleepy
T3s|4_
U1F642
Wikk_0
Zapek
aargh4
ac9f
ahiru
anontor
dr4wd3
duanin2
eyedeekay_
eyedeekay_bnc
ice_juice
leopold
mahlay
makoto
n2
not_bob_afk2
poriori
profetikla
r00tobo
rapidash
test3847473
thetia
uop23ip
urist_
utp
vivid_reader56
x74a6
zelgomer
orignal
I saw incloming SSU2 session with 4 at nKkG
orignal
no issues
zzz
thats an i2pd router
orignal
yes, but got incoming connection from soemone
zzz
yup
orignal
nKkG s mine
orignal
*is
zzz
eyedeekay, a lot of connection resets today from git.idk.i2p, sometimes resolves quickly, sometimes not
zzz
adding still more logging for outgoing PQ
zzz
eyedeekay, skimming through your new ssu2 code...
zzz
I assume it's not working yet?
zzz
I see a couple things, holler
orignal
go router that was supposed to release in February?
zzz
please be supportive of the go router development. Don't take any schedule seriously. I doubt he promised perfection by February
orignal
I remember you mentioned this zt zzz.i2p
zzz
ok, but I'm not managing the go project, and don't have a lot of insights. I'm sure eyedeekay can answer any questions you have
orignal
my question is where did February come from?
zzz
no idea. point me to my post and I might be able to answer. What's your concern? Are you in a hurry to use it?
orignal
no concern
orignal
your post was about an outcome of some conference where people were enthusiastic about go and rust routers
orignal
may it was not at zzz.i2p, maybe it was a link here
zzz
may have been reporting what eyedeekay told me, I wasn't there
zzz
it would have been at CCC at Christmas
nyaa2pguy
was video of the talk ever uploaded?
eyedeekay
zzz yeah it doesn't work yet I'm just getting it wired in and finding the bugs. I actually did most of it months ago and by the time I merged it I knew I had made mistakes but it was easier to work on like this. I did release what I said I hoped I would release in February, which was the parts between go-i2p and onramp, and I didn't promise anything.
eyedeekay
Specifically IIRC I targeted the release the "lib/embedded" which I did
zzz
ok heres a couple comments on the ssu2 code for your notes when you get to it
zzz
- ack handler is wildly off, the acnt field is the count of acks, not a RTT
zzz
- in header protection, the IV is of course 12 bytes, not 11 with one padding, the KDF in the spec makes it clear, perhaps you were confused about [x:y] notation inclusive/exclusive
eyedeekay
I probably did that in frustration
eyedeekay
But yeah
eyedeekay
I remember around there being confused
eyedeekay
So that makes sens
eyedeekay
*sense
eyedeekay
Should have marked it TODO/BUG
zzz
- seems a little odd to have the whole transport in go-noise, strictly speaking everything after the handshake (after split()) isn't noise at all
eyedeekay
Yeah that's definitely a known on my part, I'm trying to figure out exactly where each part should be scoped
zzz
and even the handshake is transport-specific stuff in it
zzz
you said go-noise was just an overlay on the basic noise lib to make mods along the way but now it's basically half the router code
zzz
- suggest you definitely go in and disable the subprotocols relay, peer test, and connection migration until you get the main part working. it's bananas to code it all up at once
eyedeekay
yeah go-noise is suffering in that way, my idea which I spent so much time on was to narrowly enable the noise modifications in go-noise but I've struggled to maintain those architectural decisions in practice
zzz
may have been too ambitious, not sure
eyedeekay
That's sort of how I ended up dropping too-much-ssu2 all at once into go-noise, I'm sort of in the process of disentangling it
zzz
still think you might benefit doing streaming before ssu2 but just a guess
eyedeekay
Well it's the scoping thing actually that's bugging me, I've had all this kinda half-baked but existent ssu2 work on a couple branches for a while but I know it's a mess compared to what I'd like it to be. So my thinking was do the work to at least be able to merge it, hook it up, and disable it at runtime so I don't have to resovle a gazillion merge conflicts later
zzz
sounds good. having a plan will help you and will attract contributors
zzz
as will having WIP stuff checked in instead of just sitting on your computer
eyedeekay
I've been really drilling down on the package scope thing since February, I'm down to only one or two scope violations per repo except in go-noise which is unfortunately pretty blurry around the edges right now
eyedeekay
Yeah that was my thinking, merge my WIP before it becomes stale and dies
zzz
yeah eyedeekay suggest you draw yourself a dependency DAG for various end-products you have in mind, and eyebell them to see if they make sense
orignal
what's the goal of i2p-go router?
orignal
since go seems less and less popular vs. few yeras ago
zzz
eyedeekay, on another topic, no luck on pushing itoopie and newsxml to GH? also need a push for i2p.i2p; I'm trying to iterate to make weblate happy
eyedeekay
Darn I guess it didn't work, I'll set a cron job to sync them manually until I can fix them properly
zzz
thx
orignal
zzz, any locuk with connection to 2RRY?
zzz
let's look, I added some logging this morning
orignal
I don't see any connectivity problem from i2pd
orignal
that's why it's starnge
zzz
yeah I've had 4 successful since this morning, from two different routers
zzz
03/20 16:10:04.786 ERROR [ handler 1/1] outer.transport.udp.PeerState2: Outgoing version 4 ACK 0 FROM [2606:65c0:10:94:9539:125e:68d:908e]:15123 2RRYXk OB4 recvAge: 152ms sendAge: 56y sendAttemptAge: 152ms sendACKAge: 152ms lifetime: 152ms RTT: 156 RTTdev: 78 RTO: 1000 MTU: 1280 LMTU: 1500 cwin: 3840 acwin: 3660 SST: 524288 FRTX? false consecFail: 0 msgs rcvd: 0 msgs sent: 1 pkts rcvd OK/Dup: 0/0 pkts sent OK/Dup:
zzz
1/0 IBM: 0 OBQ: 0 OBL: 1
orignal
let's inverstigate later
orignal
16:10:04@649/warn - SSU2: SessionRequest AEAD verification failed
orignal
same story
zzz
my log was europe time, not UTC or EDT. but something does seem a little fishy, will take some time
zzz
log above was of success - I got thru the handshake and got a ACK 0
orignal
got it
zzz
ok, not fishy, confusing logging had me confused
zzz
going to update my logging one.more.time to be sure