What does MTU depend on?What is the actual size of an Ethernet MTUIntenet IP MTU must not exceed 1500...
Count repetitions of an array
Boss asked me to sign a resignation paper without a date on it along with my new contract
Prevent Nautilus / Nemo from creating .Trash-1000 folder in mounted devices
How much mayhem could I cause as a fish?
Has any human ever had the choice to leave Earth permanently?
The No-Straight Maze
Critique vs nitpicking
Why do neural networks need so many training examples to perform?
Website seeing my Facebook data?
"Starve to death" Vs. "Starve to the point of death"
Are the positive and negative planes inner or outer planes in the Great Wheel cosmology model?
Midterm in Mathematics Courses
Subsurf on a crown. How can I smooth some edges and keep others sharp?
Am I correct in stating that the study of topology is purely theoretical?
What senses are available to a corpse subjected to a Speak with Dead spell?
Reading Mishnayos without understanding
Is `Object` a function in javascript?
How is this property called for mod?
Can a player sacrifice a creature after declaring that creature as blocker while taking lethal damage?
Plausible reason for gold-digging ant
What's this assembly doing?
Why is that max-Q doesn't occur in transonic regime?
Should I cite R or RStudio?
If angels and devils are the same species, why would their mortal offspring appear physically different?
What does MTU depend on?
What is the actual size of an Ethernet MTUIntenet IP MTU must not exceed 1500 bytesBasic Interface MTU SettingMTU when creating IPSec PacketsMTU affects access to some sitesOverride Interface MTURegarding clns mtuWhy is the Ethernet data frame size limited to 1500 bytes?Is the MTU of Ethernet still 1500 Bytes?Advantages of setting the MTU and MRU at the server-facing port?
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
asked 7 hours ago
VasilisVasilis
187115
add a comment |
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
asked 7 hours ago
VasilisVasilis
187115
add a comment |
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
asked 7 hours ago
VasilisVasilis
187115
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
ethernet ieee-802.11 mtu
asked 7 hours ago
VasilisVasilis
187115
asked 7 hours ago
VasilisVasilis
187115
asked 7 hours ago
VasilisVasilis
187115
asked 7 hours ago
VasilisVasilis
187115
asked 7 hours ago
VasilisVasilis
187115
187115
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
7 hours ago
2
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
6 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "496"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
},
noCode: 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%2fnetworkengineering.stackexchange.com%2fquestions%2f57206%2fwhat-does-mtu-depend-on%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
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
7 hours ago
2
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
6 hours ago
add a comment |
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
7 hours ago
2
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
6 hours ago
add a comment |
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
edited 6 hours ago
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
answered 7 hours ago
Ron Maupin♦Ron Maupin
66k1369123
66k1369123
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
7 hours ago
2
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
6 hours ago
add a comment |
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
7 hours ago
2
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
6 hours ago
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
7 hours ago
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
7 hours ago
2
2
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
6 hours ago
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
6 hours ago
add a comment |
Thanks for contributing an answer to Network Engineering Stack Exchange!
- 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%2fnetworkengineering.stackexchange.com%2fquestions%2f57206%2fwhat-does-mtu-depend-on%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
