Hi Ben,
Checked out the function format_odp_key_attr(), it has the correct parameters
in form of struct ds->string. This string shows correct set of tunnelling
params. But we need to do parsing in dpif class. Can you suggest how can we do
this? Looks like we aren't doing the correct netlink par
Also, just make sure you did not terminate ovs by 'kill' it, since that way,
the opened tap interfaces are not removed and could cause errors when
you restart ovs.
Thanks,
Alex Wang,
On Tue, Feb 24, 2015 at 3:35 PM, Atanu Ghosh wrote:
> Hi,
>
> If SIOCSIFNAME is used to change the name of the t
Hi,
If SIOCSIFNAME is used to change the name of the tap interface it seems to
work on FreeBSD 10.1:
ovs-netdev: flags=ffdc8802
metric 0 mtu 1500
options=8
ether 00:bd:43:48:02:00
nd6 options=21
media: Ethernet autoselect
status: no carrier
br0: flags=ffdc8802 metric 0
mtu
Sorry for the slow response.
The answer is to add more decoding at the collector. You could refer to
the "sflowtool" source code for a simple example.
The "struct sampled_ipv4" record (flow sample type 0:3) is only there in
case there is a device somewhere that has that decoded information, bu
According to
https://www.freebsd.org/cgi/man.cgi?query=tap&apropos=0&sektion=4&manpath=FreeBSD+9.3-RELEASE&arch=default&format=html
it seems that freebsd does not support setting SIOCSIFNAME for tap
interfaces.
I think I'll just remove the code in ovs.
Thanks,
Alex Wang,
On Tue, Feb 24, 2015 at
> -Original Message-
> From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of
> IñakiMurillo
> Sent: Tuesday, February 24, 2015 4:42 PM
> To: discuss@openvswitch.org
> Subject: [ovs-discuss] Fwd: Doubt: QEMU <-> OVS using DPDK
>
>
>
> Hello,
>
> I am trying to connect a vi
Have you looked at the code in odp-util.c that prints these
structures, e.g. format_odp_key_attr()?
On Tue, Feb 24, 2015 at 05:00:31PM +, Chetan Bali wrote:
> Hi Ben,
>
> Thanks for the quick response. Please find the code snippet below:
>
> This below function is called from flow_put in dpi
Okay, could you show me the ovs-vswitchd.log?
Usually, there should be some messages explaining the error.
Thanks,
Alex Wang,
On Tue, Feb 24, 2015 at 9:33 AM, Atanu Ghosh wrote:
> Hi,
>
> It seems to be loaded:
>
> k3$ kldstat | grep if_tap
> 131 0x81b93000 5584 if_tap.ko
>
>
Hi,
It seems to be loaded:
k3$ kldstat | grep if_tap
131 0x81b93000 5584 if_tap.ko
Atanu.
On Tue, Feb 24, 2015 at 9:29 AM, Alex Wang wrote:
> Hey,
>
> I think you need to load the 'if_tap.ko'~
>
> Thanks,
> Alex Wang,
>
> On Mon, Feb 23, 2015 at 3:29 PM, Atanu Ghosh w
Hey,
I think you need to load the 'if_tap.ko'~
Thanks,
Alex Wang,
On Mon, Feb 23, 2015 at 3:29 PM, Atanu Ghosh wrote:
> Hi,
>
> The code in the master branch now passes all the tests on FreeBSD 10.1.
> However, I still see the same errors when trying to create a bridge.
> Setting the datapath
Hi,
The code in the master branch now passes all the tests on FreeBSD 10.1.
However, I still see the same errors when trying to create a bridge.
Setting the datapath type to netdev doesn't seem to help the situation.
Atanu.
On Fri, Feb 20, 2015 at 2:32 PM, Alex Wang wrote:
> Hey Atanu,
Didn’t find how to gracefully restart vswitchd (no init script). After
rebooting the hypervisor, it’s gone. I tried adding a new switch and set the dp
type at creation and it still works.
root@pve:~# ovs-vsctl add-br vmbr2 -- set bridge vmbr2 datapath_type=netdev
root@pve:~# ovs-ofctl show vmbr2
Hi Ben,
Just reproduced it. Booted back to kernel 3.10.0-7 (it’s proxmox) and after
setting the switch as netdev, the error appears again. the log does not get
updated when I run a command like “ovs-ofctl show vmbr1” but it got populated
when I turned the switch to “netdev” device (logs below).
sorry for the delay,
libvirt version is 1.2.2
ovs_version: "2.0.2"
i'm installing it through Virt-manager.
xml file is
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made
using:
virsh edit 1511_secondary
o
Nope. That’s the whole thing AFTER I set the ‘netdev’ switch:
2015-02-22T20:39:05.099Z|00018|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath
supports recirculation
2015-02-22T20:39:05.099Z|00019|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS label
stack length probed as 3
2015-02-22T20:39:05
Hi Ben,
Thanks for the quick response. Please find the code snippet below:
This below function is called from flow_put in dpif class code.
uint8_t dpif_tunnel_parse_actions(s_action_t *action_list, const struct nlattr
*actions, size_t actions_len, struct flow_tnl *tun_param)
{
if(OVS_LIKELY(NUL
On Tue, Feb 24, 2015 at 01:33:29PM +, Chetan Bali wrote:
> I am configuring gre-port in my ovs bridge, for establishing gre-tunnel
> between 2 machines. I am trying to parse the tunnelling key params sent by
> OVS while adding flow, when it sets action as OVS_ACTION_ATTR_SET. I am
> parsing
Hello,
I am trying to connect a virtual machine with a openvswitch using DPDK
for performance, as you can see in the next figure.
+---+
| QMEU VM |
| |
|
Hi,
I am configuring gre-port in my ovs bridge, for establishing gre-tunnel between
2 machines. I am trying to parse the tunnelling key params sent by OVS while
adding flow, when it sets action as OVS_ACTION_ATTR_SET. I am parsing the
tun-key attributes in dpif-linux.c in exact manner as ovs do
19 matches
Mail list logo
