GNOME Bugzilla – Bug 726400
NMPolicy: don't reject activating devices with incomplete IP config
Last modified: 2014-06-30 15:26:51 UTC
An activating device may have an IP config that is unrelated to the current activation (for example if it comes from capturing the existing config when NM is started), and that config might not have a gateway, which would have NM ignore that the device is activating until after DHCP.
Created attachment 271993 [details] [review] NMPolicy: don't reject activating devices with incomplete IP config
ACK. This looks correct to me.
(In reply to comment #2) > ACK. This looks correct to me. I don't have commit access in Freedesktop, would you please push it for me? Thanks!
(In reply to comment #3) > (In reply to comment #2) > > ACK. This looks correct to me. > > I don't have commit access in Freedesktop, would you please push it for me? > Thanks! Sure, I just waiting what others have to say about it... soembody will take care of it. Btw, thanks for your effort!! :)
Any update on this? This is causing buggy behavior in gnome-shell 3.12, it would be nice to merge and then backport it.
Yeah, this makes sense to me. Do we want to get it into 0.9.10?
The patch seems right to me.
Merged to: master: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=86ca7dce0ca3e08b8a3ea41799d2c4c103559c53 nm-0-9-10: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=66a593fd5a48172b0a309fa943833000512ebb14 nm-0-9-8: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2b989048d6cc63a3f87b1b8e35b534acebe2179d