 | 1 | initial version |
"don`t fragment flag" itself can't be a reason for performance issues as it allows fragmentation, but don't requires it.
You have to check if there is an actual fragmentation happening on the network (look for Fragmented IP Protocol caption.)
| | 2 | No.2 Revision |
"don`t fragment flag" itself can't be a reason for performance issues as it allows allows fragmentation, but don't requires requires it.
You have to check if there is an actual fragmentation happening on the network (look for Fragmented IP Protocol caption.)caption or apply ip.flags.mf == 1 filter and check whether you observe any packets).
| | 3 | No.3 Revision |
"don`t fragment flag" itself can't be a reason for performance issues as it allows allows fragmentation, but don't requires doesn't require it.
You have to check if there is an actual fragmentation happening on the network (look for Fragmented IP Protocol caption or apply ip.flags.mf == 1 filter and check whether you observe any packets).
| | 4 | No.4 Revision |
"don`t fragment flag" itself can't be a reason for performance issues as it allows fragmentation, but doesn't require it.
You have to check if there is an actual fragmentation happening on the network (look for Fragmented IP Protocol caption or apply ip.flags.mf == 1 filter and check whether you observe any packets).
This is to be checked at the receiver side and may happen of you have some kind of tunneling on the path.
