Gordon Messmer writes:
On 11/16/2017 07:50 PM, Sam Varshavchik wrote:Now, with the crisis averted, I'd like to figure out how to get my Windows VM back on the LAN, with its own static IP address.Usually, bridged networking can be set up with virsh: virsh iface-bridge eth0 br0 --no-stp
virt-manager itself can handle this too. But before any of that happens the physical port has to be attached to the bridge, and an IP address has to be assigned to the bridged physical port. That's the step that was not working any more.
It took some aimless poking for a while, and trying things at random, but after adding
NM_CONTROLLED=noto networks-scripts/ifcfg-vnet0, the config settings for the bridge itself, resulted in "ifup vnet0" work again, and running dhclient to acquire the server's IP address. It was working, without this explicit setting, prior to F27.
I compared all the initscripts between their F26 and F27 versions. There were some differences but I did not immediately see anything that explains the change in behavior. Both the F26 and the F27 versions of ifup-eth were quite insistent on exit 0-ing out before running dhclient, if the device was TYPE=Bridge. I could not figure out which dominoes are responsible for kicking off dhclient for bridge devices, but whatever and wherever it is, it apparently now requires NM_CONTROLLED=no before doing so.
Attachment:
pgpBF3Guv2_48.pgp
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
