Trouble enabling Jumbo Frames?Link Aggregation And Jumbo Frames configured but not workingJumbo Frames, ISCSI...
What happens if a wizard reaches level 20 but has no 3rd-level spells that they can use with the Signature Spells feature?
Has the Isbell–Freyd criterion ever been used to check that a category is concretisable?
Proof by Induction - New to proofs
Meaning of すきっとした
How to add multiple differently colored borders around a node?
Is my plan for fixing my water heater leak bad?
Where was Karl Mordo in Infinity War?
Why does the DC-9-80 have this cusp in its fuselage?
Can chords be played on the flute?
Is Draco canonically good-looking?
Obtaining a matrix of complex values from associations giving the real and imaginary parts of each element?
It took me a lot of time to make this, pls like. (YouTube Comments #1)
How to properly claim credit for peer review?
Can a hotel cancel a confirmed reservation?
How do Japanese speakers determine the implied topic when none has been mentioned?
raspberry pi change directory (cd) command not working with USB drive
Is the theory of the category of topological spaces computable?
If all harmonics are generated by plucking, how does a guitar string produce a pure frequency sound?
If a druid in Wild Shape swallows a creature whole, then turns back to her normal form, what happens?
Removing debris from PCB
Why is c4 a better move in this position?
Where is this triangular-shaped space station from?
If I delete my router's history can my ISP still provide it to my parents?
How to define a macro with multiple optional parameters?
Trouble enabling Jumbo Frames?
Link Aggregation And Jumbo Frames configured but not workingJumbo Frames, ISCSI and ESXiServer 2012, Jumbo Frames - should I expect problems?Issue with Netgear GS108T Managed Switch and Jumbo FramesJumbo frames between KVM guest and host?Enabling jumbo frames on switch but not on devices: looking for trouble?Jumbo Frame configuration & VMwareMixing jumbo frames on Vsphere 5 ISCSI networkFull MTU not utilized with jumbo frames enabledVMWare - Jumbo Frames over iSCSI to a NAS4Free array
I'm trying to enable jumbo frames. I have a linux client & a windows server. I've standardized across the board on intel nics. On the windows server the only choice for jumbo frames is 9014 & 4088. I've researched on whether I should set the MTU speed in linux to 9014 or 9000. There has been conflicting posts googling around but it seems like probably 9000 is the correct number. I, of course, have tried both though.
Going off of this site i tried to test if everything was working correctly. From my linux client: ping -M do -s 8972 [destinationIP] everything seems to be working correctly:
8980 bytes from file ([destinationIP]): icmp_seq=1 ttl=128 time=0.946 ms
8980 bytes from file ([destinationIP]): icmp_seq=2 ttl=128 time=1.16 ms
8980 bytes from file ([destinationIP]): icmp_seq=3 ttl=128 time=1.02 ms
8980 bytes from file ([destinationIP]): icmp_seq=5 ttl=128 time=0.935 ms
but when it tried testing from the windows side: ping -f -l 9000 [destinationIP]
Pinging <linux client> with 9000 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
After googling around i seen conflicting post on what size you should use when pinging from windows. So i tried 8972 (9000-28) but it times out and i get no response. I even tried 8986 (9014-28) but i get the fragmented error. I thought it was an issue between windows/linux but when i tried pinging other windows server (jumbo frames is on for every server) i get the same issue. I found out that when i hit 8972 it started timing out and from 9014 to 8973 i get the fragmented error. So my questions are:
- In linux is
9000the correct MTU speed to use (because of the difference between linux & windows) or is9014? - Anyone know why i'm getting these
fragmentederrors from the windows side & it appears from the linux side everything is ok?
Here is my switch which clearly supports jumbo frames up to 9216
linux windows ethernet gigabit-ethernet jumboframes
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
add a comment |
I'm trying to enable jumbo frames. I have a linux client & a windows server. I've standardized across the board on intel nics. On the windows server the only choice for jumbo frames is 9014 & 4088. I've researched on whether I should set the MTU speed in linux to 9014 or 9000. There has been conflicting posts googling around but it seems like probably 9000 is the correct number. I, of course, have tried both though.
Going off of this site i tried to test if everything was working correctly. From my linux client: ping -M do -s 8972 [destinationIP] everything seems to be working correctly:
8980 bytes from file ([destinationIP]): icmp_seq=1 ttl=128 time=0.946 ms
8980 bytes from file ([destinationIP]): icmp_seq=2 ttl=128 time=1.16 ms
8980 bytes from file ([destinationIP]): icmp_seq=3 ttl=128 time=1.02 ms
8980 bytes from file ([destinationIP]): icmp_seq=5 ttl=128 time=0.935 ms
but when it tried testing from the windows side: ping -f -l 9000 [destinationIP]
Pinging <linux client> with 9000 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
After googling around i seen conflicting post on what size you should use when pinging from windows. So i tried 8972 (9000-28) but it times out and i get no response. I even tried 8986 (9014-28) but i get the fragmented error. I thought it was an issue between windows/linux but when i tried pinging other windows server (jumbo frames is on for every server) i get the same issue. I found out that when i hit 8972 it started timing out and from 9014 to 8973 i get the fragmented error. So my questions are:
- In linux is
9000the correct MTU speed to use (because of the difference between linux & windows) or is9014? - Anyone know why i'm getting these
fragmentederrors from the windows side & it appears from the linux side everything is ok?
Here is my switch which clearly supports jumbo frames up to 9216
linux windows ethernet gigabit-ethernet jumboframes
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
Welcome to a world without a standard (the ethernet standard is still a 1500 octet MTU, and there is no standard for jumbo frames). Also, make sure you never try to send jumbo frames over the public Internet. The jumbo frames would need to be fragmented, but fragments are probably not allowed at the destination by smart engineers because of the fragment DoS attacks.
– Ron Maupin
11 hours ago
add a comment |
I'm trying to enable jumbo frames. I have a linux client & a windows server. I've standardized across the board on intel nics. On the windows server the only choice for jumbo frames is 9014 & 4088. I've researched on whether I should set the MTU speed in linux to 9014 or 9000. There has been conflicting posts googling around but it seems like probably 9000 is the correct number. I, of course, have tried both though.
Going off of this site i tried to test if everything was working correctly. From my linux client: ping -M do -s 8972 [destinationIP] everything seems to be working correctly:
8980 bytes from file ([destinationIP]): icmp_seq=1 ttl=128 time=0.946 ms
8980 bytes from file ([destinationIP]): icmp_seq=2 ttl=128 time=1.16 ms
8980 bytes from file ([destinationIP]): icmp_seq=3 ttl=128 time=1.02 ms
8980 bytes from file ([destinationIP]): icmp_seq=5 ttl=128 time=0.935 ms
but when it tried testing from the windows side: ping -f -l 9000 [destinationIP]
Pinging <linux client> with 9000 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
After googling around i seen conflicting post on what size you should use when pinging from windows. So i tried 8972 (9000-28) but it times out and i get no response. I even tried 8986 (9014-28) but i get the fragmented error. I thought it was an issue between windows/linux but when i tried pinging other windows server (jumbo frames is on for every server) i get the same issue. I found out that when i hit 8972 it started timing out and from 9014 to 8973 i get the fragmented error. So my questions are:
- In linux is
9000the correct MTU speed to use (because of the difference between linux & windows) or is9014? - Anyone know why i'm getting these
fragmentederrors from the windows side & it appears from the linux side everything is ok?
Here is my switch which clearly supports jumbo frames up to 9216
linux windows ethernet gigabit-ethernet jumboframes
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
I'm trying to enable jumbo frames. I have a linux client & a windows server. I've standardized across the board on intel nics. On the windows server the only choice for jumbo frames is 9014 & 4088. I've researched on whether I should set the MTU speed in linux to 9014 or 9000. There has been conflicting posts googling around but it seems like probably 9000 is the correct number. I, of course, have tried both though.
Going off of this site i tried to test if everything was working correctly. From my linux client: ping -M do -s 8972 [destinationIP] everything seems to be working correctly:
8980 bytes from file ([destinationIP]): icmp_seq=1 ttl=128 time=0.946 ms
8980 bytes from file ([destinationIP]): icmp_seq=2 ttl=128 time=1.16 ms
8980 bytes from file ([destinationIP]): icmp_seq=3 ttl=128 time=1.02 ms
8980 bytes from file ([destinationIP]): icmp_seq=5 ttl=128 time=0.935 ms
but when it tried testing from the windows side: ping -f -l 9000 [destinationIP]
Pinging <linux client> with 9000 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
After googling around i seen conflicting post on what size you should use when pinging from windows. So i tried 8972 (9000-28) but it times out and i get no response. I even tried 8986 (9014-28) but i get the fragmented error. I thought it was an issue between windows/linux but when i tried pinging other windows server (jumbo frames is on for every server) i get the same issue. I found out that when i hit 8972 it started timing out and from 9014 to 8973 i get the fragmented error. So my questions are:
- In linux is
9000the correct MTU speed to use (because of the difference between linux & windows) or is9014? - Anyone know why i'm getting these
fragmentederrors from the windows side & it appears from the linux side everything is ok?
Here is my switch which clearly supports jumbo frames up to 9216
linux windows ethernet gigabit-ethernet jumboframes
linux windows ethernet gigabit-ethernet jumboframes
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
asked Feb 18 at 5:06
coding4funcoding4fun
2171510
2171510
Welcome to a world without a standard (the ethernet standard is still a 1500 octet MTU, and there is no standard for jumbo frames). Also, make sure you never try to send jumbo frames over the public Internet. The jumbo frames would need to be fragmented, but fragments are probably not allowed at the destination by smart engineers because of the fragment DoS attacks.
– Ron Maupin
11 hours ago
add a comment |
Welcome to a world without a standard (the ethernet standard is still a 1500 octet MTU, and there is no standard for jumbo frames). Also, make sure you never try to send jumbo frames over the public Internet. The jumbo frames would need to be fragmented, but fragments are probably not allowed at the destination by smart engineers because of the fragment DoS attacks.
– Ron Maupin
11 hours ago
Welcome to a world without a standard (the ethernet standard is still a 1500 octet MTU, and there is no standard for jumbo frames). Also, make sure you never try to send jumbo frames over the public Internet. The jumbo frames would need to be fragmented, but fragments are probably not allowed at the destination by smart engineers because of the fragment DoS attacks.
– Ron Maupin
11 hours ago
Welcome to a world without a standard (the ethernet standard is still a 1500 octet MTU, and there is no standard for jumbo frames). Also, make sure you never try to send jumbo frames over the public Internet. The jumbo frames would need to be fragmented, but fragments are probably not allowed at the destination by smart engineers because of the fragment DoS attacks.
– Ron Maupin
11 hours ago
add a comment |
1 Answer
1
active
oldest
votes
You need to distinguish:
- Ethernet maximum frame size: needs to take Ethernet L2 overhead into account, normally 18 bytes - standard is 1518 bytes untagged
- IP MTU: this is what you usually aim for - standard over Ethernet is 1500 bytes, jumbos often use 9000
- maximum
pingpayload for testing: ping uses ICMP (8 bytes overhead) over IPv4 (20 bytes overhead) - so the maximum unfragmented ping payload length is 1472 bytes (MTU 1500) or 8972 bytes (MTU 9000)
For testing path MTU you need to send echo requests with the DF bit set. This is accomplished in Windows by -f and in Linux by -M prohibit. Your -M do *explicitly enables fragmentation. When testing the "Packet needs to be fragmented but DF set" shows the source machine to lack the correct setup. When the ping times out, the destination or something in between isn't working. Switches usually have a counter for oversized frames.
Setting the switch to a somewhat larger maximum frame size than necessary isn't hurtful. However, do make sure your end nodes and routers are all set to the exact same size: 9000 when setting the MTU or 9018 when setting the max L2 PDU/frame size.
Intel's Jumbo Packet setting is somewhat misleading. The help text shows that the FCS (4 bytes) isn't counted, so 9014 is the correct setting for MTU 9000 frames.
answered 11 hours ago
Zac67Zac67
3,9732415
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f954433%2ftrouble-enabling-jumbo-frames%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to distinguish:
- Ethernet maximum frame size: needs to take Ethernet L2 overhead into account, normally 18 bytes - standard is 1518 bytes untagged
- IP MTU: this is what you usually aim for - standard over Ethernet is 1500 bytes, jumbos often use 9000
- maximum
pingpayload for testing: ping uses ICMP (8 bytes overhead) over IPv4 (20 bytes overhead) - so the maximum unfragmented ping payload length is 1472 bytes (MTU 1500) or 8972 bytes (MTU 9000)
For testing path MTU you need to send echo requests with the DF bit set. This is accomplished in Windows by -f and in Linux by -M prohibit. Your -M do *explicitly enables fragmentation. When testing the "Packet needs to be fragmented but DF set" shows the source machine to lack the correct setup. When the ping times out, the destination or something in between isn't working. Switches usually have a counter for oversized frames.
Setting the switch to a somewhat larger maximum frame size than necessary isn't hurtful. However, do make sure your end nodes and routers are all set to the exact same size: 9000 when setting the MTU or 9018 when setting the max L2 PDU/frame size.
Intel's Jumbo Packet setting is somewhat misleading. The help text shows that the FCS (4 bytes) isn't counted, so 9014 is the correct setting for MTU 9000 frames.
answered 11 hours ago
Zac67Zac67
3,9732415
add a comment |
You need to distinguish:
- Ethernet maximum frame size: needs to take Ethernet L2 overhead into account, normally 18 bytes - standard is 1518 bytes untagged
- IP MTU: this is what you usually aim for - standard over Ethernet is 1500 bytes, jumbos often use 9000
- maximum
pingpayload for testing: ping uses ICMP (8 bytes overhead) over IPv4 (20 bytes overhead) - so the maximum unfragmented ping payload length is 1472 bytes (MTU 1500) or 8972 bytes (MTU 9000)
For testing path MTU you need to send echo requests with the DF bit set. This is accomplished in Windows by -f and in Linux by -M prohibit. Your -M do *explicitly enables fragmentation. When testing the "Packet needs to be fragmented but DF set" shows the source machine to lack the correct setup. When the ping times out, the destination or something in between isn't working. Switches usually have a counter for oversized frames.
Setting the switch to a somewhat larger maximum frame size than necessary isn't hurtful. However, do make sure your end nodes and routers are all set to the exact same size: 9000 when setting the MTU or 9018 when setting the max L2 PDU/frame size.
Intel's Jumbo Packet setting is somewhat misleading. The help text shows that the FCS (4 bytes) isn't counted, so 9014 is the correct setting for MTU 9000 frames.
answered 11 hours ago
Zac67Zac67
3,9732415
add a comment |
You need to distinguish:
- Ethernet maximum frame size: needs to take Ethernet L2 overhead into account, normally 18 bytes - standard is 1518 bytes untagged
- IP MTU: this is what you usually aim for - standard over Ethernet is 1500 bytes, jumbos often use 9000
- maximum
pingpayload for testing: ping uses ICMP (8 bytes overhead) over IPv4 (20 bytes overhead) - so the maximum unfragmented ping payload length is 1472 bytes (MTU 1500) or 8972 bytes (MTU 9000)
For testing path MTU you need to send echo requests with the DF bit set. This is accomplished in Windows by -f and in Linux by -M prohibit. Your -M do *explicitly enables fragmentation. When testing the "Packet needs to be fragmented but DF set" shows the source machine to lack the correct setup. When the ping times out, the destination or something in between isn't working. Switches usually have a counter for oversized frames.
Setting the switch to a somewhat larger maximum frame size than necessary isn't hurtful. However, do make sure your end nodes and routers are all set to the exact same size: 9000 when setting the MTU or 9018 when setting the max L2 PDU/frame size.
Intel's Jumbo Packet setting is somewhat misleading. The help text shows that the FCS (4 bytes) isn't counted, so 9014 is the correct setting for MTU 9000 frames.
answered 11 hours ago
Zac67Zac67
3,9732415
You need to distinguish:
- Ethernet maximum frame size: needs to take Ethernet L2 overhead into account, normally 18 bytes - standard is 1518 bytes untagged
- IP MTU: this is what you usually aim for - standard over Ethernet is 1500 bytes, jumbos often use 9000
- maximum
pingpayload for testing: ping uses ICMP (8 bytes overhead) over IPv4 (20 bytes overhead) - so the maximum unfragmented ping payload length is 1472 bytes (MTU 1500) or 8972 bytes (MTU 9000)
For testing path MTU you need to send echo requests with the DF bit set. This is accomplished in Windows by -f and in Linux by -M prohibit. Your -M do *explicitly enables fragmentation. When testing the "Packet needs to be fragmented but DF set" shows the source machine to lack the correct setup. When the ping times out, the destination or something in between isn't working. Switches usually have a counter for oversized frames.
Setting the switch to a somewhat larger maximum frame size than necessary isn't hurtful. However, do make sure your end nodes and routers are all set to the exact same size: 9000 when setting the MTU or 9018 when setting the max L2 PDU/frame size.
Intel's Jumbo Packet setting is somewhat misleading. The help text shows that the FCS (4 bytes) isn't counted, so 9014 is the correct setting for MTU 9000 frames.
answered 11 hours ago
Zac67Zac67
3,9732415
answered 11 hours ago
Zac67Zac67
3,9732415
answered 11 hours ago
Zac67Zac67
3,9732415
answered 11 hours ago
Zac67Zac67
3,9732415
3,9732415
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f954433%2ftrouble-enabling-jumbo-frames%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to a world without a standard (the ethernet standard is still a 1500 octet MTU, and there is no standard for jumbo frames). Also, make sure you never try to send jumbo frames over the public Internet. The jumbo frames would need to be fragmented, but fragments are probably not allowed at the destination by smart engineers because of the fragment DoS attacks.
– Ron Maupin
11 hours ago