What are the differences between tunneling and regulare encapsulation?
What are the difference between tunneling (https://en.wikipedia.org/wiki/Tunneling_protocol) and regular encapsulation (e.g. TCP/UDP over IP, HTTP/SSH over TCP)?
Is TCP/UDP over IP considered tunneling?
Is HTTP/SSH over TCP considered tunneling?
Thanks.
protocol-theory tunnel
edited 4 hours ago
Zac67
31.3k21961
asked 5 hours ago
TimTim
428416
add a comment |
What are the difference between tunneling (https://en.wikipedia.org/wiki/Tunneling_protocol) and regular encapsulation (e.g. TCP/UDP over IP, HTTP/SSH over TCP)?
Is TCP/UDP over IP considered tunneling?
Is HTTP/SSH over TCP considered tunneling?
Thanks.
protocol-theory tunnel
edited 4 hours ago
Zac67
31.3k21961
asked 5 hours ago
TimTim
428416
add a comment |
What are the difference between tunneling (https://en.wikipedia.org/wiki/Tunneling_protocol) and regular encapsulation (e.g. TCP/UDP over IP, HTTP/SSH over TCP)?
Is TCP/UDP over IP considered tunneling?
Is HTTP/SSH over TCP considered tunneling?
Thanks.
protocol-theory tunnel
edited 4 hours ago
Zac67
31.3k21961
asked 5 hours ago
TimTim
428416
What are the difference between tunneling (https://en.wikipedia.org/wiki/Tunneling_protocol) and regular encapsulation (e.g. TCP/UDP over IP, HTTP/SSH over TCP)?
Is TCP/UDP over IP considered tunneling?
Is HTTP/SSH over TCP considered tunneling?
Thanks.
protocol-theory tunnel
protocol-theory tunnel
edited 4 hours ago
Zac67
31.3k21961
asked 5 hours ago
TimTim
428416
edited 4 hours ago
Zac67
31.3k21961
asked 5 hours ago
TimTim
428416
edited 4 hours ago
Zac67
31.3k21961
edited 4 hours ago
Zac67
31.3k21961
edited 4 hours ago
Zac67
31.3k21961
31.3k21961
asked 5 hours ago
TimTim
428416
asked 5 hours ago
TimTim
428416
asked 5 hours ago
TimTim
428416
428416
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Encapsulation is the normal method of using a lower layer mechanism for moving your data. E.g. HTTP is encapsulated by TCP, TCP is encapsulated by IPv4, IPv4 is encapsulated by an Ethernet frame.
Encapsulating backwards or at the same layer - IP in GRE, IP in IPsec, IP in UDP, Ethernet in L2TP, ... is called tunneling. It somewhat ties a knot in your layering model.
The most common use for tunneling is to allow you to pass packets/frames across a network that doesn't support the protocol or addressing scheme. You can tunnel private IP address packets across a public IP network, IPv4 over an IPv6 network or vice versa, Ethernet frames across a layer-3 connection, and so on.
answered 4 hours ago
Zac67Zac67
31.3k21961
Thanks. What does "It somewhat ties a knot in your layering model" mean?
– Tim
3 hours ago
He means that tunneling does not fit into the OSI or TCPIP model very well.
– Ron Trunk
1 hour ago
add a comment |
For me tunnelling is when you have another level of routing and once you reach one destination of one of the layers the datagram progress to another destination, for example when you have two IP layers on the same datagram, and encapsulation is just put information over TCP/UDP, that basically is put information to be read on the destination. Probably other users have better responses and with more detail
answered 4 hours ago
camp0camp0
13111
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%2f57738%2fwhat-are-the-differences-between-tunneling-and-regulare-encapsulation%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
Encapsulation is the normal method of using a lower layer mechanism for moving your data. E.g. HTTP is encapsulated by TCP, TCP is encapsulated by IPv4, IPv4 is encapsulated by an Ethernet frame.
Encapsulating backwards or at the same layer - IP in GRE, IP in IPsec, IP in UDP, Ethernet in L2TP, ... is called tunneling. It somewhat ties a knot in your layering model.
The most common use for tunneling is to allow you to pass packets/frames across a network that doesn't support the protocol or addressing scheme. You can tunnel private IP address packets across a public IP network, IPv4 over an IPv6 network or vice versa, Ethernet frames across a layer-3 connection, and so on.
answered 4 hours ago
Zac67Zac67
31.3k21961
Thanks. What does "It somewhat ties a knot in your layering model" mean?
– Tim
3 hours ago
He means that tunneling does not fit into the OSI or TCPIP model very well.
– Ron Trunk
1 hour ago
add a comment |
Encapsulation is the normal method of using a lower layer mechanism for moving your data. E.g. HTTP is encapsulated by TCP, TCP is encapsulated by IPv4, IPv4 is encapsulated by an Ethernet frame.
Encapsulating backwards or at the same layer - IP in GRE, IP in IPsec, IP in UDP, Ethernet in L2TP, ... is called tunneling. It somewhat ties a knot in your layering model.
The most common use for tunneling is to allow you to pass packets/frames across a network that doesn't support the protocol or addressing scheme. You can tunnel private IP address packets across a public IP network, IPv4 over an IPv6 network or vice versa, Ethernet frames across a layer-3 connection, and so on.
answered 4 hours ago
Zac67Zac67
31.3k21961
Thanks. What does "It somewhat ties a knot in your layering model" mean?
– Tim
3 hours ago
He means that tunneling does not fit into the OSI or TCPIP model very well.
– Ron Trunk
1 hour ago
add a comment |
Encapsulation is the normal method of using a lower layer mechanism for moving your data. E.g. HTTP is encapsulated by TCP, TCP is encapsulated by IPv4, IPv4 is encapsulated by an Ethernet frame.
Encapsulating backwards or at the same layer - IP in GRE, IP in IPsec, IP in UDP, Ethernet in L2TP, ... is called tunneling. It somewhat ties a knot in your layering model.
The most common use for tunneling is to allow you to pass packets/frames across a network that doesn't support the protocol or addressing scheme. You can tunnel private IP address packets across a public IP network, IPv4 over an IPv6 network or vice versa, Ethernet frames across a layer-3 connection, and so on.
answered 4 hours ago
Zac67Zac67
31.3k21961
Encapsulation is the normal method of using a lower layer mechanism for moving your data. E.g. HTTP is encapsulated by TCP, TCP is encapsulated by IPv4, IPv4 is encapsulated by an Ethernet frame.
Encapsulating backwards or at the same layer - IP in GRE, IP in IPsec, IP in UDP, Ethernet in L2TP, ... is called tunneling. It somewhat ties a knot in your layering model.
The most common use for tunneling is to allow you to pass packets/frames across a network that doesn't support the protocol or addressing scheme. You can tunnel private IP address packets across a public IP network, IPv4 over an IPv6 network or vice versa, Ethernet frames across a layer-3 connection, and so on.
answered 4 hours ago
Zac67Zac67
31.3k21961
answered 4 hours ago
Zac67Zac67
31.3k21961
answered 4 hours ago
Zac67Zac67
31.3k21961
answered 4 hours ago
Zac67Zac67
31.3k21961
31.3k21961
Thanks. What does "It somewhat ties a knot in your layering model" mean?
– Tim
3 hours ago
He means that tunneling does not fit into the OSI or TCPIP model very well.
– Ron Trunk
1 hour ago
add a comment |
Thanks. What does "It somewhat ties a knot in your layering model" mean?
– Tim
3 hours ago
He means that tunneling does not fit into the OSI or TCPIP model very well.
– Ron Trunk
1 hour ago
Thanks. What does "It somewhat ties a knot in your layering model" mean?
– Tim
3 hours ago
Thanks. What does "It somewhat ties a knot in your layering model" mean?
– Tim
3 hours ago
He means that tunneling does not fit into the OSI or TCPIP model very well.
– Ron Trunk
1 hour ago
He means that tunneling does not fit into the OSI or TCPIP model very well.
– Ron Trunk
1 hour ago
add a comment |
For me tunnelling is when you have another level of routing and once you reach one destination of one of the layers the datagram progress to another destination, for example when you have two IP layers on the same datagram, and encapsulation is just put information over TCP/UDP, that basically is put information to be read on the destination. Probably other users have better responses and with more detail
answered 4 hours ago
camp0camp0
13111
add a comment |
For me tunnelling is when you have another level of routing and once you reach one destination of one of the layers the datagram progress to another destination, for example when you have two IP layers on the same datagram, and encapsulation is just put information over TCP/UDP, that basically is put information to be read on the destination. Probably other users have better responses and with more detail
answered 4 hours ago
camp0camp0
13111
add a comment |
For me tunnelling is when you have another level of routing and once you reach one destination of one of the layers the datagram progress to another destination, for example when you have two IP layers on the same datagram, and encapsulation is just put information over TCP/UDP, that basically is put information to be read on the destination. Probably other users have better responses and with more detail
answered 4 hours ago
camp0camp0
13111
For me tunnelling is when you have another level of routing and once you reach one destination of one of the layers the datagram progress to another destination, for example when you have two IP layers on the same datagram, and encapsulation is just put information over TCP/UDP, that basically is put information to be read on the destination. Probably other users have better responses and with more detail
answered 4 hours ago
camp0camp0
13111
answered 4 hours ago
camp0camp0
13111
answered 4 hours ago
camp0camp0
13111
answered 4 hours ago
camp0camp0
13111
13111
add a comment |
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%2f57738%2fwhat-are-the-differences-between-tunneling-and-regulare-encapsulation%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
