Issue:
The src-port for UDP is based on RSS hash in the packet metadata.
In case of packets coming from VM it will be 5-tuple, if available,
otherwise just IP addresses.If the VM fragments a large IP packet
and sends the fragments to ovs, only the first fragment will contain
the L4 header. Therefo
Issue:
The src-port for UDP is based on RSS hash in the packet metadata.
In case of packets coming from VM it will be 5-tuple, if available,
otherwise just IP addresses.If the VM fragments a large IP packet
and sends the fragments to ovs, only the first fragment will contain
the L4 header. Therefo
Issue:
The src-port for UDP is based on RSS hash in the packet metadata.
In case of packets coming from VM it will be 5-tuple, if available,
otherwise just IP addresses.If the VM fragments a large IP packet
and sends the fragments to ovs, only the first fragment will contain
the L4 header. Therefo
Issue:
The src-port for UDP is based on RSS hash in the packet metadata.
In case of packets coming from VM it will be 5-tuple, if available,
otherwise just IP addresses.If the VM fragments a large IP packet
and sends the fragments to ovs, only the first fragment will contain
the L4 header. Therefo
Issue:
The src-port for UDP is based on RSS hash in the packet metadata.
In case of packets coming from VM it will be 5-tuple, if available,
otherwise just IP addresses.If the VM fragments a large IP packet
and sends the fragments to ovs, only the first fragment will contain
the L4 header. Therefo
Issue:
The src-port for UDP is based on RSS hash in the packet metadata.
In case of packets coming from VM it will be 5-tuple, if available,
otherwise just IP addresses.If the VM fragments a large IP packet
and sends the fragments to ovs, only the first fragment will contain
the L4 header. Therefo
Issue:
The src-port for UDP is based on RSS hash in the packet metadata.
In case of packets coming from VM it will be 5-tuple, if available,
otherwise just IP addresses. If the VM fragments a large IP packet
and sends the fragments to OVS, only the first fragment will contain
the L4 header. Theref
On 1/12/21 10:50 AM, Parvathy Tarur Ramachandran via dev wrote:
> Issue:
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> otherwise just IP addresses. If the VM fragments a large IP packet
> and sends the fra
Normally, VXLAN packets will be set to DF( don't frag) in the outter IP
header.
I am trying to understand why fragmentation happens in the first place.
Hemanth Aramadaka via dev 于2022年3月15日周二 22:38写道：
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of pac
,
Hemanth.
From: Peng He
Sent: 16 March 2022 11:30
To: Hemanth Aramadaka
Cc: Sriharsha Basavapatna via dev ; Ilya Maximets
Subject: Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
fragmented packets
Normally, VXLAN packets will be set to DF( don't frag) in the outt
encapsulated with vxlan
> header in which we have the different source ports for UDP.
>
>
>
> Thanks,
>
> Hemanth.
>
>
>
> *From:* Peng He
> *Sent:* 16 March 2022 11:30
> *To:* Hemanth Aramadaka
> *Cc:* Sriharsha Basavapatna via dev ; Ilya
> Maximets
&g
Hi Peng,
Could you please review the below request.
Thanks,
Hemanth.
From: Peng He
Sent: 08 April 2022 07:50
To: Hemanth Aramadaka
Cc: Sriharsha Basavapatna via dev ; Ilya Maximets
Subject: Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
fragmented packets
got
From:* Peng He
> *Sent:* 08 April 2022 07:50
> *To:* Hemanth Aramadaka
> *Cc:* Sriharsha Basavapatna via dev ; Ilya
> Maximets
> *Subject:* Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
> fragmented packets
>
>
>
> got it. thanks!
>
>
>
>>
>>
>>
>> Could you please review the below request.
>>
>>
>>
>> Thanks,
>>
>> Hemanth.
>>
>>
>>
>> *From:* Peng He
>> *Sent:* 08 April 2022 07:50
>> *To:* Hemanth Aramadaka
>> *Cc:* Srihars
Hi Peng,
Did the changes got merged ?
Thanks,
Hemanth
From: Peng He
Sent: 09 May 2022 09:09
To: Hemanth Aramadaka
Cc: Sriharsha Basavapatna via dev ; Ilya Maximets
Subject: Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
fragmented packets
sorry, ack name is
Aramadaka
> *Cc:* Sriharsha Basavapatna via dev ; Ilya
> Maximets
> *Subject:* Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
> fragmented packets
>
>
>
> sorry, ack name is wrong:
>
>
>
> Acked-by: Peng He
>
>
>
> Peng He 于202
On 3/15/22 15:30, Hemanth Aramadaka wrote:
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> otherwise just IP addresses.If the VM fragments a large IP packet
> and sends the fragments to ovs, only
On 11/3/22 13:11, Hemanth Aramadaka via dev wrote:
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> otherwise just IP addresses.If the VM fragments a large IP packet
> and sends the fragments to o
.dir -name 'ubsan.*')" &&
\
test X'' = Xyes && "$@" --recheck)
Illegal "police"
## -------------- ##
## openvswitch 3.0.90 test suite. ##
## -- ##
796: tunnel_push_pop - packet_out debug_slow
nd /home/sdn/zarahem/ovs/tests/testsuite.dir -name 'ubsan.*')"
> && \
> test X'' = Xyes && "$@" --recheck)
> Illegal "police"
> ## -- ##
> ## openvswitch 3.0.90 test suite. ##
> ## -
On 11/4/22 13:58, Hemanth Aramadaka via dev wrote:
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> otherwise just IP addresses.If the VM fragments a large IP packet
> and sends the fragments to o
On 11/4/22 14:43, Hemanth Aramadaka via dev wrote:
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> otherwise just IP addresses.If the VM fragments a large IP packet
> and sends the fragments to o
On 12/2/22 13:55, Hemanth Aramadaka via dev wrote:
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> otherwise just IP addresses.If the VM fragments a large IP packet
> and sends the fragments to o
VXLAN UDP src ports for
fragmented packets
On Thu, Jan 05, 2023 at 06:55:03PM +0530, Hemanth Aramadaka via dev wrote:
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> ot
anuary 20, 2023 8:52 PM
> To: ovs-dev@openvswitch.org
> Cc: Hemanth Aramadaka
> Subject: Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
> fragmented packets
>
> On Thu, Jan 05, 2023 at 06:55:03PM +0530, Hemanth Aramadaka via dev wrote:
>> Issue:
>>
>
; 'Simon Horman'
; ovs-dev@openvswitch.org
Cc: i.maxim...@ovn.org
Subject: Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
fragmented packets
On 6/26/23 08:59, Hemanth Aramadaka via dev wrote:
> Hi Simon,
>
> Sorry for the late response. Yes, the changes a
orman'
> ; ovs-dev@openvswitch.org
> Cc: i.maxim...@ovn.org
> Subject: Re: [ovs-dev] [PATCH] flow: Consistent VXLAN UDP src ports for
> fragmented packets
>
> On 6/26/23 08:59, Hemanth Aramadaka via dev wrote:
>> Hi Simon,
>>
>> Sorry for the late response. Yes,
On Thu, Jan 05, 2023 at 06:55:03PM +0530, Hemanth Aramadaka via dev wrote:
> Issue:
>
> The src-port for UDP is based on RSS hash in the packet metadata.
> In case of packets coming from VM it will be 5-tuple, if available,
> otherwise just IP addresses.If the VM fragments a large IP packet
> and
28 matches
Mail list logo
