Re: [PATCH ipsec/vti 0/2] Fragmentation of IPv4 in VTI

2019-03-22 Thread Bram Yvahk
Bram Yvahk wrote: > Steffen Klassert wrote: >> On Sun, Mar 17, 2019 at 11:37:55PM +, Bram Yvahk wrote: >>> We've experienced an issue with VTI when the path-mtu is smaller than > the size >>> of the "client" packet. >>> >>> What happens: IPv4 packet from the client (i.e. another system in the >

Re: [PATCH ipsec/vti 0/2] Fragmentation of IPv4 in VTI

2019-03-21 Thread Bram Yvahk
Steffen Klassert wrote: > On Sun, Mar 17, 2019 at 11:37:55PM +, Bram Yvahk wrote: >> We've experienced an issue with VTI when the path-mtu is smaller than the size >> of the "client" packet. >> >> What happens: IPv4 packet from the client (i.e. another system in the LAN) >> attempts to transmit

Re: [PATCH ipsec/vti 0/2] Fragmentation of IPv4 in VTI

2019-03-21 Thread Steffen Klassert
On Sun, Mar 17, 2019 at 11:37:55PM +, Bram Yvahk wrote: > We've experienced an issue with VTI when the path-mtu is smaller than the size > of the "client" packet. > > What happens: IPv4 packet from the client (i.e. another system in the LAN) > attempts to transmit some data; IPv4 header shows

[PATCH ipsec/vti 0/2] Fragmentation of IPv4 in VTI

2019-03-17 Thread Bram Yvahk
We've experienced an issue with VTI when the path-mtu is smaller than the size of the "client" packet. What happens: IPv4 packet from the client (i.e. another system in the LAN) attempts to transmit some data; IPv4 header shows that 'DF' bit is not set but still the client receives ICMPv4 "need-to