 |
This works fine for me (I use it for my kvm host) however you have some config options that may not be correct. I have: ifcfg-enp6s0 which contains: NAME=enp6s0 UUID=6e1754ca-7c6d-4abf-89d2-124987e4ff6c ONBOOT=yes HWADDR=BC:30:5B:A1:AE:BF ONBOOT=yes BRIDGE=br0 NM_CONTROLLED=no and ifcfg-br0, which contains: DEVICE=br0 TYPE=Bridge BOOTPROTO=dhcp ONBOOT=yes DELAY=0 NM_CONTROLLED=no PEERDNS=yes PEERROUTES=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no Once the files are there, you should not need to use the ifup/ifdown scripts (and these may cause issues). You simply need to (re)start the network service |
|
|
WFM with listed configuration in previous comment. Please double check your configs. |
|
|
Some of the differences in the ifcfg-files may be caused by ipv4 <-> ipv6. And yes, of course the interfaces are brought up and down automatically during network start and stop (without error messages), I used them for debugging only. The problem of the calls to brctl with swapped parameters remains, as the ifup-eth and ifdown-eth scripts are called by service network start and stop: the ethernet interface is not bound to the bridge. |
- Anonymous
