On 23 Mar 2023, at 8:54, Alex Zetaeffesse wrote:
> Just a note aside; in OVS I haven't defined the port bond0 as trunk, it's
> just a (LACP) port, what comes in is processed and what comes from the
> other ports is sent out of it. Needless to say, perhaps, that I can have
> more control on which
Just a note aside; in OVS I haven't defined the port bond0 as trunk, it's
just a (LACP) port, what comes in is processed and what comes from the
other ports is sent out of it. Needless to say, perhaps, that I can have
more control on which S-tagged frames the bond can process if I apply some
option
On Wed, Mar 22, 2023 at 5:35 PM Eelco Chaudron wrote:
>
>
> On 22 Mar 2023, at 17:19, Alex Zetaeffesse wrote:
>
> > For the bridge's interfaces' list, I guess the shorter the output the
> > better...
> >
> > root@pve:~# ovs-vsctl list-ifaces vmbr1
> > enp6s0f0
> > enp7s0f0
> > sv_z1ad0101
> > sv_
On 22 Mar 2023, at 17:19, Alex Zetaeffesse wrote:
> For the bridge's interfaces' list, I guess the shorter the output the
> better...
>
> root@pve:~# ovs-vsctl list-ifaces vmbr1
> enp6s0f0
> enp7s0f0
> sv_z1ad0101
> sv_z1ad0102
> sv_z1ad0103
> sv_z1ad0104
> sv_z1ad4064
Use ovs-vsctl show, as it
On 22 Mar 2023, at 14:42, Alex Zetaeffesse wrote:
> I will do my best in describing the goal and the issue
> The ports connected to the bridge (I shrunk the output for readability) are
> the following
>
> root@pve:~# ovs-ofctl show vmbr1
> [CUT]
> 2(sv_z1ad0101): addr:1e:9a:25:9b:22:0a
> 3(sv_
I will do my best in describing the goal and the issue
The ports connected to the bridge (I shrunk the output for readability) are
the following
root@pve:~# ovs-ofctl show vmbr1
[CUT]
2(sv_z1ad0101): addr:1e:9a:25:9b:22:0a
3(sv_z1ad0102): addr:ba:46:f5:b8:4a:63
4(sv_z1ad0103): addr:56:75:a3:a8:
On 3/22/23 10:42, Eelco Chaudron via discuss wrote:
>
>
> On 21 Mar 2023, at 23:42, Alex Zetaeffesse via discuss wrote:
>
>> Hi all,
>>
>> First of all, let me be clear on the fact that I'm the first who doesn't
>> want to run a mixed environment :-)
>>
>> In my ProxMox environment I have the fo
On 22 Mar 2023, at 10:49, Alex Zetaeffesse wrote:
> Thank you Eelco,
>
> the thing is that I'm troubleshooting connectivity issues and the problem
> for the moment seems right in vmbr1.
> Hence I'm trying to understand if vmbr1 works as expected.
For OVS to work the bridge does not need to be u
On 21 Mar 2023, at 23:42, Alex Zetaeffesse via discuss wrote:
> Hi all,
>
> First of all, let me be clear on the fact that I'm the first who doesn't
> want to run a mixed environment :-)
>
> In my ProxMox environment I have the following:
>
> root@pve:~# ip link show dev vmbr1
> 11: vmbr1: mtu
Hi all,
First of all, let me be clear on the fact that I'm the first who doesn't
want to run a mixed environment :-)
In my ProxMox environment I have the following:
root@pve:~# ip link show dev vmbr1
11: vmbr1: mtu 1500 qdisc noqueue state
UNKNOWN mode DEFAULT group default qlen 1000
link/e
On Mon, Oct 28, 2019 at 12:47:21PM +0530, Bhaskar Valaboju wrote:
> Based on documentation and code understanding I was under the impression
> that when a new bridge interface is created using ovs-vsct add-br* command,
> there will be a datapath instance created in kernel. But my understanding
> s
Hello All,
Based on documentation and code understanding I was under the impression
that when a new bridge interface is created using ovs-vsct add-br* command,
there will be a datapath instance created in kernel. But my understanding
seems wrong, there is only one datapath instance created and eac
Hofmann -T (tohofman - AAP3 INC at Cisco)
Subject: Re: [ovs-discuss] Bridge datapath_type gets reset after couple of
reboots
The ovsdb-tool.log shows several bridges being inserted but only one of them
has its datapath_type set to netdev. Is that intentional?
On Thu, Jun 20, 2019 at 11:46:09PM +
s@openvswitch.org; Alex Yeh (ayeh) ; Tobias
> Hofmann -T (tohofman - AAP3 INC at Cisco)
> Subject: Re: [ovs-discuss] Bridge datapath_type gets reset after couple of
> reboots
>
> On Thu, Jun 20, 2019 at 12:34:31AM +, Shriroop Joshi (shrirjos) via
> discuss wrote:
> > I enc
On Thu, Jun 20, 2019 at 12:34:31AM +, Shriroop Joshi (shrirjos) via discuss
wrote:
> I encountered a strange problem with OVS-DPDK. I created a bridge and changed
> its datapath_type to netdev after initializing DPDK.
> After a couple of reboots, it's datapath_type gets reset with DPDK
> ini
On Fri, Dec 07, 2018 at 10:14:48AM +0530, Pranav Godway wrote:
>I want to understand what is meant by a bridge (br0) exactly.
A bridge and a switch are the same thing.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mail
Hi,
I want to understand what is meant by a bridge (br0) exactly.
Regards
Pranav
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
I am using Ubuntu server and the following configuration but sometimes
vmbr0 does not take ip address at all.
so is there any alternative to dhclient?
ovs-vsctl add-br vmbr0
ifconfig vmbr0 up
ovs-vsctl add-bond vmbr0 bond0 enp7s0f0 enp7s0f1 trunks=1529,1530
ovs-vsctl set
...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Steven Pollock
Sent: Thursday, January 04, 2018 11:21 AM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] Bridge not working..
Hopefully this is the correct mailing list, there is no description on the
admin page.
Running on
> On Jan 3, 2018, at 10:51 PM, Steven Pollock wrote:
>
> Hopefully this is the correct mailing list, there is no description on the
> admin page.
>
> Running on Ubuntu 16.04 on top of vmware.
>
> ens192 is connect to the 10.80.180.0/24 network
> ens224 is connected to a standard vswitch4, and
Hopefully this is the correct mailing list, there is no description on the
admin page.
Running on Ubuntu 16.04 on top of vmware.
ens192 is connect to the 10.80.180.0/24 network
ens224 is connected to a standard vswitch4, and a windows machine is also
connected to vswitch4
I expected packets from
I fail with bridging multitagged vlans which brings me in trouble.
May be you can find the fault or solution for ovs
I do have one phy IF ens19 which is a trunk for several vlans.
But I do need only a few on a single iP interface.
Ens19.988
Ens19.988.0
Ens19.988.4090
These three vlans should be
"Stokes, Ian" writes:
>> The mirror-related errors in the log. ovs-tcpdump creates a mirror.
>
> Are there any other errors in the logs? (with a view to figuring out
> why traffic isn't reaching the VMs). Feel free to attach them if
> you're unsure.
>
> Can you provide some more detail with rega
> The mirror-related errors in the log. ovs-tcpdump creates a mirror.
Are there any other errors in the logs? (with a view to figuring out why
traffic isn't reaching the VMs). Feel free to attach them if you're unsure.
Can you provide some more detail with regards to your setup?
OVS release/co
The mirror-related errors in the log. ovs-tcpdump creates a mirror.
On Tue, Dec 06, 2016 at 03:05:32PM -0500, Lax Clarke wrote:
> Pardon? What's caused by ovs-tcpdump??
>
> On Tue, Dec 6, 2016 at 2:17 PM, Ben Pfaff wrote:
>
> > Oh, it's probably caused by ovs-tcpdump, now that I think abo
Pardon? What's caused by ovs-tcpdump??
On Tue, Dec 6, 2016 at 2:17 PM, Ben Pfaff wrote:
> Oh, it's probably caused by ovs-tcpdump, now that I think about it.
>
> On Tue, Dec 06, 2016 at 01:20:19PM -0500, Lax Clarke wrote:
> > I do not think we did.
> >
> > Only config we did:
> >
> > # Subs
Oh, it's probably caused by ovs-tcpdump, now that I think about it.
On Tue, Dec 06, 2016 at 01:20:19PM -0500, Lax Clarke wrote:
> I do not think we did.
>
> Only config we did:
>
> # Subscribers DPDK-based Bridge
> ovs-vsctl add-br flat-br-0 -- set bridge flat-br-0 datapath_type=netdev
> ovs-vsc
I do not think we did.
Only config we did:
# Subscribers DPDK-based Bridge
ovs-vsctl add-br flat-br-0 -- set bridge flat-br-0 datapath_type=netdev
ovs-vsctl add-port flat-br-0 dpdk0 -- set Interface dpdk0 type=dpdk
ovs-vsctl add-port flat-br-0 stack-1-pts-1-subscribers-1 -- set Interface
stack-1-
On Tue, Dec 06, 2016 at 12:20:35PM -0500, Lax Clarke wrote:
> I'm having trouble with 2 OVS bridges I've configured (sitting on top of
> OVS-DPDK):
>
> 2e18698f-9583-4c59-972c-72c2c32cfc7d
> Bridge "flat-br-1"
> Port "stack-1-pts-1-internet-1"
> Interface "stack-1-pts-1-int
Hi,
I'm having trouble with 2 OVS bridges I've configured (sitting on top of
OVS-DPDK):
2e18698f-9583-4c59-972c-72c2c32cfc7d
Bridge "flat-br-1"
Port "stack-1-pts-1-internet-1"
Interface "stack-1-pts-1-internet-1"
type: dpdkvhostuser
Port "flat-br-1"
30 matches
Mail list logo
