diff options
| author | Jon Maloy <jmaloy@redhat.com> | 2025-02-19 10:20:41 -0500 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2025-02-20 12:43:00 +0100 |
| commit | ea69ca6a20ac7408a913fd5de383a5383d679678 (patch) | |
| tree | 3b5e58d10d156f9ac8c013ffa9c60f4eebfdda87 /contrib/qemu/git: | |
| parent | 4dac2351fae5534c01e144273f849ce9ece0dca7 (diff) | |
| download | passt-ea69ca6a20ac7408a913fd5de383a5383d679678.tar passt-ea69ca6a20ac7408a913fd5de383a5383d679678.tar.gz passt-ea69ca6a20ac7408a913fd5de383a5383d679678.tar.bz2 passt-ea69ca6a20ac7408a913fd5de383a5383d679678.tar.lz passt-ea69ca6a20ac7408a913fd5de383a5383d679678.tar.xz passt-ea69ca6a20ac7408a913fd5de383a5383d679678.tar.zst passt-ea69ca6a20ac7408a913fd5de383a5383d679678.zip | |
tap: always set the no_frag flag in IPv4 headers
When studying the Linux source code and Wireshark dumps it seems like
the no_frag flag in the IPv4 header is always set. Following discussions
in the Internet on this subject indicates that modern routers never
fragment packets, and that it isn't even supported in many cases.
Adding to this that incoming messages forwarded on the tap interface
never even pass through a router it seems safe to always set this flag.
This makes the IPv4 headers of forwarded messages identical to those
sent by the external sockets, something we must consider desirable.
Signed-off-by: Jon Maloy <jmaloy@redhat.com>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'contrib/qemu/git:')
0 files changed, 0 insertions, 0 deletions