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 694588 - RFE: Automatic bridge <--> route/NAT (connection sharing) transitions for VM bridge device
RFE: Automatic bridge <--> route/NAT (connection sharing) transitions for VM ...
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on: 593815
Blocks:
 
 
Reported: 2013-02-24 14:40 UTC by David Jaša
Modified: 2020-11-12 14:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Jaša 2013-02-24 14:40:34 UTC 
Travelling computer sometimes connects to networks capable of bridging and sometimes to other networks. It would be nice to be able to specify for bridge device that the outgoing connection should be enslaved to it if possible so that VMs could get direct connectivity for that case; and if it is not possible, fall back to some "connection sharing" scheme (routing if possible, NAT on IPv4 if not).
Comment 1 David Jaša 2013-02-24 14:41:45 UTC 
Just to add: when transitioning from one state to another, tap slaves should be put down and up again so that VMs can notice network configuration changes.
Comment 2 Pavel Simerda 2013-05-09 11:02:34 UTC 
This would be rather complicated. But it might be possible to use some fallback scheme (e.g. ARP proxy based) that could be optionally used instead of bridging. We don't even have IPv6 internet sharing solved, see bug 593815.
Comment 3 André Klapper 2020-11-12 14:27:43 UTC 
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).