Hey all,
Is there a way I can encapsulate a packet with VXLAN, and then resubmit it
through OVS again to run other flow actions based on this encapsulated packet?
Currently, I have a OVS-DPDK setup where in the final step, before a packet
leaves the host, the group action is used to pick betwee
On 1/25/24 10:42, Lim, Derrick via discuss wrote:
> Hey all,
>
> Is there a way I can encapsulate a packet with VXLAN, and then resubmit
> it through OVS again to run other flow actions based on this encapsulated
> packet?
>
> Currently, I have a OVS-DPDK setup where in the final step, before a p
ck | Derrick | CMD ,
ovs-discuss@openvswitch.org
Cc: i.maxim...@ovn.org
Subject: Re: [ovs-discuss] Encapsulate VXLAN and then process other flows
[EXTERNAL] This message comes from an external organization.
On 1/25/24 10:42, Lim, Derrick via discuss wrote:
> Hey all,
>
> Is there a way I can enca
(0x0806),arp(sip=192.168.1.34/0.0.0.0,tip=192.168.1.33/0.0.0.0,op=1/0,sha=52:54:00:3d:cd:0c/00:00:00:00:00:00,tha=00:00:00:00:00:00/00:00:00:00:00:00),
> packets:5, bytes:210, used:0.447s, dp:ovs, actions:drop,
> dp-extra-info:miniflow_bits(4,0)
>
> Thank you,
> Derrick
>
>
g
Cc: i.maxim...@ovn.org
Subject: Re: [ovs-discuss] Encapsulate VXLAN and then process other flows
[EXTERNAL] This message comes from an external organization.
On 1/26/24 09:37, Lim, Derrick wrote:
> Hi Ilya Maximets,
>
> Thank you for explanation. I've create the two bridges, but the p
iscuss
Date: Monday, January 29, 2024 at 11:19
To: Ilya Maximets , ovs-discuss@openvswitch.org
Cc: i.maxim...@ovn.org
Subject: Re: [ovs-discuss] Encapsulate VXLAN and then process other flows
[EXTERNAL] This message comes from an external organization.
Hi Ilya Maximets,
Thank you for looking i
2412ac443e/lib/ovs-router.c#L285C1-L290C6
>
> How should I be writing the flow entry on br-phy to rewrite the source IP?
> I think this would be my preferred approach intead of adding static ARP/route
> entries since it gives me more flexibility.
The rules look mostly fine. I think the ma
Hi Ilya Maximets,
Thank you for the guidance on where to make the code changes.
About the the source address issue, I'm on ovs version "3.1.1" that came with
FC38.
I'll build and try this again with OVS 3.2.
Thank you,
Derrick
___
discuss mailing list
Hi Ilya Maximets,
> The rules look mostly fine. I think the main problem you have is priority.
> Default priority for OF rules (if not specified) is 32768, so your new rules
> with priority 50 are too low in a priority list and not getting hit.
I tried this again with the default flow at pr
On 2/2/24 08:58, Lim, Derrick via discuss wrote:
> Hi Ilya Maximets,
>
>> The rules look mostly fine. I think the main problem you have is priority.
>> Default priority for OF rules (if not specified) is 32768, so your new rules
>> with priority 50 are too low in a priority list and not getting h
(vid=304,pcp=0),exit_p0
===
# VXLAN interface on bridge configuration
===
Port vxlan0
Interface vxlan0
type: vxlan
options: {dst_port="4789", key="1",
local_ip="2403:400:31da:::18:6", remote_ip="2403:400:31da:::18:3"}
===
lan(flags=0x800,vni=0x1)),out_port(br-phy)),push_vlan(vid=304,pcp=0),exit_p0
> ===
>
> # VXLAN interface on bridge configuration
> ===
> Port vxlan0
> Interface vxlan0
> type: vxlan
> options: {dst_port="4789", key="1"
>NXM_NX_IPV6_SRC[64..127]
>> NORMAL
>> -> forwarding to learned port
>>
>> Final flow: unchanged
>> Megaflow: recirc_id=0,eth,ip,in_port="dpdk-vm101",nw_ecn=0,nw_frag=no
>> Datapath actions:
>> tnl_push(tnl_port(vxlan_sys_4789),header(si
13 matches
Mail list logo
