On 2019-01-09 8:33 a.m., Christopher Hannon wrote:
Thanks for your reply, I think I understand your point regarding
hardware switching. Although wouldn't there need to be a layer 3
connection somewhere to pull a packet from one vlan to the other? I
guess I am not completely sure about how the
I made sure while building that I use the module that was built from OVS
sources by creating a config file as shown in Building section here:
http://docs.openvswitch.org/en/latest/intro/install/general/
What else should I do to use the module from OVS sources?
On Thu, Jan 10, 2019 at 11:33 AM
You’ll need to consult your distro’s documentation about how to load an
out-of-tree kernel module. There’s usually plenty of examples available online.
--Justin
> On Jan 9, 2019, at 10:41 PM, Ramzah Rehman wrote:
>
> I made sure while building that I use the module that was built from OVS
That’s the version of ovs-vswitchd—the userspace daemon that talks with the
kernel datapath.
--Justin
> On Jan 9, 2019, at 10:17 PM, Ramzah Rehman wrote:
>
> Alright. But I can find ovs-vswitchd version like this:
>
> ovs-vswitchd --version
> ovs-vswitchd (Open vSwitch) 2.10.90
>
> Does
Alright. But I can find ovs-vswitchd version like this:
ovs-vswitchd --version
ovs-vswitchd (Open vSwitch) 2.10.90
Does this mean something?
On Thu, Jan 10, 2019 at 2:33 AM Justin Pettit wrote:
>
> > On Jan 8, 2019, at 5:48 AM, Ramzah Rehman
> wrote:
> >
> > ovs-vsctl list bridge br0
> >
>
Is there any other way to distinguish different types of packets/flows when
they enter dp_netdev_input__ and processed further(EMC,fastpath etc)?
As of now, I have to *flow_extract* the packets using *struct flow flow*:
if (flow.nw_proto == IPPROTO_TCP && l4_size >= TCP_HEADER_LEN) I want to
Thanks for your reply, I think I understand your point regarding hardware
switching. Although wouldn't there need to be a layer 3 connection
somewhere to pull a packet from one vlan to the other? I guess I am not
completely sure about how the vlans get connected together. Would this be
in OVS?
hello everyone,
i have a doubt here when i am trying the mqprio qdisc of linux on my
physical interface its working but when i am trying on interfaces created
by ovs then mqprio qdisc is not working.
eg:
root@IN:/sys/devices/virtual/net/s1-eth1/queues# sudo tc -g class show dev
ens160
+--(:4) mq
On Tue, Jan 08, 2019 at 04:04:37PM +0300, Artem Gromov wrote:
> Hi,
> OVS sends confusing error message to incorrectly formed OFPGroupMod message
> with OFPGC_ADD command and command_bucket_id set.
>
> This condition (absence of else keyword and body) is probably the main
> cause:
>
> On Jan 8, 2019, at 5:48 AM, Ramzah Rehman wrote:
>
> ovs-vsctl list bridge br0
>
> _uuid : bd776aad-3a88-4d38-a7a2-6be57723f04b
> auto_attach : []
> controller : []
> datapath_id : "ae6a77bd384d"
> datapath_type : ""
> datapath_version:
On Mon, Jan 07, 2019 at 07:45:05PM +0200, George Papathanail wrote:
> I have instantiate a topology in Mininet with 2hosts and 3 switches.
> I have to encode the output ports of the switches on packet header in order
> to reduce the state of the switches.
>
> For example if the output ports are 3
11 matches
Mail list logo
