Hi Tommy,
Here’s how I do it. It’s essentially the same as what the ‘ovs-ofctl add-flow’
command does under the hood.
1. Build a string formatted as the “ovs-ofctl” command would do, for example
“table=1,cookie=0xdeadbeef,in_port=1,actions=resubmit(,2)”
2. Pass this to
Hi Wolfgang,
> On Sep 13, 2017, at 3:48 AM, Wolfgang Link wrote:
>
> The new package libopenvswitch depends on libssl-dev.
> Is this intentionally made or is libssl1.1 also good?
>
This is intentional. In general 'libfoo-dev' packages contain header files and
symlinks to
Hi,
I don’t think you should see the OVS bridge there. You should have created the
OVS bridge using ‘ovs-vsctl add-br’, not using bridge utilities. In my case,
‘brctl show’ has nothing, while ‘ovs-vsctl show’ displays my bridge topology.
—Ben
> On Aug 23, 2017, at 10:19 AM, Chad Willman
Hi Chad,
I’ve seen this if regular Linux bridging is enabled. The command ‘brctl show’
will display non-OVS bridges.
regards,
Ben
> On Aug 23, 2017, at 9:23 AM, Chad Willman wrote:
>
>
> Is there a forum specific to discing issues encountered ?
>
> My ovs-vswitchd
Hello Xiao,
> On Jul 29, 2017, at 11:30 PM, Xiao Liang wrote:
>
> Hi,
>
> I've encountered some problems building a controller with
> libopenvswitch in C++. Although they can be solved by some hacks, I
> want to know if OVS is meant to be used in such case.
>
I don’t
Sorry, conntrack support was added in 2.5 and NAT in 2.6.
--Ben
> On Dec 14, 2016, at 5:12 PM, Joo Yong-Seok wrote:
>
> Is it possible to configure D-NAT rule in this version of ovs-ofctl?
>
> # ovs-ofctl --version
> ovs-ofctl (Open vSwitch) 2.3.90
> Compiled Dec 12