cannot see a remote peer
Bug #277586 reported by
Vincent Verdot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dSM |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
When I launch two peers, say A and B, the device A can see B but B cannot see A.
Related branches
| Changed in dsm: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Vincent Verdot (vincent.verdot) wrote | #1 |
To post a comment you must log in.
This bug is caused by two problems:
- jxta library seems to send multicast peer discovery messages to an arbitrary selected interface, possibly different from the network interface it is bound to...
- dSM currently does not support multiple interfaces, it uses the first available one, so for now it is preferable to use dSM with a unique network interface activated on each testing device (multiple interfaces management will be the object of a future blueprint).
As a consequence, if two connected devices own several eligible interfaces, discovery messages can be sent to the wrong interfaces and so both devices could never meet (or partially).