Opened 6 years ago
Closed 5 years ago
#1171 closed defect (fixed)
Fix tunnel message documentation
| Reported by: | str4d | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.10 |
| Component: | www/i2p | Version: | 0.9.9 |
| Keywords: | docs | Cc: | |
| Parent Tickets: | Sensitive: | no |
Description
<orignal> I've found the big mistake in the documentation
<iRelay> <user@kyirc> seems like you're making good progress
<iRelay> <user@kyirc> oh
<orignal> delivery instruction are different between tunnels and garlics
<iRelay> <user@kyirc> ideally open a ticket on trac.i2p2.de
<orignal> just FYI
<orignal> hash and tunnelID are reverted in garlic messages
<iRelay> <user@kyirc> maybe you can elaborate a bit
<orignal> https://geti2p.net/en/docs/spec/tunnel-message#delivery
<iRelay> Title: Tunnel Message Specification - I2P (at geti2p.net)
<iRelay> <user@kyirc> I'm not into thsese coding details, but I'm sure those who are will read that and correct the specs
<orignal> it says they tunnelID is first and hash is next
<iRelay> <user@kyirc> thank you for reporting that, orignal! 
<orignal> that's true for tunnels but not for garlics
<orignal> spent few days to find out what's wrong
I missed this ticket but the OP later entered it in #1147 comment 1, which I did see. Fixed in d19c55c7887b96bf1bda4868976a623f94cc9e92 et seq., ca. Feb. 7, as noted in #1147 comment 8.