Dear all ,
we create a bridge "br1" with the type of netdev .And the version of the
ovs is 2.5.0. Then we run the command "ovs-vsctl set int br1 lldp:enable=true "
to make the interface br1 enable the function lldp.After that ,we delete the
bridge br1 ,we found the the process
Got it. I'll try it.
Ethan
Ben Pfaff 於 2017年4月19日 週三 上午2:08寫道:
> I guess that if you know these kinds of specific properties of your
> network, then perhaps you should disable in-band control and add your
> own control flows.
>
> On Tue, Apr 18, 2017 at 05:31:37PM +, 蘇于倫
Thanks, Ben!
In case of the last email content is hidden, I re-send the question again
here:
If I set the action of in-band hidden flows to be output: OFPP_PORT_X with
X being the port number: 1, 2 or 3, etc,
which are defined in openflow-1.0.h. Does it make sense to direct all
in-band packet
One way, which may not be satisfactory, is to use "ovs-appctl
ofproto/trace" to simulate a packet from the switch to the controller.
On Tue, Apr 18, 2017 at 03:39:24PM +, 蘇于倫 wrote:
> Hi Farooq,
>
> Thanks for the comments.
>
> I use the command a lot. However, what I want to get is which
On Tue, Apr 18, 2017 at 10:29:50AM -0400, Eric Garver wrote:
> On Tue, Apr 18, 2017 at 12:17:17PM +0800, Dickens Yeh wrote:
> > Thanks for your response.
> > I know that if I have to match multiple vlan tags, it have to pop the outer
> > vlan.
> > But I think my question are not the matching vlan
Hi Farooq,
Thanks for the comments.
I use the command a lot. However, what I want to get is which ports the OVS
is using for hidden flow packet.
The actions of default hidden flows are NORMAL (ports) which do not provide
this info.
If I got any misunderstanding, please kindly comment!
Thanks
Hi everyone,
I'd like to know if we can see which ports the OVS is using to connect to
controller in "in-band" mode?
I use ovs-appctl fdb/show , and get the following table
port VLAN MACAge
2 0 00:0c:29:30:04:484
1 0 00:0c:29:c2:d1:420
1 0
On Tue, Apr 18, 2017 at 12:22:56PM +0800, Dickens Yeh wrote:
> Yes, I use the master branch and set with vlan-limit=0.
> The line 362 says "e.g. a packet with more 802.1q headers will match
> Ethernet type 0x8100."
This applies if the number of VLAN tags exceeds the value of vlan-limit.
For
Hi Ben, Darrell,
It sounds like the general feeling is that any kind of tc pre-processing is not
worth it and the existing egress queing/QoS facilities should suffice.
Thanks for your comments.
/Billy
> -Original Message-
> From: Ben Pfaff [mailto:b...@ovn.org]
> Sent: Thursday,