What are the differences between tunneling and regulare encapsulation?












1















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







share|improve this question





























    1















    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







    share|improve this question



























      1












      1








      1








      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







      share|improve this question
















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 5 hours ago









      Zac67

      31.3k21961




      31.3k21961










      asked 7 hours ago









      TimTim

      433416




      433416






















          2 Answers
          2






          active

          oldest

          votes


















          2














          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.






          share|improve this answer
























          • Thanks. What does "It somewhat ties a knot in your layering model" mean?

            – Tim
            5 hours ago











          • He means that tunneling does not fit into the OSI or TCPIP model very well.

            – Ron Trunk
            3 hours ago



















          1














          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






          share|improve this answer























            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
            });


            }
            });














            draft saved

            draft discarded


















            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









            2














            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.






            share|improve this answer
























            • Thanks. What does "It somewhat ties a knot in your layering model" mean?

              – Tim
              5 hours ago











            • He means that tunneling does not fit into the OSI or TCPIP model very well.

              – Ron Trunk
              3 hours ago
















            2














            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.






            share|improve this answer
























            • Thanks. What does "It somewhat ties a knot in your layering model" mean?

              – Tim
              5 hours ago











            • He means that tunneling does not fit into the OSI or TCPIP model very well.

              – Ron Trunk
              3 hours ago














            2












            2








            2







            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.






            share|improve this answer













            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.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 5 hours ago









            Zac67Zac67

            31.3k21961




            31.3k21961













            • Thanks. What does "It somewhat ties a knot in your layering model" mean?

              – Tim
              5 hours ago











            • He means that tunneling does not fit into the OSI or TCPIP model very well.

              – Ron Trunk
              3 hours ago



















            • Thanks. What does "It somewhat ties a knot in your layering model" mean?

              – Tim
              5 hours ago











            • He means that tunneling does not fit into the OSI or TCPIP model very well.

              – Ron Trunk
              3 hours ago

















            Thanks. What does "It somewhat ties a knot in your layering model" mean?

            – Tim
            5 hours ago





            Thanks. What does "It somewhat ties a knot in your layering model" mean?

            – Tim
            5 hours ago













            He means that tunneling does not fit into the OSI or TCPIP model very well.

            – Ron Trunk
            3 hours ago





            He means that tunneling does not fit into the OSI or TCPIP model very well.

            – Ron Trunk
            3 hours ago











            1














            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






            share|improve this answer




























              1














              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






              share|improve this answer


























                1












                1








                1







                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






                share|improve this answer













                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







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 6 hours ago









                camp0camp0

                13111




                13111






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    -

                    Popular posts from this blog

                    A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

                    Image
                    0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
                    Read more

                    Calculate evaluation metrics using cross_val_predict sklearn

                    Image
                    1 In the sklearn.model_selection.cross_val_predict page it is stated: Generate cross-validated estimates for each input data point. It is not appropriate to pass these predictions into an evaluation metric. Can someone explain what does it mean? If this gives estimate of Y (y prediction) for every Y (true Y), why can't I calculate metrics such as RMSE or coefficient of determination using these results? python scikit-learn cross-validation share | improve this question edited Nov 28 '18 at 17:52 desertnaut 20.3k 7 43 79 ...
                    Read more

                    Insert data from modal to MySQL (multiple modal on website)

                    Image
                    0 I have problem with inserting data to MySQL from modal. My modal: <a href="#" class="badge badge-pill badge-success">6 komentarzy</a> <a href="#" class="badge badge-pill badge-danger">brak komentarzy</a> <a data-toggle="modal" href="#add_desk_comm_{$desk_['desk_id']}" data-target="#add_desk_comm_{$desk_['desk_id']}" class="ediiit">(dodaj)</a> <div class="modal fade" id="add_desk_comm_{$desk_['desk_id']}" tabindex="-1" role="dialog" aria-labelledby="edit_printer" aria-hidden="true"> <div class="modal-dialog" role="document"> ...
                    Read more