After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764491 - Automatically discover remote boxes in the local network
Automatically discover remote boxes in the local network
Status: RESOLVED DUPLICATE of bug 694854
Product: gnome-boxes
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-04-02 11:33 UTC by Felipe Borges
Modified: 2017-06-20 12:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Felipe Borges 2016-04-02 11:33:07 UTC 
Considering the current goal of feature parity with Vinagre[0], It would be useful for Boxes to be able to discover remote machines shared in the local network.

Vinagre uses Avahi (if available) to discover shared local remote machines when the user presses the Find button in the Connect dialog.

[0] https://wiki.gnome.org/Apps/Boxes/Remote
Comment 1 Visarion Alexandru 2017-03-22 14:46:31 UTC 
(In reply to Felipe Borges from comment #0)
> Considering the current goal of feature parity with Vinagre[0], It would be
> useful for Boxes to be able to discover remote machines shared in the local
> network.
> 
> Vinagre uses Avahi (if available) to discover shared local remote machines
> when the user presses the Find button in the Connect dialog.
> 
> [0] https://wiki.gnome.org/Apps/Boxes/Remote

This might actually be already implemented.

In the bug related to exposing SPICE connections on the network, I have also developed a way to create Remote Boxes out of shared VNC/SPICE connections on the local network (and also added some extra setup pages for the wizard, as guided by Zeeshan)

https://bugzilla.gnome.org/show_bug.cgi?id=694854
Comment 2 Felipe Borges 2017-06-20 12:04:36 UTC 

*** This bug has been marked as a duplicate of bug 694854 ***