public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed
* New issue with nncp-caller in 6.1.0
@ 2021-02-28 21:39 John Goerzen
2021-03-01 9:52 ` Sergey Matveev
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: John Goerzen @ 2021-02-28 21:39 UTC (permalink / raw)
To: nncp-devel
Hi Sergey,
First, THANKS for all the work you've been doing with NNCP.
That's great!
Avoiding the separate check step is a huge improvement for large
transfers.
Also, FYI, I've had some more posts at
https://changelog.complete.org/archives/tag/nncp
So on a machine I upgraded from 5.6.0 to 6.1.0, I'm now seeing
this from nncp-call periodically:
2021-02-28T21:17:39Z Got packet
67YD5DNOPZCLFX2YCQHARXREOGYSVY43HNJGJMP3WMDQMOKBBK5Q 100% (1.3 KiB
/ 1.3 KiB)
Can not humanize: strconv.ParseUint: parsing "": invalid syntax
When: 2021-02-28T21:17:39.780465113Z
Err: offset differs
Who: sp-file
Node: L3WOIONS7NFQN53SIDHT3VMJ7HELW3WLBRYTO7MEAH4OMC36JLHQ
Nice: 255
Type: file
XX: rx
Pkt: LV7CQMEYQ2SD234AZ35GROB3RT7NABGU5TVDCM5325ODFBB3ADWA
Size: 65232
Msg: deleting hasher
2
Incidentally I've also made some tests of NNCP over tor. tor
takes some time with connection establishment, and I wound up with
some of those 10-second timeouts trying that. But if I'd retry
enough times, eventually it would work.
I put this in addrs:
tor: "|nc -X 5 -x 127.0.0.1:9050 [redacted].onion 12345"
- John
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: New issue with nncp-caller in 6.1.0
2021-02-28 21:39 New issue with nncp-caller in 6.1.0 John Goerzen
@ 2021-03-01 9:52 ` Sergey Matveev
2021-03-01 11:23 ` Sergey Matveev
2021-03-07 16:35 ` Sergey Matveev
2 siblings, 0 replies; 4+ messages in thread
From: Sergey Matveev @ 2021-03-01 9:52 UTC (permalink / raw)
To: nncp-devel
[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]
Greetings!
*** John Goerzen [2021-02-28 15:39]:
>First, THANKS for all the work you've been doing with NNCP. That's great!
Thank you!
>Avoiding the separate check step is a huge improvement for large transfers.
I am planning to add tree hashing (Merkle tree) to speed up partly
received files checking.
>Also, FYI, I've had some more posts at
>https://changelog.complete.org/archives/tag/nncp
I am subscribed to your blog. Yep, interesting things you write.
I have got similar, but on russian language :-).
>So on a machine I upgraded from 5.6.0 to 6.1.0, I'm now seeing this from
>nncp-call periodically:
Fixed it quickly in: http://www.git.cypherpunks.ru/?p=nncp.git;a=commitdiff;h=36953cde29afd58982caf2327d3dbe5bf5242256
Current messages are a long-time mess already. Seems that the first
thing I should do is to clean all of them and make a clear strict scheme
for each possible message. That should prevent that kind of errors when
some fields are missing.
>Incidentally I've also made some tests of NNCP over tor. tor takes some time
>with connection establishment, and I wound up with some of those 10-second
>timeouts trying that. But if I'd retry enough times, eventually it would
>work.
I think that configurable option for handshake timeout is easy to add.
Handshake timeouts are just hardcoded, that is not right.
If you do not need some kind of anonymity, then Yggdrasil works pretty
well with very low overhead and relatively low latencies. I have not
touched for years, but remember that liked it much. Very easy to setup
overlay network, where even NATed nodes can communicate through the
other ones. cjdns was very unstable when I connected to Hyperboria.
--
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263 6422 AE1A 8109 E498 57EF
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: New issue with nncp-caller in 6.1.0
2021-02-28 21:39 New issue with nncp-caller in 6.1.0 John Goerzen
2021-03-01 9:52 ` Sergey Matveev
@ 2021-03-01 11:23 ` Sergey Matveev
2021-03-07 16:35 ` Sergey Matveev
2 siblings, 0 replies; 4+ messages in thread
From: Sergey Matveev @ 2021-03-01 11:23 UTC (permalink / raw)
To: nncp-devel
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
*** John Goerzen [2021-02-28 15:39]:
>Err: offset differs
>Msg: deleting hasher
Also that should not be the error message. It should be the debug one,
just telling that transparent hashing of (partly) received file won't be
used. No worries.
--
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263 6422 AE1A 8109 E498 57EF
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: New issue with nncp-caller in 6.1.0
2021-02-28 21:39 New issue with nncp-caller in 6.1.0 John Goerzen
2021-03-01 9:52 ` Sergey Matveev
2021-03-01 11:23 ` Sergey Matveev
@ 2021-03-07 16:35 ` Sergey Matveev
2 siblings, 0 replies; 4+ messages in thread
From: Sergey Matveev @ 2021-03-07 16:35 UTC (permalink / raw)
To: nncp-devel
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
*** John Goerzen [2021-02-28 15:39]:
>Can not humanize: strconv.ParseUint: parsing "": invalid syntax
I make huge refactoring in 6.2.0 of the logging and all that kind of errors
should pass away. Shamefully logging is the most refactoring thing in NNCP.
--
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263 6422 AE1A 8109 E498 57EF
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-03-07 16:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-28 21:39 New issue with nncp-caller in 6.1.0 John Goerzen
2021-03-01 9:52 ` Sergey Matveev
2021-03-01 11:23 ` Sergey Matveev
2021-03-07 16:35 ` Sergey Matveev