Hello all,
An ingress qdisc configured on a port that is enslaved into an OpenvSwitch
bridge gets automatically deleted when tcpdump is run on that port!
*OVS version :*
ovs-vsctl (Open vSwitch) 2.17.1
DB Schema 8.3.0
*OVS bridge config*
Bridge br0
Port br0
Interface br0
Hello all,
An ingress qdisc configured on a port that is enslaved into an OpenvSwitch
bridge gets automatically deleted when tcpdump is run on that port!
OVS version :
ovs-vsctl (Open vSwitch) 2.17.1 (also seen on 3.2.1)
DB Schema 8.3.0
OVS bridge config
Bridge br0
Port br0
0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
~$
Regards,
RS
On Thu, Jan 11, 2024 at 5:42 PM Ilya Maximets wrote:
> (trying to re-send as gmail decided to not deliver the previous email)
>
> On 1/11/24 17:38, Ilya Maximets wrote:
> > On 1/11/24 17:25, Res
The message from Ilya was somehow missed! Thanks for pointing it out and I
will continue discussion on the other thread.
Regards,
RS
On Fri, Jan 12, 2024 at 2:55 PM Eelco Chaudron wrote:
>
>
> On 12 Jan 2024, at 14:35, Reshma Sreekumar via discuss wrote:
>
> > Hello all,
I see..thanks for the explanation. My use-case is to have a traffic
redirection from an ovs-enslaved port to IFB netdevice on ingress Qdisc.
Considering the given mode of operation,may be it's better if I opt for
some other methods of redirection to IFB netdevice?
Thanks & Regards,
RS
, I believe, enslaving IFB into ovs will not work for me. If ovs
supports some sort of ingress redirection, then that might help!
Thanks & Regards,
RS
On Mon, Jan 15, 2024 at 10:23 PM Ilya Maximets wrote:
> On 1/15/24 21:05, Reshma Sreekumar via discuss wrote:
> > I see..t
of it to OVS, then
> add an OpenFlow rule to direct all traffic from veth1 to that new port.
> Traffic will appear on the other side of a veth. Though I'm not sure
> why OVS is in the picture in the first place.
>
> >
> > Thanks & Regards,
> > RS
> >
Hello,
I see similar behaviour for *ovs-internal* ports as well. My understanding
is that, ovs-internal ports aren't *managed* by Openvswitch (Please correct
me if I'm wrong) ?
In this case, is it expected for the *ingress qdisc on ovs-internal ports*
as well to be managed by ovs ?
Thanks,
RS
__
I see... Thanks a lot for the quick clarification!
Thanks & Best Regards,
RS
On Thu, 22 Feb, 2024, 11:18 am Ilya Maximets, wrote:
> On 2/22/24 10:03, Reshma Sreekumar wrote:
> > Hello,
> >
> > I see similar behaviour for *ovs-internal* ports as well. My
> understanding is that,
> > ovs-internal
