View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003196 | GNUnet | transport service | public | 2013-12-11 13:54 | 2013-12-24 20:53 |
| Reporter | Matthias Wachs | Assigned To | Matthias Wachs | ||
| Priority | urgent | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | Git master | ||||
| Target Version | 0.10.0 | ||||
| Summary | 0003196: Report on peer connectivity: UDP | ||||
| Description | Connectivity with UDP plugin: Peer a) 131.159.20.147 Peer b) 131.159.20.52 2 clean peers in same LAN running revision 31272 - 2 peers with udp no firewall, directly connected with hostlist: connected (transport, topology, core, dht, fs): OK benchmark: OK reconnect after shutdown: FAIL peer a and b connected peer a shutdown peer b does not notice, stays connected Case a) peer a starts again in < CONNECTION_IDLE_TIME -> peer a connects on transport level (statistics) but not on level > transport (core ... ) peer b states to be connected, no new additional connect message after peer a restarts transport benchmark works -> reconnecting peer does not notify upper layers -> disconnected peer does not notify disconnect (within reasonable time) -> ISSUE! Case b) peer b states peer a disconnected after CONNECTION_IDLE_TIME peer a starts again both peers connect on all levels -> OK - 2 peers with udp no firewall, directly connected with broadcasting: connected (transport, topology, core, dht, fs): OK benchmark: OK reconnect after shutdown: OK - 2 peers with udp 1 peer a listen only, directly connected hostlist: connected (transport, topology, core, dht, fs): OK benchmark : OK reconnect after shutdown of peer a: OK (but takes some time since peer b thinks it is still connected) | ||||
| Tags | No tags attached. | ||||
| parent of | 0003213 | closed | Christian Grothoff | udp address validation denied due to address mismatch, despite address matching |
|
|
The issue mentioned above is fixed with reducing the idle connection timeout and fixing the core key exchange issue ... peers connect on both transport and core level. |
|
|
Fixed with 31309. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-12-11 13:54 | Matthias Wachs | New Issue | |
| 2013-12-11 13:54 | Matthias Wachs | Status | new => assigned |
| 2013-12-11 13:54 | Matthias Wachs | Assigned To | => Matthias Wachs |
| 2013-12-11 13:54 | Matthias Wachs | Description Updated | |
| 2013-12-11 13:59 | Christian Grothoff | Priority | normal => urgent |
| 2013-12-11 13:59 | Christian Grothoff | Product Version | => Git master |
| 2013-12-11 13:59 | Christian Grothoff | Target Version | => 0.10.0 |
| 2013-12-11 14:54 | Matthias Wachs | Description Updated | |
| 2013-12-11 14:55 | Matthias Wachs | Description Updated | |
| 2013-12-11 15:07 | Matthias Wachs | Description Updated | |
| 2013-12-11 15:16 | Matthias Wachs | Description Updated | |
| 2013-12-13 18:40 | Christian Grothoff | Severity | minor => major |
| 2013-12-13 19:38 | Christian Grothoff | Relationship added | parent of 0003213 |
| 2013-12-16 11:28 | Matthias Wachs | Note Added: 0007888 | |
| 2013-12-16 11:29 | Matthias Wachs | Note Added: 0007889 | |
| 2013-12-16 11:29 | Matthias Wachs | Status | assigned => resolved |
| 2013-12-16 11:29 | Matthias Wachs | Resolution | open => fixed |
| 2013-12-24 20:53 | Christian Grothoff | Status | resolved => closed |
