Created attachment 1149050 [details] interfaces: ignore virbr0 Hi! The way libnice works by collecting local interfaces addresses and making candidate pairs with the list of remote addresses obtained from the remote peer makes it very sensitive to the number of local addresses collected. Roughly, every new local address multiply by two the number of candidate pairs to be checked. If you consider that the remote peer is in the same situation, you double again the number of candidates to be tested. This has a direct impact on the delay required to establish a connection, because the ICE algorithm of libnice will test each pair at a fixed rate, so the more pairs are to be tested, the more time the algorithm will take to complete. Pairs related to the virbr0 local interface can almost always (*) be ignored by the ICE algorithm. The virbr0 interface is created by the libvirtd daemon and allows access to the local virtual machines, if any. ICE connections between the host and other boxes on the internet have no interest in testing pairs related to this virbr0 interface, because its IP address is private, and outgoing traffic in nat-ted. And even ICE connections between a host and its virtual machine will work when the virbr0 interface is ignored by the ICE algorithm : the virtual machine has no knowledge of this interface, so it is not concerned, and the host will connect to its virtual machine, (*) as long as it has another local network interface up, with an IP address that the virtual machine can connect to. This patch is Fedora-specific, because other distros may choose to name this interface with a different name.
This could be submitted upstream with an AC_ARG_WITH([virtual-bridge-interface-name],…) option added to configure.ac, which determines the name to use instead of virbr0. Distributions can then change their packaging to set --with-virtual-bridge-interface-name=myspecialsnowflakeiface0 in their packaging instead.
Good idea, thanks!
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.