Some questions on UDP send receive buffer, and networkingHow is the MTU is 65535 in UDP but ethernet does not allow frame size more than 1500 bytes(RFC-791) Application Layer PDU size, guaranteed to pass without fragmentationComputer Networks bonus: find MTU less than 1500What is the “in-the-wire” size of a ethernet frame? 1518 or 1542?gentoo bonded nics dropping packetsCan TCP and UDP packets be split into pieces?UDP maximum segment sizeKVM Network configuration + VLAN trunckExtreme UDP packet loss at 300Mbit (14%), but TCP > 800Mbit w/o retransmitsBAD UDP LENGTH > IP PAYLOAD LENGTH
Predict the product from the reaction
What preparations would Hubble have needed to return in a Shuttle?
Are there examples of rowers who also fought?
Why are there no file insertion syscalls
If the mass of the Earth is decreasing by sending debris in space, does its angular momentum also decrease?
How can I prevent a user from copying files on another hard drive?
Why is it 出差去 and not 去出差?
How can a warlock learn from a spellbook?
Large-n limit of the distribution of the normalized sum of Cauchy random variables
Freewill and rewarding dogs
How is linear momentum conserved in circular motion?
How can the US president give an order to a civilian?
First occurrence in the Sixers sequence
Implementation of the Jacobi Symbol in C
How can I improve my violin intonation for enharmonic notes?
I found a password with hashcat but it doesn't work
How much steel armor can you wear and still be able to swim?
Definition of 'vrit'
In the US, can a former president run again?
What is the highest power supply a Raspberry pi 3 B can handle without getting damaged?
How to sort human readable size
Help with coding a matrix
What kind of chart is this?
Examples of protocols that are insecure when run concurrently
Some questions on UDP send receive buffer, and networking
How is the MTU is 65535 in UDP but ethernet does not allow frame size more than 1500 bytes(RFC-791) Application Layer PDU size, guaranteed to pass without fragmentationComputer Networks bonus: find MTU less than 1500What is the “in-the-wire” size of a ethernet frame? 1518 or 1542?gentoo bonded nics dropping packetsCan TCP and UDP packets be split into pieces?UDP maximum segment sizeKVM Network configuration + VLAN trunckExtreme UDP packet loss at 300Mbit (14%), but TCP > 800Mbit w/o retransmitsBAD UDP LENGTH > IP PAYLOAD LENGTH
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have two debian servers located on the same subnet. They are connected by a switch. I am aware the UDP is unreliable.
Question 1: I assume the link layer is ethernet. And MTU from a standard
Ethernet is 1500 bytes. So the maximum datagram not being fragramented is 1500- 20 -8 = 1472 bytes? Can I say, because there's no router in between these two servers, therefore, the IP datagram will
not be fragmented.
Question 2: Because two servers are directly connected with a switch, can I
assume that all datagrams arrives in order and no loss on the path?
Question 3: How can I determine that the chances of datagram dropped
at the server because of buffer overflow. What size to set the receive buffer so that datagram will not overflow receive buffer.
linux networking debian udp
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
add a comment |
I have two debian servers located on the same subnet. They are connected by a switch. I am aware the UDP is unreliable.
Question 1: I assume the link layer is ethernet. And MTU from a standard
Ethernet is 1500 bytes. So the maximum datagram not being fragramented is 1500- 20 -8 = 1472 bytes? Can I say, because there's no router in between these two servers, therefore, the IP datagram will
not be fragmented.
Question 2: Because two servers are directly connected with a switch, can I
assume that all datagrams arrives in order and no loss on the path?
Question 3: How can I determine that the chances of datagram dropped
at the server because of buffer overflow. What size to set the receive buffer so that datagram will not overflow receive buffer.
linux networking debian udp
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
add a comment |
I have two debian servers located on the same subnet. They are connected by a switch. I am aware the UDP is unreliable.
Question 1: I assume the link layer is ethernet. And MTU from a standard
Ethernet is 1500 bytes. So the maximum datagram not being fragramented is 1500- 20 -8 = 1472 bytes? Can I say, because there's no router in between these two servers, therefore, the IP datagram will
not be fragmented.
Question 2: Because two servers are directly connected with a switch, can I
assume that all datagrams arrives in order and no loss on the path?
Question 3: How can I determine that the chances of datagram dropped
at the server because of buffer overflow. What size to set the receive buffer so that datagram will not overflow receive buffer.
linux networking debian udp
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
I have two debian servers located on the same subnet. They are connected by a switch. I am aware the UDP is unreliable.
Question 1: I assume the link layer is ethernet. And MTU from a standard
Ethernet is 1500 bytes. So the maximum datagram not being fragramented is 1500- 20 -8 = 1472 bytes? Can I say, because there's no router in between these two servers, therefore, the IP datagram will
not be fragmented.
Question 2: Because two servers are directly connected with a switch, can I
assume that all datagrams arrives in order and no loss on the path?
Question 3: How can I determine that the chances of datagram dropped
at the server because of buffer overflow. What size to set the receive buffer so that datagram will not overflow receive buffer.
linux networking debian udp
linux networking debian udp
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
edited Dec 17 '11 at 22:50
Kevin Q
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
asked Dec 17 '11 at 22:27
Kevin QKevin Q
113
113
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The IP packet can certainly be fragmented by the devices sending them; they know that their media's MTU is lower than the packet that they're sending, so they'll split the IP packet accordingly. In this day and age, many hosts implement path MTU discovery, which explicitly tells routers not to handle fragmentation at all, but to tell the host to adjust its effective MTU for that path instead, so that it's handling any necessary fragmentation.
No - with a single switch topology you can probably assume that they'll arrive in order, but you cannot assume no loss.
This completely depends on the devices in use, their performance, and the amount of data in transit.
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
add a comment |
1) No. In practice, even setting the don't fragment (DF) bit won't guarantee to the layer above UDP that there's no fragmentation. UDP simply doesn't provide this guarantee to layers above it. Layers above UDP are not supposed to care.
2) No. UDP simply doesn't provide this guarantee to layers above it.
3) The only reliable way to tell is to measure under the actual conditions you plan to use.
Fundamentally, what you are trying to do is synthesize a guarantee by reasoning that you can't think of any way the guarantee could be violated. You can't synthesize a guarantee that way. You only get the guarantees the protocol actually provides. Though in practice, it will happen most of the time this way, it just isn't guaranteed, period.
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
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%2f341991%2fsome-questions-on-udp-send-receive-buffer-and-networking%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The IP packet can certainly be fragmented by the devices sending them; they know that their media's MTU is lower than the packet that they're sending, so they'll split the IP packet accordingly. In this day and age, many hosts implement path MTU discovery, which explicitly tells routers not to handle fragmentation at all, but to tell the host to adjust its effective MTU for that path instead, so that it's handling any necessary fragmentation.
No - with a single switch topology you can probably assume that they'll arrive in order, but you cannot assume no loss.
This completely depends on the devices in use, their performance, and the amount of data in transit.
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
add a comment |
The IP packet can certainly be fragmented by the devices sending them; they know that their media's MTU is lower than the packet that they're sending, so they'll split the IP packet accordingly. In this day and age, many hosts implement path MTU discovery, which explicitly tells routers not to handle fragmentation at all, but to tell the host to adjust its effective MTU for that path instead, so that it's handling any necessary fragmentation.
No - with a single switch topology you can probably assume that they'll arrive in order, but you cannot assume no loss.
This completely depends on the devices in use, their performance, and the amount of data in transit.
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
add a comment |
The IP packet can certainly be fragmented by the devices sending them; they know that their media's MTU is lower than the packet that they're sending, so they'll split the IP packet accordingly. In this day and age, many hosts implement path MTU discovery, which explicitly tells routers not to handle fragmentation at all, but to tell the host to adjust its effective MTU for that path instead, so that it's handling any necessary fragmentation.
No - with a single switch topology you can probably assume that they'll arrive in order, but you cannot assume no loss.
This completely depends on the devices in use, their performance, and the amount of data in transit.
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
The IP packet can certainly be fragmented by the devices sending them; they know that their media's MTU is lower than the packet that they're sending, so they'll split the IP packet accordingly. In this day and age, many hosts implement path MTU discovery, which explicitly tells routers not to handle fragmentation at all, but to tell the host to adjust its effective MTU for that path instead, so that it's handling any necessary fragmentation.
No - with a single switch topology you can probably assume that they'll arrive in order, but you cannot assume no loss.
This completely depends on the devices in use, their performance, and the amount of data in transit.
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
answered Dec 17 '11 at 22:47
Shane Madden♦Shane Madden
105k9149225
105k9149225
add a comment |
add a comment |
1) No. In practice, even setting the don't fragment (DF) bit won't guarantee to the layer above UDP that there's no fragmentation. UDP simply doesn't provide this guarantee to layers above it. Layers above UDP are not supposed to care.
2) No. UDP simply doesn't provide this guarantee to layers above it.
3) The only reliable way to tell is to measure under the actual conditions you plan to use.
Fundamentally, what you are trying to do is synthesize a guarantee by reasoning that you can't think of any way the guarantee could be violated. You can't synthesize a guarantee that way. You only get the guarantees the protocol actually provides. Though in practice, it will happen most of the time this way, it just isn't guaranteed, period.
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
add a comment |
1) No. In practice, even setting the don't fragment (DF) bit won't guarantee to the layer above UDP that there's no fragmentation. UDP simply doesn't provide this guarantee to layers above it. Layers above UDP are not supposed to care.
2) No. UDP simply doesn't provide this guarantee to layers above it.
3) The only reliable way to tell is to measure under the actual conditions you plan to use.
Fundamentally, what you are trying to do is synthesize a guarantee by reasoning that you can't think of any way the guarantee could be violated. You can't synthesize a guarantee that way. You only get the guarantees the protocol actually provides. Though in practice, it will happen most of the time this way, it just isn't guaranteed, period.
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
add a comment |
1) No. In practice, even setting the don't fragment (DF) bit won't guarantee to the layer above UDP that there's no fragmentation. UDP simply doesn't provide this guarantee to layers above it. Layers above UDP are not supposed to care.
2) No. UDP simply doesn't provide this guarantee to layers above it.
3) The only reliable way to tell is to measure under the actual conditions you plan to use.
Fundamentally, what you are trying to do is synthesize a guarantee by reasoning that you can't think of any way the guarantee could be violated. You can't synthesize a guarantee that way. You only get the guarantees the protocol actually provides. Though in practice, it will happen most of the time this way, it just isn't guaranteed, period.
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
1) No. In practice, even setting the don't fragment (DF) bit won't guarantee to the layer above UDP that there's no fragmentation. UDP simply doesn't provide this guarantee to layers above it. Layers above UDP are not supposed to care.
2) No. UDP simply doesn't provide this guarantee to layers above it.
3) The only reliable way to tell is to measure under the actual conditions you plan to use.
Fundamentally, what you are trying to do is synthesize a guarantee by reasoning that you can't think of any way the guarantee could be violated. You can't synthesize a guarantee that way. You only get the guarantees the protocol actually provides. Though in practice, it will happen most of the time this way, it just isn't guaranteed, period.
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
answered Dec 18 '11 at 5:56
David SchwartzDavid Schwartz
28.8k14474
28.8k14474
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%2f341991%2fsome-questions-on-udp-send-receive-buffer-and-networking%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
