WAN encapsulation Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?SonicWall tz 215 with three LAN and three WANHow does frame relay and MPLS fit in with BGP and WAN/internet/cloud routing?Can't Ping INTERNET from clients but I CAN from Internal RoutersCisco 1921 private LAN can't access internet on WAN interfaceRunning office WAN via MPLS connected Datacenter's WAN connection. Thoughts?Using an ASE(MPLS) line to route datacenter WAN traffic to officeWhat problem does Frame Relay or ATM solve that Ethernet does not?Lost Ethertype in encrypted MACsec framesWAN/Campus network design - Learning purposesDifference between WAN and VPN(tunnels)

Why there are no cargo aircraft with "flying wing" design?

What does '1 unit of lemon juice' mean in a grandma's drink recipe?

What are the motives behind Cersei's orders given to Bronn?

Gastric acid as a weapon

Is the Standard Deduction better than Itemized when both are the same amount?

How to recreate this effect in Photoshop?

If 'B is more likely given A', then 'A is more likely given B'

How to deal with a team lead who never gives me credit?

Antler Helmet: Can it work?

How was the dust limit of 546 satoshis was chosen? Why not 550 satoshis?

Should gear shift center itself while in neutral?

How do I stop a creek from eroding my steep embankment?

Is there a way in Ruby to make just any one out of many keyword arguments required?

How to draw this diagram using TikZ package?

Are my PIs rude or am I just being too sensitive?

Letter Boxed validator

How widely used is the term Treppenwitz? Is it something that most Germans know?

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?

Why was the term "discrete" used in discrete logarithm?

Does polymorph use a PC’s CR or its level?

If Jon Snow became King of the Seven Kingdoms what would his regnal number be?

macOS-like app switching in Plasma 5

Do I really need recursive chmod to restrict access to a folder?

The logistics of corpse disposal



WAN encapsulation



Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?SonicWall tz 215 with three LAN and three WANHow does frame relay and MPLS fit in with BGP and WAN/internet/cloud routing?Can't Ping INTERNET from clients but I CAN from Internal RoutersCisco 1921 private LAN can't access internet on WAN interfaceRunning office WAN via MPLS connected Datacenter's WAN connection. Thoughts?Using an ASE(MPLS) line to route datacenter WAN traffic to officeWhat problem does Frame Relay or ATM solve that Ethernet does not?Lost Ethertype in encrypted MACsec framesWAN/Campus network design - Learning purposesDifference between WAN and VPN(tunnels)










1















I am having some trouble understanding why does a WAN link need encapsulation, such as MPLS or frame relay? Is it merely to encrypt the info from one LAN to another LAN across the internet?










share|improve this question
























  • Do you perhaps mean "encode" (put into computer form) not "encrypt" (provide privacy/secrecy) ? Providing secrecy is not normally an L2 function.

    – jonathanjo
    5 hours ago












  • Is this the same as asking why not every network node is an IP router? I think so but I'm not sure.

    – immibis
    11 mins ago















1















I am having some trouble understanding why does a WAN link need encapsulation, such as MPLS or frame relay? Is it merely to encrypt the info from one LAN to another LAN across the internet?










share|improve this question
























  • Do you perhaps mean "encode" (put into computer form) not "encrypt" (provide privacy/secrecy) ? Providing secrecy is not normally an L2 function.

    – jonathanjo
    5 hours ago












  • Is this the same as asking why not every network node is an IP router? I think so but I'm not sure.

    – immibis
    11 mins ago













1












1








1








I am having some trouble understanding why does a WAN link need encapsulation, such as MPLS or frame relay? Is it merely to encrypt the info from one LAN to another LAN across the internet?










share|improve this question
















I am having some trouble understanding why does a WAN link need encapsulation, such as MPLS or frame relay? Is it merely to encrypt the info from one LAN to another LAN across the internet?







protocol-theory transport-protocol wan






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 5 hours ago









jonathanjo

12.3k1937




12.3k1937










asked 8 hours ago









Alexandre Amaral BednellAlexandre Amaral Bednell

965




965












  • Do you perhaps mean "encode" (put into computer form) not "encrypt" (provide privacy/secrecy) ? Providing secrecy is not normally an L2 function.

    – jonathanjo
    5 hours ago












  • Is this the same as asking why not every network node is an IP router? I think so but I'm not sure.

    – immibis
    11 mins ago

















  • Do you perhaps mean "encode" (put into computer form) not "encrypt" (provide privacy/secrecy) ? Providing secrecy is not normally an L2 function.

    – jonathanjo
    5 hours ago












  • Is this the same as asking why not every network node is an IP router? I think so but I'm not sure.

    – immibis
    11 mins ago
















Do you perhaps mean "encode" (put into computer form) not "encrypt" (provide privacy/secrecy) ? Providing secrecy is not normally an L2 function.

