On Wed, Oct 08, 2014 at 03:17:56PM +0200, Mehdi Abaakouk wrote: > root@g3:/var/lib/openvswitch# /etc/init.d/openvswitch-switch start > [ 382.897893] openvswitch: Open vSwitch switching datapath > Inserting openvswitch module. > /etc/openvswitch/conf.db does not exist ... (warning). > Creating empty database /etc/openvswitch/conf.db. > Starting ovsdb-server. > Configuring Open vSwitch system IDs. > Starting ovs-vswitchd. > Enabling remote OVSDB managers. > root@g3:/var/lib/openvswitch# ovs-vsctl add-br br-eth0 > [ 387.549586] device ovs-system entered promiscuous mode > [ 387.551218] openvswitch: netlink: Unknown key attribute (type=20, > max=19). > [ 387.553223] openvswitch: netlink: Unknown key attribute (type=62, > max=19). > [ 387.568880] device br-eth0 entered promiscuous mode > > I still have this errors when I create the bridge > > root@g3:/var/lib/openvswitch# ovs-vsctl add-port br-eth0 eth0 > [ 2279.939240] device eth0 entered promiscuous mode
None of the above messages indicates an error. > root@g3:/var/lib/openvswitch# ip link set eth0 up > root@g3:/var/lib/openvswitch# ip link set br-eth0 up > > > # ovs-vsctl show > 321f5ebc-adf4-4fe5-ab2c-5ccca143f366 > Bridge "br-eth0" > Port "eth0" > Interface "eth0" > Port "br-eth0" > Interface "br-eth0" > type: internal > ovs_version: "2.3.0" > > > But this bridge doesn't works. I test by just setting a ip on br-eth0 and > pinging an other machine on the same lan. OK, that is an indication that something is wrong. With the "ping" ongoing in the background, run "ovs-dpctl dump-flows" and show us the output. Thanks, Ben. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
