What version of libnl3 do you have installed? I was having bridge
problems too this week. I downgraded libnl3 from 3.2.24-1.fc20 to
3.2.21-2.fc20 and restarted the NetworkManager service, and then my
bridge worked. See https://bugzilla.redhat.com/1063290
- Ken
On Fri, Feb 14, 2014 at 12:30 PM, Jo
I've also noticed a regression in my network bridge setup.
Use bridging for both virt-manager, and development work with aarch64
bringup (emulated ARMv8).
Have seen this happen on two recently updated f20 systems.
I'm using traditional network-scripts, and what happens is the
physical interface ap
Hello,
I have two fully updated F20 boxes running VMs. The
bridging on one box was working but not on the
other... It appeared the only real difference was
the names. The working bridge was call 'br0'
and the non-working was called 'bridge0'
I also notice that 'br0' showed virt-manager's list o
