Hi,
I would like to confirm whether Veeam explicitly sets the DF (Don't Fragment) bit in its network communication.
Is there any processing in the following products that sets the DF bit?
- Veeam Backup & Replication 13
- Veeam Agent for Linux 13
- Veeam Agent for Microsoft Windows 13
Or does Veeam rely entirely on the OS/network stack behavior without controlling the DF flag?
Thanks,
Rin
-
rin
- Influencer
- Posts: 24
- Liked: 3 times
- Joined: Jun 24, 2025 6:40 am
- Full Name: Rintaro Tamura
- Contact:
-
vnikiforov
- Veeam Software
- Posts: 137
- Liked: 46 times
- Joined: Aug 17, 2022 5:03 am
- Full Name: Vladimir Nikiforov
- Location: Romania
- Contact:
Re: Does Veeam set the DF (Don't Fragment) bit?
Hello, Rin,
The DF (Don't Fragment) flag is an IPv4 header parameter (OSI model layers 4 and 3), it is managed by the OS kernel IP layer.
Veeam applications don't perform low-level or kernel-level IP stack actions.
The DF (Don't Fragment) flag is an IPv4 header parameter (OSI model layers 4 and 3), it is managed by the OS kernel IP layer.
Veeam applications don't perform low-level or kernel-level IP stack actions.
---
BR,
Vladimir
Veeam Software
BR,
Vladimir
Veeam Software
-
rin
- Influencer
- Posts: 24
- Liked: 3 times
- Joined: Jun 24, 2025 6:40 am
- Full Name: Rintaro Tamura
- Contact:
Re: Does Veeam set the DF (Don't Fragment) bit?
Hi, vnikiforov,
Thank you for the clarification.
I understand that the DF flag is managed by the OS/network stack and that Veeam does not explicitly control or configure it. This answers my question.
Thank you for your assistance.
Best regards,
Rin
Thank you for the clarification.
I understand that the DF flag is managed by the OS/network stack and that Veeam does not explicitly control or configure it. This answers my question.
Thank you for your assistance.
Best regards,
Rin
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 60 guests