Re: NetworkManager git20121211

On Thu, 2013-01-31 at 10:59 -0500, Gene Czarcinski wrote:
> I needed some functionality (dynamic dns update) not available in the 
> NetworkManager package available in Fedora 18 so I created my own 
> version based on git20121130.  This worked nicely providing the 
> functionality and did not appear to have any bad side effects.
> Then the NetworkManager git20121211 package appeared in rawhide it is 
> usually better to use a package available from Fedora.  So, I got the 
> source rpm and rebuilt it for Fedora 18.
> This appeared to work fine until I realized that all of the virtual 
> networks did not have the expected IPv4 addresses.  Surprisingly, if 
> IPv6 was defined for a network, it was there.

And by "virtual networks" you mean bridge interfaces, as I see from the
bug.  Bridging support will be turned off-by-default in the 0.9.8
release until we can become better at cooperating with existing
configurations.  It will be enabled by editing the NetworkManager.conf
file if you'd like to use NM to configure bridges.


> After some investigation, I could only see that NetworkManager may be 
> the problem.  I downgraded to the git20121130 package and rebooted.  The 
> virtual networks were now OK.
> Any suggestions on how to report this problem? (against what and what 
> release?)
> I am effectively cross-posting by sending identical messages to the 
> NetworkManager and libvirt mailing lists.  Yes, I believe the problem is 
> with NetworkManager but there is a large libvirt impact.
> Gene
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]