Re: [ovs-discuss] OVS port name differ from interface name

There is s typo in add-br command. Your bridge name is br instead of 0.br /Shivaram ::Sent from my mobile device:: > On Jan 18, 2018, at 5:17 AM, Riccardo Ravaioli > wrote: > > Hi Ben, > > I have a related question. I do the following in order to have a bridge

Re: [ovs-discuss] OVS port name differ from interface name

In the example above my bridge name is br and my ports are named 0.br, 1.br, etc. It's just an example. I could have chosen myport0, myport1, etc. On 18 January 2018 at 14:39, Shivaram Mysore wrote: > There is s typo in add-br command. Your bridge name is br instead

Re: [ovs-discuss] OVS port name differ from interface name

Hi Ben, I have a related question. I do the following in order to have a bridge br with ports 0.br, 1.br... and later add existing interfaces to such ports: ovs-vsctl add-br br ovs-vsctl add-port br 0.br ovs-vsctl --id=@ifce create interface name=eth1 -- set port 0.br interface=@ifce When I

Re: [ovs-discuss] OVS port name differ from interface name

Maybe you want it to be an "internal" port: ovs-vsctl set interface type=internal On Thu, Jan 18, 2018 at 02:17:03PM +0100, Riccardo Ravaioli wrote: > Hi Ben, > > I have a related question. I do the following in order to have a bridge br > with ports 0.br, 1.br... and later add existing

Re: [ovs-discuss] In 'OVS Faucet Tutorial', router does not work as expected at 'Step 4: Router Broadcasts ARP Request'

I sent a series that adds these features: https://patchwork.ozlabs.org/project/openvswitch/list/?series=24270 On Thu, Jan 18, 2018 at 09:34:40AM +1300, Brad Cowie wrote: > We've had a bit of a think about this, variable length probably isn't too > important (static 64b is probably fine),

[ovs-discuss] Block outgoing packets on a specific port

Our OVS runs a broadcast app that sends UDP packets out on br0. Currently as expected, these packets go out of all interfaces in br0. I would like to force it such that these packets do NOT go out of a specific interface, but still goes out of the other interfaces. I tried using open flow as

Re: [ovs-discuss] unexpected behavior in ovs faucet tutorial

Hi Du, Did you build your OpenvSwitch version 2.8.90 source? If so what git commit are you using? I just tried to replicate your problem with OVS 2.8.2 from git (commit 27dbf5d394) and that step of the tutorial works fine for me. Perhaps you could send me the contents of your faucet.log and I

Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports

> OK, what about this patch instead? It should fix the issue without the > errors. I have not tested. I tried your patch but it does not re-add the routes. The reason is doing $ ifup br0 will not invoke ifup-post since the bridge port is already UP and so $OVSBRIDGECONFIGURED will be 'true'. I

[ovs-discuss] Linking of OFPROTO and NETDEV libraries to OVS

Hi All, Is there a way to link OFPROTO and NETDEV libraries directly to OVS binary without recompiling the OVS codebase. Like, downloading the OVS debian binary directly and link the ofproto and netdev dynamic libraries to it. Afaik, currently, we need to compile the OVS code with ofproto and

Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports

On Thu, Jan 18, 2018 at 10:12:40AM +, Vishal Deep Ajmera wrote: > > BTW, I suggested earlier but maybe I wasn't clear. > > > > Instead of adding networking configuration to the bridge's port, just > > leave it alone with a name that doesn't bother you. > > > > Then create an internal port

[ovs-discuss] vPort state

Hi, Can someone help in understanding the reason for not allowing the vport state to DOWN. Presently, if we try to bring down tunnel ports (or vPorts) using "ovs-ofctl mod-port" command then OVS rejects it as "not supported". Thanks, Nitin ___

Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports

On Thu, Jan 18, 2018 at 08:32:03AM +, Vishal Deep Ajmera wrote: > > OK, what about this patch instead? It should fix the issue without the > > errors. I have not tested. > > I tried your patch but it does not re-add the routes. The reason is doing > $ ifup br0 will not invoke ifup-post since

Re: [ovs-discuss] Block outgoing packets on a specific port

> On Jan 18, 2018, at 3:27 PM, Ajit Warrier wrote: > > Our OVS runs a broadcast app that sends UDP packets out on br0. Currently as > expected, these packets go out of all interfaces in br0. I would like to > force it such that these packets do NOT go out of a specific

Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports

> BTW, I suggested earlier but maybe I wasn't clear. > > Instead of adding networking configuration to the bridge's port, just > leave it alone with a name that doesn't bother you. > > Then create an internal port with the name and the networking > configuration you need. It won't change its MAC