View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006870 | GNUnet | transport service | public | 2021-05-17 08:33 | 2026-08-20 12:05 |
| Reporter | schanzen | Assigned To | t3sserakt | Due Date | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | Git master | ||||
| Target Version | 1.0.0 | Fixed in Version | 0.29.0 | ||
| Summary | 0006870: [TNG] UDP Communicator should tell TNG service of outgoing queue on packet receipt | ||||
| Description | Currently, the UDP communicator tells the service of outgoing queues whenever we connect to an ip/port given a hello. The communicator then tries to verify this connection through a key exchange. The receiver, upon receiving a KX, tries to send an answer back via the TNG service. (Backchannel) Before doing that, the receiver should tell the TNG service of the outgoing queue to the endpoint from which we just received the KX. Currently, this is not done and this results in a situation where if the receiver does not have any other connections, it will never send an answer to the KX. Basically, we should treat the incoming packet like a connection request from the TNG service, providing unverified queues for use in a virtual link. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-05-17 08:33 | schanzen | New Issue | |
| 2021-05-17 08:33 | schanzen | Tag Attached: tng | |
| 2021-06-10 17:36 | schanzen | Target Version | 0.15.0 => 0.16.0 |
| 2021-12-31 08:29 | schanzen | Target Version | 0.16.0 => 0.17.0 |
| 2021-12-31 08:32 | schanzen | Target Version | 0.17.0 => 1.0.0 |
| 2024-03-05 14:53 | schanzen | Assigned To | => t3sserakt |
| 2024-03-05 14:53 | schanzen | Status | new => assigned |
| 2024-03-05 14:54 | schanzen | Note Added: 0021683 | |
| 2026-01-25 14:13 | Christian Grothoff | Tag Detached: tng | |
| 2026-08-19 05:52 | schanzen | Status | assigned => resolved |
| 2026-08-19 05:52 | schanzen | Resolution | open => fixed |
| 2026-08-19 05:52 | schanzen | Fixed in Version | => 0.29.0 |
| 2026-08-20 12:05 | schanzen | Status | resolved => closed |