[ovs-discuss] OVS bridge can not obtain the same physical interface ip by dhcp bootproto

Gurucharan Shetty shettyg at nicira.com
Tue Nov 11 16:15:12 UTC 2014

On Mon, Nov 10, 2014 at 12:14 AM, huwei.xtu at gmail.com
<huwei.xtu at gmail.com> wrote:
> Hi,
> I have a requirement to move the interface ip address to ovs bridge by
> ifcfg-ethX file's configuration. In some of my environment the following
> configuration can move the ip address to bridge, but some can not.
> ifcfg-br-ex:
> DEVICE=br-ex
> ONBOOT=yes
> HWADDR=00:50:56:B2:3C:5F
> OVS_EXTRA="set Bridge br-ex other-config:hwaddr=$HWADDR"
> TYPE=OVSBridge
Have a look at the examples here:
The examples ask you to use OVSBOOTPROTO instead of BOOTPROTO and then

> ifcfg-eth0:
> DEVICE=eth0
> ONBOOT=yes
> HWADDR=00:50:56:B2:3C:5F
> OVS_BRIDGE=br-ex
> In some of my environment, after service network restart, the ip in physical
> interface can be moved to the bridge. And there is no ip address in physical
> interface any more. But in some of other environments, this does not work.
> After service network restart, the related bridge can not obtain ip address,
> but the physical interface can obtain an ip address. If use dchlient -r eth0
> &&  dhclient br-ex, the br-ex can obtain a ip address which is not same with
> the physical interface ip address. Should this can be a ovs bug ? Or how can
> I make sure the ovs bridge can obtain the same ip address with the related
> physical interface, and the physical interface not get ip addesss ?
> ________________________________
> huwei.xtu at gmail.com
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss

More information about the discuss mailing list