View Issue Details

IDProjectCategoryView StatusLast Update
0003866GNUnettransport servicepublic2024-11-14 09:48
Reporterdangole Assigned Tot3sserakt  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Target Version1.0.0Fixed in Version0.23.0 
Summary0003866: local peer discovery should be implemented
DescriptionIdeally by announcing and querying using different mDNS backends like bonjour/apple?, android?/binder, avahi/dbus, mdns/ubus, ...
Another way might be to use UDPv6 link-local multicast directly on-top of Ethernet-like media.
Tagstng

Activities

Christian Grothoff

2015-06-27 16:48

manager   ~0009352

We do use UPDv6 multicast, and UDPv4 broadcast for local discovery already.

dangole

2015-06-27 17:39

developer   ~0009353

I see, looking at the code it seems sufficient.
It would be nice to allow configuring the specific interface to use for multicast/broadcast as well as adding/removing interfaces during runtime.

schanzen

2024-03-15 13:51

administrator   ~0021935

Is this issue fixed already?

thejackimonster

2024-10-07 16:59

developer   ~0023468

Last edited: 2024-10-07 17:59

I've found an issue in the UDPv4 broadcast for discovery:

In case the udp communicator does not disable ipv6, it will bind the `default_udp_sock` to an ipv6 address. That will cause a failure when trying to send a broadcast packet to an ipv4 broadcast address. So it's probably necessary to always have another default socket around for ipv4 traffic (bound to an ipv4 address) or using a raw socket for both protocols.

Issue is pretty much in gnunet-communicator-udp.c line 3341. So currently the UDPv4 broadcast only works when disabling ipv6 for the communicator.

thejackimonster

2024-10-08 19:07

developer   ~0023483

The issue with UDPv4 broadcast should be fixed with commit b3edc7b2ad04d09d84b06367b6c38c60ceebb33e now.

schanzen

2024-10-11 11:12

administrator   ~0023513

Isnt this already fixed?

schanzen

2024-11-14 09:48

administrator   ~0023717

This is fixed (at least as feature) since we introduced TNG.
Any remaining bugs may go into new issues.

Issue History

Date Modified Username Field Change
2015-06-27 02:17 dangole New Issue
2015-06-27 02:17 dangole Status new => assigned
2015-06-27 02:17 dangole Assigned To => Matthias Wachs
2015-06-27 16:48 Christian Grothoff Note Added: 0009352
2015-06-27 16:49 Christian Grothoff Assigned To Matthias Wachs =>
2015-06-27 16:49 Christian Grothoff Status assigned => acknowledged
2015-06-27 17:39 dangole Note Added: 0009353
2020-10-29 10:54 schanzen Tag Attached: tng
2020-10-29 10:55 schanzen Target Version => 0.15.0
2021-06-10 19:36 schanzen Target Version 0.15.0 => 0.16.0
2021-12-31 09:29 schanzen Target Version 0.16.0 => 0.17.0
2021-12-31 09:32 schanzen Target Version 0.17.0 => 1.0.0
2024-03-15 13:51 schanzen Assigned To => schanzen
2024-03-15 13:51 schanzen Status acknowledged => feedback
2024-03-15 13:51 schanzen Note Added: 0021935
2024-03-15 13:51 schanzen Assigned To schanzen => Christian Grothoff
2024-08-05 12:57 Christian Grothoff Assigned To Christian Grothoff => t3sserakt
2024-10-07 16:59 thejackimonster Note Added: 0023468
2024-10-07 17:59 thejackimonster Note Edited: 0023468
2024-10-08 19:07 thejackimonster Note Added: 0023483
2024-10-11 11:12 schanzen Target Version 1.0.0 => 0.22.2
2024-10-11 11:12 schanzen Note Added: 0023513
2024-10-11 11:13 schanzen Fixed in Version => 0.22.2
2024-10-11 11:13 schanzen Target Version 0.22.2 => 1.0.0
2024-10-29 20:56 schanzen Fixed in Version 0.22.2 =>
2024-11-14 09:48 schanzen Status feedback => resolved
2024-11-14 09:48 schanzen Resolution open => fixed
2024-11-14 09:48 schanzen Fixed in Version => 0.23.0
2024-11-14 09:48 schanzen Note Added: 0023717
2024-11-14 09:48 schanzen Status resolved => closed