– jonathanjo
5 hours ago






Do you perhaps mean "encode" (put into computer form) not "encrypt" (provide privacy/secrecy) ? Providing secrecy is not normally an L2 function.

– jonathanjo
5 hours ago














Is this the same as asking why not every network node is an IP router? I think so but I'm not sure.

– immibis
11 mins ago





Is this the same as asking why not every network node is an IP router? I think so but I'm not sure.

– immibis
11 mins ago










3 Answers
3






active

oldest

votes


















4














IP packets are encapsulated in a layer 2 protocol, whether they are sent on a LAN or WAN. Frame relay is one such WAN layer 2 protocol. There are others, but most are being rapidly replaced by Ethernet. On LANs, of course, you have Ethernet and Wi-fi.



MPLS doesn't quite fit into the TCP/IP or OSI model. Some consider it a "layer 2.5" protocol.






share|improve this answer
































    2














    The term encapsulation is used to describe a process of adding headers and trailers around some data. For example, here is what happens when you send an email using your favourite email program (like Outlook or Thunderbird):



    • The email is sent from the Application layer to the Transport layer.


    • The Transport layer encapsulates the data and adds its own header (with its own information, such as which port will be used) and passes the data to the Internet layer


    • The Internet layer encapsulates the received data and adds its own header, usually with information about the source and destination IP addresses. The Internet layer than passes the data to the Network Access layer


    • The Network Access layer is the only layer that adds both a header and a trailer. The data is then sent through a physical network link.


    Fore more details wiki






    share|improve this answer






























      1














      Layer 2 Encapsulation covers a number of purposes, most notably framing, error detection, addressing, and protocol layering, and these really apply whether the networking is wide area or local area.




      • Framing: We need some way to reliably chunk the data into frames


      • Error detection: If the encapsulation has addressing or length fields, it's normally vastly much more efficient if it can do its own error detection (and perhaps correction), so it can discard frames which have been corrupted. It's good to put this at a low level, because it's much more likely to have knowledge of what kinds of errors are probably and improbable.


      • Addressing: Very frequently there are multiple devices on the medium, and we want to be able to select which to disturb with this frame: most notable for broadcast media such as ethernet, and often not present in encapsulation for point-to-point networks.


      • Protocol layering: it's very common that the technology should be capable of being used by several upper protocols, perhaps internet protocol and some other. The encapsulation has some method of saying which upper-layer protocol stack should receive it.

      The simplest encapsulation is SLIP, which just does framing and nothing else: it's for point to point links, so addressing isn't used, and the only upper protocol suppported is IP, so it doesn't even have to say that.



      One of the most complex is ethernet, which does framing, error checking, broadcast/unicast, local addressing and upper protocol selection.






      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%2f58483%2fwan-encapsulation%23new-answer', 'question_page');

        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        4














        IP packets are encapsulated in a layer 2 protocol, whether they are sent on a LAN or WAN. Frame relay is one such WAN layer 2 protocol. There are others, but most are being rapidly replaced by Ethernet. On LANs, of course, you have Ethernet and Wi-fi.



        MPLS doesn't quite fit into the TCP/IP or OSI model. Some consider it a "layer 2.5" protocol.






        share|improve this answer





























          4














          IP packets are encapsulated in a layer 2 protocol, whether they are sent on a LAN or WAN. Frame relay is one such WAN layer 2 protocol. There are others, but most are being rapidly replaced by Ethernet. On LANs, of course, you have Ethernet and Wi-fi.



          MPLS doesn't quite fit into the TCP/IP or OSI model. Some consider it a "layer 2.5" protocol.






          share|improve this answer



























            4












            4








            4







            IP packets are encapsulated in a layer 2 protocol, whether they are sent on a LAN or WAN. Frame relay is one such WAN layer 2 protocol. There are others, but most are being rapidly replaced by Ethernet. On LANs, of course, you have Ethernet and Wi-fi.



            MPLS doesn't quite fit into the TCP/IP or OSI model. Some consider it a "layer 2.5" protocol.






            share|improve this answer















            IP packets are encapsulated in a layer 2 protocol, whether they are sent on a LAN or WAN. Frame relay is one such WAN layer 2 protocol. There are others, but most are being rapidly replaced by Ethernet. On LANs, of course, you have Ethernet and Wi-fi.



            MPLS doesn't quite fit into the TCP/IP or OSI model. Some consider it a "layer 2.5" protocol.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 5 hours ago

























            answered 6 hours ago









            Ron TrunkRon Trunk

            39.8k33781




            39.8k33781





















                2














                The term encapsulation is used to describe a process of adding headers and trailers around some data. For example, here is what happens when you send an email using your favourite email program (like Outlook or Thunderbird):



                • The email is sent from the Application layer to the Transport layer.


                • The Transport layer encapsulates the data and adds its own header (with its own information, such as which port will be used) and passes the data to the Internet layer


                • The Internet layer encapsulates the received data and adds its own header, usually with information about the source and destination IP addresses. The Internet layer than passes the data to the Network Access layer


                • The Network Access layer is the only layer that adds both a header and a trailer. The data is then sent through a physical network link.


                Fore more details wiki






                share|improve this answer



























                  2














                  The term encapsulation is used to describe a process of adding headers and trailers around some data. For example, here is what happens when you send an email using your favourite email program (like Outlook or Thunderbird):



                  • The email is sent from the Application layer to the Transport layer.


                  • The Transport layer encapsulates the data and adds its own header (with its own information, such as which port will be used) and passes the data to the Internet layer


                  • The Internet layer encapsulates the received data and adds its own header, usually with information about the source and destination IP addresses. The Internet layer than passes the data to the Network Access layer


                  • The Network Access layer is the only layer that adds both a header and a trailer. The data is then sent through a physical network link.


                  Fore more details wiki






                  share|improve this answer

























                    2












                    2








                    2







                    The term encapsulation is used to describe a process of adding headers and trailers around some data. For example, here is what happens when you send an email using your favourite email program (like Outlook or Thunderbird):



                    • The email is sent from the Application layer to the Transport layer.


                    • The Transport layer encapsulates the data and adds its own header (with its own information, such as which port will be used) and passes the data to the Internet layer


                    • The Internet layer encapsulates the received data and adds its own header, usually with information about the source and destination IP addresses. The Internet layer than passes the data to the Network Access layer


                    • The Network Access layer is the only layer that adds both a header and a trailer. The data is then sent through a physical network link.


                    Fore more details wiki






                    share|improve this answer













                    The term encapsulation is used to describe a process of adding headers and trailers around some data. For example, here is what happens when you send an email using your favourite email program (like Outlook or Thunderbird):



                    • The email is sent from the Application layer to the Transport layer.


                    • The Transport layer encapsulates the data and adds its own header (with its own information, such as which port will be used) and passes the data to the Internet layer


                    • The Internet layer encapsulates the received data and adds its own header, usually with information about the source and destination IP addresses. The Internet layer than passes the data to the Network Access layer


                    • The Network Access layer is the only layer that adds both a header and a trailer. The data is then sent through a physical network link.


                    Fore more details wiki







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered 7 hours ago









                    serverAdmin123serverAdmin123

                    3617




                    3617





















                        1














                        Layer 2 Encapsulation covers a number of purposes, most notably framing, error detection, addressing, and protocol layering, and these really apply whether the networking is wide area or local area.




                        • Framing: We need some way to reliably chunk the data into frames


                        • Error detection: If the encapsulation has addressing or length fields, it's normally vastly much more efficient if it can do its own error detection (and perhaps correction), so it can discard frames which have been corrupted. It's good to put this at a low level, because it's much more likely to have knowledge of what kinds of errors are probably and improbable.


                        • Addressing: Very frequently there are multiple devices on the medium, and we want to be able to select which to disturb with this frame: most notable for broadcast media such as ethernet, and often not present in encapsulation for point-to-point networks.


                        • Protocol layering: it's very common that the technology should be capable of being used by several upper protocols, perhaps internet protocol and some other. The encapsulation has some method of saying which upper-layer protocol stack should receive it.

                        The simplest encapsulation is SLIP, which just does framing and nothing else: it's for point to point links, so addressing isn't used, and the only upper protocol suppported is IP, so it doesn't even have to say that.



                        One of the most complex is ethernet, which does framing, error checking, broadcast/unicast, local addressing and upper protocol selection.






                        share|improve this answer



























                          1














                          Layer 2 Encapsulation covers a number of purposes, most notably framing, error detection, addressing, and protocol layering, and these really apply whether the networking is wide area or local area.




                          • Framing: We need some way to reliably chunk the data into frames


                          • Error detection: If the encapsulation has addressing or length fields, it's normally vastly much more efficient if it can do its own error detection (and perhaps correction), so it can discard frames which have been corrupted. It's good to put this at a low level, because it's much more likely to have knowledge of what kinds of errors are probably and improbable.


                          • Addressing: Very frequently there are multiple devices on the medium, and we want to be able to select which to disturb with this frame: most notable for broadcast media such as ethernet, and often not present in encapsulation for point-to-point networks.


                          • Protocol layering: it's very common that the technology should be capable of being used by several upper protocols, perhaps internet protocol and some other. The encapsulation has some method of saying which upper-layer protocol stack should receive it.

                          The simplest encapsulation is SLIP, which just does framing and nothing else: it's for point to point links, so addressing isn't used, and the only upper protocol suppported is IP, so it doesn't even have to say that.



                          One of the most complex is ethernet, which does framing, error checking, broadcast/unicast, local addressing and upper protocol selection.






                          share|improve this answer

























                            1












                            1








                            1







                            Layer 2 Encapsulation covers a number of purposes, most notably framing, error detection, addressing, and protocol layering, and these really apply whether the networking is wide area or local area.




                            • Framing: We need some way to reliably chunk the data into frames


                            • Error detection: If the encapsulation has addressing or length fields, it's normally vastly much more efficient if it can do its own error detection (and perhaps correction), so it can discard frames which have been corrupted. It's good to put this at a low level, because it's much more likely to have knowledge of what kinds of errors are probably and improbable.


                            • Addressing: Very frequently there are multiple devices on the medium, and we want to be able to select which to disturb with this frame: most notable for broadcast media such as ethernet, and often not present in encapsulation for point-to-point networks.


                            • Protocol layering: it's very common that the technology should be capable of being used by several upper protocols, perhaps internet protocol and some other. The encapsulation has some method of saying which upper-layer protocol stack should receive it.

                            The simplest encapsulation is SLIP, which just does framing and nothing else: it's for point to point links, so addressing isn't used, and the only upper protocol suppported is IP, so it doesn't even have to say that.



                            One of the most complex is ethernet, which does framing, error checking, broadcast/unicast, local addressing and upper protocol selection.






                            share|improve this answer













                            Layer 2 Encapsulation covers a number of purposes, most notably framing, error detection, addressing, and protocol layering, and these really apply whether the networking is wide area or local area.




                            • Framing: We need some way to reliably chunk the data into frames


                            • Error detection: If the encapsulation has addressing or length fields, it's normally vastly much more efficient if it can do its own error detection (and perhaps correction), so it can discard frames which have been corrupted. It's good to put this at a low level, because it's much more likely to have knowledge of what kinds of errors are probably and improbable.


                            • Addressing: Very frequently there are multiple devices on the medium, and we want to be able to select which to disturb with this frame: most notable for broadcast media such as ethernet, and often not present in encapsulation for point-to-point networks.


                            • Protocol layering: it's very common that the technology should be capable of being used by several upper protocols, perhaps internet protocol and some other. The encapsulation has some method of saying which upper-layer protocol stack should receive it.

                            The simplest encapsulation is SLIP, which just does framing and nothing else: it's for point to point links, so addressing isn't used, and the only upper protocol suppported is IP, so it doesn't even have to say that.



                            One of the most complex is ethernet, which does framing, error checking, broadcast/unicast, local addressing and upper protocol selection.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered 5 hours ago









                            jonathanjojonathanjo

                            12.3k1937




                            12.3k1937



























                                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%2f58483%2fwan-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

                                Oświęcim Innehåll Historia | Källor | Externa länkar | Navigeringsmeny50°2′18″N 19°13′17″Ö / 50.03833°N 19.22139°Ö / 50.03833; 19.2213950°2′18″N 19°13′17″Ö / 50.03833°N 19.22139°Ö / 50.03833; 19.221393089658Nordisk familjebok, AuschwitzInsidan tro och existensJewish Community i OświęcimAuschwitz Jewish Center: MuseumAuschwitz Jewish Center

                                Valle di Casies Indice Geografia fisica | Origini del nome | Storia | Società | Amministrazione | Sport | Note | Bibliografia | Voci correlate | Altri progetti | Collegamenti esterni | Menu di navigazione46°46′N 12°11′E / 46.766667°N 12.183333°E46.766667; 12.183333 (Valle di Casies)46°46′N 12°11′E / 46.766667°N 12.183333°E46.766667; 12.183333 (Valle di Casies)Sito istituzionaleAstat Censimento della popolazione 2011 - Determinazione della consistenza dei tre gruppi linguistici della Provincia Autonoma di Bolzano-Alto Adige - giugno 2012Numeri e fattiValle di CasiesDato IstatTabella dei gradi/giorno dei Comuni italiani raggruppati per Regione e Provincia26 agosto 1993, n. 412Heraldry of the World: GsiesStatistiche I.StatValCasies.comWikimedia CommonsWikimedia CommonsValle di CasiesSito ufficialeValle di CasiesMM14870458910042978-6

                                Typsetting diagram chases (with TikZ?) Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How to define the default vertical distance between nodes?Draw edge on arcNumerical conditional within tikz keys?TikZ: Drawing an arc from an intersection to an intersectionDrawing rectilinear curves in Tikz, aka an Etch-a-Sketch drawingLine up nested tikz enviroments or how to get rid of themHow to place nodes in an absolute coordinate system in tikzCommutative diagram with curve connecting between nodesTikz with standalone: pinning tikz coordinates to page cmDrawing a Decision Diagram with Tikz and layout manager