Re: [ovs-dev] [PATCH] tunnel: Do not carry source port from a previous tunnel.

2023-12-05 Thread Ilya Maximets
On 12/4/23 16:24, Eelco Chaudron wrote: > > > On 1 Dec 2023, at 22:04, Ilya Maximets wrote: > >> If a packet is received from a UDP tunnel, it has a source port >> populated in the tunnel metadata. This field cannot be read or >> changed with OpenFlow or the tunnel configuration. However,

Re: [ovs-dev] [PATCH] tunnel: Do not carry source port from a previous tunnel.

2023-12-04 Thread Eelco Chaudron
On 1 Dec 2023, at 22:04, Ilya Maximets wrote: > If a packet is received from a UDP tunnel, it has a source port > populated in the tunnel metadata. This field cannot be read or > changed with OpenFlow or the tunnel configuration. However, while > sending this packet to a different tunnel,

Re: [ovs-dev] [PATCH] tunnel: Do not carry source port from a previous tunnel.

2023-12-02 Thread Vladislav Odintsov
Hi Ilya, thanks for the patch! I’ve validated it against my setup with geneve tunnels hairpin. With [0] applied, tc offloading works as expected: no warnings/errors in ovs-vswitchd.log, and only first packets of a flow reach system/CPU/are visible in tcpdump. Also, ovs-appctl dpctl/dump-flows

[ovs-dev] [PATCH] tunnel: Do not carry source port from a previous tunnel.

2023-12-01 Thread Ilya Maximets
If a packet is received from a UDP tunnel, it has a source port populated in the tunnel metadata. This field cannot be read or changed with OpenFlow or the tunnel configuration. However, while sending this packet to a different tunnel, the value remains in the metadata and is being sent to the