@eyedeekay
+R4SAS
+RN
+RN_
+T3s|4
+Xeha
+orignal
FreeRider
Irc2PGuest15271
Onn4l7h
Onn4|7h
T3s|4_
aargh3
acetone_
anon4
cancername
eyedeekay_bnc
not_bob_afk
profetikla
shiver_1
u5657
weko_
x74a6
orignal
will try more
orignal
tried 15 more
orignal
14 worked fine
orignal
1 was not reachable
zzz
try XAng and Ug0S, they seem to fail frequently for me
zzz
note that I almost never see a peer with 100% fails, maybe that's a clue
orignal
when I test I run for few minutes
orignal
so there were multiple peer tests
orignal
I don't see Ug0S in you list
orignal
will try XAng
orignal
3336971979:me ⇒ XAng ⇒ ( 92ms ) established, 6 KiB
orignal
3336971979:me ⇒ XAng ⇒ ( 97ms ) established, 10 KiB
orignal
no problem with tests
orignal
well 90 ms seems too much for me
orignal
2295247437:me ⇒ XAng ⇒ ( 124ms ) established, 25 KiB
orignal
after 15 minutes
orignal
a new tunnel, no problems
orignal
can you also try xZ9n if it has some issue for you
orignal
this is my router
orignal
if there are problems I will be able error messages
zlatinb
I'm still building the testnet, my LXC containers are Bionic so I had to build i2pd from inside the container
zlatinb
but it should be up soon
orignal
but I still don't understand what's a problem exactly
orignal
initially I was under impression that nothing went trhough that tuunels
orignal
now zzz says that sometimes tests are successive, somotimes fail
orignal
if it's the last case my tests might be irrelevant
orignal
because I have OBEP and IBGW on the same router
zlatinb
orignal: how can I force the external SSU/NTCP2 address? RIght now i2pd is picking up 127.0.0.1 and building the RouterInfo with it
R4SAS
address4 = 10.X.X.X
R4SAS
nat = false
zzz
if it will publish 127.0.0.1 that's a bug
zzz
I thought that was only in the forks, but if it's in mainline it needs to be fixed
R4SAS
zzz: it wont
R4SAS
mustn't at least
zzz
<zlatinb> orignal: how can I force the external SSU/NTCP2 address? RIght now i2pd is picking up 127.0.0.1 and building the RouterInfo with it
R4SAS
address4 = 10.X.X.X
R4SAS
nat = false
R4SAS
zlatinb: how you disabled address check?
R4SAS
address_pair_v4
zlatinb
comment out the line with 10.0.3
R4SAS
try two options above
R4SAS
nat = false will disable reachability checks
R4SAS
and will be forced to use address from option, AFAIK
zlatinb
works now, thanks
zlatinb
SSU 10.0.3.39:...
zlatinb
hmm
zlatinb
Our external address:
zlatinb
NTCP2: 0.0.0.0:...
zlatinb
SSU: 0.0.0.0:...
zlatinb
but maybe works
zlatinb
let me add a java router
R4SAS
zlatinb: both options added?
zlatinb
host=10.0....
zlatinb
nat=false
orignal
host is for RI
orignal
address4, address6 and address is an interface to bind
orignal
I think it publishes 127.0.0.1 because it detects it as 127.0.0.1
zlatinb
had to add ifname and ifname4, now i2pds talk to each other, but not to java yet
orignal
ifname is obsolote thing
orignal
just for backward compaibility
zzz
if it ever publishes 127.0.0.1 or 0.0.0.0, that's a bug. I see it a lot on the live net, but I thought it was only in forks, not mainline
zlatinb
I was wrong, i2pd's not talking to each other either, but they have each other in the netdb successfully looks like
zlatinb
an ntcp2 corruption in the java logs? very weird
zlatinb
SSU: Send exception: Invalid argument while trying to send data to 10.0.3.191:25616 (length: 304)
zlatinb
that's between two i2pds
zlatinb
that's some boost thing in SSU.cpp, I don't know how to read it well
zlatinb
looks like an invalid argument is passed to the boost library
zlatinb
I'll call it a day for now
orignal
probably can't find a route or something
orignal
zzz it did publish before but I have fixed it few releases ago
orignal
or maybe ifname
zlatinb
oh I had the ip instead of the ifname, now they talk to each other
zlatinb
:)
zlatinb
now let's try java...