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)

I am not a queen, who am I?

Does accepting a pardon have any bearing on trying that person for the same crime in a sovereign jurisdiction?

Java 8 stream max() function argument type Comparator vs Comparable

How discoverable are IPv6 addresses and AAAA names by potential attackers?

Do you forfeit tax refunds/credits if you aren't required to and don't file by April 15?

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

Is high blood pressure ever a symptom attributable solely to dehydration?

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

Check which numbers satisfy the condition [A*B*C = A! + B! + C!]

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

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

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

What would be the ideal power source for a cybernetic eye?

How to assign captions for two tables in LaTeX?

Should I call the interviewer directly, if HR aren't responding?

How do I mention the quality of my school without bragging

Bonus calculation: Am I making a mountain out of a molehill?

What is the musical term for a note that continously plays through a melody?

"Seemed to had" is it correct?

ListPlot join points by nearest neighbor rather than order

What is a Meta algorithm?

Did Kevin spill real chili?

What LEGO pieces have "real-world" functionality?

Is a manifold-with-boundary with given interior and non-empty boundary essentially unique?



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
    7 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
    2 hours 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
    7 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
    2 hours 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 8 hours ago









jonathanjo

12.3k1937




12.3k1937










asked 10 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
    7 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
    2 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
    7 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
    2 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
7 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
7 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
2 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
2 hours ago










4 Answers
4






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






























        0














        The simplest WAN topology is a point-to-point link known as leased line or private wire. No encapsulation is necessary (although, in practice, there is usually a small header and checksum, such as HDLC).



        In this scenario, the telco transports your bitstream from end to end, reserving 100% of the contracted bandwith at all points on the network.



        Suppose you have a head office and 20 branches in a star of point-to-point links. You will need 20 links and 20 router ports. This is expensive. If you want to create a backup data centre, you multiply the cost by two.



        To save money and router ports, the telco can offer you a switched WAN.



        At the head office site, you have one high-bandwith link, which encapsulates the data streams to the branches in a protocol such as frame relay or ATM (the first non-proprietary protocol of this type was X.25). Encapsulation is necessary to address the WAN endpoint. One can also give information about priority and congestion. The telco can sell you different levels of garanteed bandwith (less than the circuit capacity), which saves you money. The branches have a similar setup. If necessary, the branches can communicate directly, without passing through head office.



        MPLS is a VPN overlay on these layer 2 protocols, which enables the telco to route your packets by IP address, making it much simpler to set up large and complex networks, while still having a secure private network. It is simpler (and therefore cheaper) for the telco to mix private MPLS networks and public internet on their network. They can also provide internet and private MPLS services on the same router at your site.



        In all these switched WAN scenarios, adding a backup data centre requires just one extra connection, one router port and the appropriate configuration.



        I should also mention Internet VPN. In this case, you are encapsulating and encrypting your data over the public network. Encapsulation allows you to access private IP addresses in the corporate network, encryption is necessary for security. What you do not have (with certain exceptions) is guaranteed bandwidth or high service levels, but it's much cheaper.






        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

























          4 Answers
          4






          active

          oldest

          votes








          4 Answers
          4






          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 8 hours ago

























              answered 9 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 9 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 7 hours ago









                              jonathanjojonathanjo

                              12.3k1937




                              12.3k1937





















                                  0














                                  The simplest WAN topology is a point-to-point link known as leased line or private wire. No encapsulation is necessary (although, in practice, there is usually a small header and checksum, such as HDLC).



                                  In this scenario, the telco transports your bitstream from end to end, reserving 100% of the contracted bandwith at all points on the network.



                                  Suppose you have a head office and 20 branches in a star of point-to-point links. You will need 20 links and 20 router ports. This is expensive. If you want to create a backup data centre, you multiply the cost by two.



                                  To save money and router ports, the telco can offer you a switched WAN.



                                  At the head office site, you have one high-bandwith link, which encapsulates the data streams to the branches in a protocol such as frame relay or ATM (the first non-proprietary protocol of this type was X.25). Encapsulation is necessary to address the WAN endpoint. One can also give information about priority and congestion. The telco can sell you different levels of garanteed bandwith (less than the circuit capacity), which saves you money. The branches have a similar setup. If necessary, the branches can communicate directly, without passing through head office.



                                  MPLS is a VPN overlay on these layer 2 protocols, which enables the telco to route your packets by IP address, making it much simpler to set up large and complex networks, while still having a secure private network. It is simpler (and therefore cheaper) for the telco to mix private MPLS networks and public internet on their network. They can also provide internet and private MPLS services on the same router at your site.



                                  In all these switched WAN scenarios, adding a backup data centre requires just one extra connection, one router port and the appropriate configuration.



                                  I should also mention Internet VPN. In this case, you are encapsulating and encrypting your data over the public network. Encapsulation allows you to access private IP addresses in the corporate network, encryption is necessary for security. What you do not have (with certain exceptions) is guaranteed bandwidth or high service levels, but it's much cheaper.






                                  share|improve this answer



























                                    0














                                    The simplest WAN topology is a point-to-point link known as leased line or private wire. No encapsulation is necessary (although, in practice, there is usually a small header and checksum, such as HDLC).



                                    In this scenario, the telco transports your bitstream from end to end, reserving 100% of the contracted bandwith at all points on the network.



                                    Suppose you have a head office and 20 branches in a star of point-to-point links. You will need 20 links and 20 router ports. This is expensive. If you want to create a backup data centre, you multiply the cost by two.



                                    To save money and router ports, the telco can offer you a switched WAN.



                                    At the head office site, you have one high-bandwith link, which encapsulates the data streams to the branches in a protocol such as frame relay or ATM (the first non-proprietary protocol of this type was X.25). Encapsulation is necessary to address the WAN endpoint. One can also give information about priority and congestion. The telco can sell you different levels of garanteed bandwith (less than the circuit capacity), which saves you money. The branches have a similar setup. If necessary, the branches can communicate directly, without passing through head office.



                                    MPLS is a VPN overlay on these layer 2 protocols, which enables the telco to route your packets by IP address, making it much simpler to set up large and complex networks, while still having a secure private network. It is simpler (and therefore cheaper) for the telco to mix private MPLS networks and public internet on their network. They can also provide internet and private MPLS services on the same router at your site.



                                    In all these switched WAN scenarios, adding a backup data centre requires just one extra connection, one router port and the appropriate configuration.



                                    I should also mention Internet VPN. In this case, you are encapsulating and encrypting your data over the public network. Encapsulation allows you to access private IP addresses in the corporate network, encryption is necessary for security. What you do not have (with certain exceptions) is guaranteed bandwidth or high service levels, but it's much cheaper.






                                    share|improve this answer

























                                      0












                                      0








                                      0







                                      The simplest WAN topology is a point-to-point link known as leased line or private wire. No encapsulation is necessary (although, in practice, there is usually a small header and checksum, such as HDLC).



                                      In this scenario, the telco transports your bitstream from end to end, reserving 100% of the contracted bandwith at all points on the network.



                                      Suppose you have a head office and 20 branches in a star of point-to-point links. You will need 20 links and 20 router ports. This is expensive. If you want to create a backup data centre, you multiply the cost by two.



                                      To save money and router ports, the telco can offer you a switched WAN.



                                      At the head office site, you have one high-bandwith link, which encapsulates the data streams to the branches in a protocol such as frame relay or ATM (the first non-proprietary protocol of this type was X.25). Encapsulation is necessary to address the WAN endpoint. One can also give information about priority and congestion. The telco can sell you different levels of garanteed bandwith (less than the circuit capacity), which saves you money. The branches have a similar setup. If necessary, the branches can communicate directly, without passing through head office.



                                      MPLS is a VPN overlay on these layer 2 protocols, which enables the telco to route your packets by IP address, making it much simpler to set up large and complex networks, while still having a secure private network. It is simpler (and therefore cheaper) for the telco to mix private MPLS networks and public internet on their network. They can also provide internet and private MPLS services on the same router at your site.



                                      In all these switched WAN scenarios, adding a backup data centre requires just one extra connection, one router port and the appropriate configuration.



                                      I should also mention Internet VPN. In this case, you are encapsulating and encrypting your data over the public network. Encapsulation allows you to access private IP addresses in the corporate network, encryption is necessary for security. What you do not have (with certain exceptions) is guaranteed bandwidth or high service levels, but it's much cheaper.






                                      share|improve this answer













                                      The simplest WAN topology is a point-to-point link known as leased line or private wire. No encapsulation is necessary (although, in practice, there is usually a small header and checksum, such as HDLC).



                                      In this scenario, the telco transports your bitstream from end to end, reserving 100% of the contracted bandwith at all points on the network.



                                      Suppose you have a head office and 20 branches in a star of point-to-point links. You will need 20 links and 20 router ports. This is expensive. If you want to create a backup data centre, you multiply the cost by two.



                                      To save money and router ports, the telco can offer you a switched WAN.



                                      At the head office site, you have one high-bandwith link, which encapsulates the data streams to the branches in a protocol such as frame relay or ATM (the first non-proprietary protocol of this type was X.25). Encapsulation is necessary to address the WAN endpoint. One can also give information about priority and congestion. The telco can sell you different levels of garanteed bandwith (less than the circuit capacity), which saves you money. The branches have a similar setup. If necessary, the branches can communicate directly, without passing through head office.



                                      MPLS is a VPN overlay on these layer 2 protocols, which enables the telco to route your packets by IP address, making it much simpler to set up large and complex networks, while still having a secure private network. It is simpler (and therefore cheaper) for the telco to mix private MPLS networks and public internet on their network. They can also provide internet and private MPLS services on the same router at your site.



                                      In all these switched WAN scenarios, adding a backup data centre requires just one extra connection, one router port and the appropriate configuration.



                                      I should also mention Internet VPN. In this case, you are encapsulating and encrypting your data over the public network. Encapsulation allows you to access private IP addresses in the corporate network, encryption is necessary for security. What you do not have (with certain exceptions) is guaranteed bandwidth or high service levels, but it's much cheaper.







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered 1 hour ago









                                      grahamj42grahamj42

                                      1462




                                      1462



























                                          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

                                          Францішак Багушэвіч Змест Сям'я | Біяграфія | Творчасць | Мова Багушэвіча | Ацэнкі дзейнасці | Цікавыя факты | Спадчына | Выбраная бібліяграфія | Ушанаванне памяці | У філатэліі | Зноскі | Літаратура | Спасылкі | НавігацыяЛяхоўскі У. Рупіўся дзеля Бога і людзей: Жыццёвы шлях Лявона Вітан-Дубейкаўскага // Вольскі і Памідораў з песняй пра немца Адвакат, паэт, народны заступнік Ашмянскі веснікВ Минске появится площадь Богушевича и улица Сырокомли, Белорусская деловая газета, 19 июля 2001 г.Айцец беларускай нацыянальнай ідэі паўстаў у бронзе Сяргей Аляксандравіч Адашкевіч (1918, Мінск). 80-я гады. Бюст «Францішак Багушэвіч».Яўген Мікалаевіч Ціхановіч. «Партрэт Францішка Багушэвіча»Мікола Мікалаевіч Купава. «Партрэт зачынальніка новай беларускай літаратуры Францішка Багушэвіча»Уладзімір Іванавіч Мелехаў. На помніку «Змагарам за родную мову» Барэльеф «Францішак Багушэвіч»Памяць пра Багушэвіча на Віленшчыне Страчаная сталіца. Беларускія шыльды на вуліцах Вільні«Krynica». Ideologia i przywódcy białoruskiego katolicyzmuФранцішак БагушэвічТворы на knihi.comТворы Францішка Багушэвіча на bellib.byСодаль Уладзімір. Францішак Багушэвіч на Лідчыне;Луцкевіч Антон. Жыцьцё і творчасьць Фр. Багушэвіча ў успамінах ягоных сучасьнікаў // Запісы Беларускага Навуковага таварыства. Вільня, 1938. Сшытак 1. С. 16-34.Большая российская1188761710000 0000 5537 633Xn9209310021619551927869394п

                                          Беларусь Змест Назва Гісторыя Геаграфія Сімволіка Дзяржаўны лад Палітычныя партыі Міжнароднае становішча і знешняя палітыка Адміністрацыйны падзел Насельніцтва Эканоміка Культура і грамадства Сацыяльная сфера Узброеныя сілы Заўвагі Літаратура Спасылкі НавігацыяHGЯOiТоп-2011 г. (па версіі ej.by)Топ-2013 г. (па версіі ej.by)Топ-2016 г. (па версіі ej.by)Топ-2017 г. (па версіі ej.by)Нацыянальны статыстычны камітэт Рэспублікі БеларусьШчыльнасць насельніцтва па краінахhttp://naviny.by/rubrics/society/2011/09/16/ic_articles_116_175144/А. Калечыц, У. Ксяндзоў. Спробы засялення краю неандэртальскім чалавекам.І ў Менску былі мамантыА. Калечыц, У. Ксяндзоў. Старажытны каменны век (палеаліт). Першапачатковае засяленне тэрыторыіГ. Штыхаў. Балты і славяне ў VI—VIII стст.М. Клімаў. Полацкае княства ў IX—XI стст.Г. Штыхаў, В. Ляўко. Палітычная гісторыя Полацкай зямліГ. Штыхаў. Дзяржаўны лад у землях-княствахГ. Штыхаў. Дзяржаўны лад у землях-княствахБеларускія землі ў складзе Вялікага Княства ЛітоўскагаЛюблінская унія 1569 г."The Early Stages of Independence"Zapomniane prawdy25 гадоў таму было аб'яўлена, што Язэп Пілсудскі — беларус (фота)Наша вадаДакументы ЧАЭС: Забруджванне тэрыторыі Беларусі « ЧАЭС Зона адчужэнняСведения о политических партиях, зарегистрированных в Республике Беларусь // Министерство юстиции Республики БеларусьСтатыстычны бюлетэнь „Полаўзроставая структура насельніцтва Рэспублікі Беларусь на 1 студзеня 2012 года і сярэднегадовая колькасць насельніцтва за 2011 год“Индекс человеческого развития Беларуси — не было бы нижеБеларусь занимает первое место в СНГ по индексу развития с учетом гендерного факцёраНацыянальны статыстычны камітэт Рэспублікі БеларусьКанстытуцыя РБ. Артыкул 17Трансфармацыйныя задачы БеларусіВыйсце з крызісу — далейшае рэфармаванне Беларускі рубель — сусветны лідар па дэвальвацыяхПра змену коштаў у кастрычніку 2011 г.Бядней за беларусаў у СНД толькі таджыкіСярэдні заробак у верасні дасягнуў 2,26 мільёна рублёўЭканомікаГаласуем за ТОП-100 беларускай прозыСучасныя беларускія мастакіАрхитектура Беларуси BELARUS.BYА. Каханоўскі. Культура Беларусі ўсярэдзіне XVII—XVIII ст.Анталогія беларускай народнай песні, гуказапісы спеваўБеларускія Музычныя IнструментыБеларускі рок, які мы страцілі. Топ-10 гуртоў«Мясцовы час» — нязгаслая легенда беларускай рок-музыкіСЯРГЕЙ БУДКІН. МЫ НЯ ЗНАЕМ СВАЁЙ МУЗЫКІМ. А. Каладзінскі. НАРОДНЫ ТЭАТРМагнацкія культурныя цэнтрыПублічная дыскусія «Беларуская новая пьеса: без беларускай мовы ці беларуская?»Беларускія драматургі па-ранейшаму лепш ставяцца за мяжой, чым на радзіме«Працэс незалежнага кіно пайшоў, і дзяржаву турбуе яго непадкантрольнасць»Беларускія філосафы ў пошуках прасторыВсе идём в библиотекуАрхіваванаАб Нацыянальнай праграме даследавання і выкарыстання касмічнай прасторы ў мірных мэтах на 2008—2012 гадыУ космас — разам.У суседнім з Барысаўскім раёне пабудуюць Камандна-вымяральны пунктСвяты і абрады беларусаў«Мірныя бульбашы з малой краіны» — 5 непраўдзівых стэрэатыпаў пра БеларусьМ. Раманюк. Беларускае народнае адзеннеУ Беларусі скарачаецца колькасць злачынстваўЛукашэнка незадаволены мінскімі ўладамі Крадзяжы складаюць у Мінску каля 70% злачынстваў Узровень злачыннасці ў Мінскай вобласці — адзін з самых высокіх у краіне Генпракуратура аналізуе стан са злачыннасцю ў Беларусі па каэфіцыенце злачыннасці У Беларусі стабілізавалася крымінагеннае становішча, лічыць генпракурорЗамежнікі сталі здзяйсняць у Беларусі больш злачынстваўМУС Беларусі турбуе рост рэцыдыўнай злачыннасціЯ з ЖЭСа. Дазволіце вас абкрасці! Рэйтынг усіх службаў і падраздзяленняў ГУУС Мінгарвыканкама вырасАб КДБ РБГісторыя Аператыўна-аналітычнага цэнтра РБГісторыя ДКФРТаможняagentura.ruБеларусьBelarus.by — Афіцыйны сайт Рэспублікі БеларусьСайт урада БеларусіRadzima.org — Збор архітэктурных помнікаў, гісторыя Беларусі«Глобус Беларуси»Гербы и флаги БеларусиАсаблівасці каменнага веку на БеларусіА. Калечыц, У. Ксяндзоў. Старажытны каменны век (палеаліт). Першапачатковае засяленне тэрыторыіУ. Ксяндзоў. Сярэдні каменны век (мезаліт). Засяленне краю плямёнамі паляўнічых, рыбакоў і збіральнікаўА. Калечыц, М. Чарняўскі. Плямёны на тэрыторыі Беларусі ў новым каменным веку (неаліце)А. Калечыц, У. Ксяндзоў, М. Чарняўскі. Гаспадарчыя заняткі ў каменным векуЭ. Зайкоўскі. Духоўная культура ў каменным векуАсаблівасці бронзавага веку на БеларусіФарміраванне супольнасцей ранняга перыяду бронзавага векуФотографии БеларусиРоля беларускіх зямель ва ўтварэнні і ўмацаванні ВКЛВ. Фадзеева. З гісторыі развіцця беларускай народнай вышыўкіDMOZGran catalanaБольшая российскаяBritannica (анлайн)Швейцарскі гістарычны15325917611952699xDA123282154079143-90000 0001 2171 2080n9112870100577502ge128882171858027501086026362074122714179пппппп

                                          ValueError: Expected n_neighbors <= n_samples, but n_samples = 1, n_neighbors = 6 (SMOTE) The 2019 Stack Overflow Developer Survey Results Are InCan SMOTE be applied over sequence of words (sentences)?ValueError when doing validation with random forestsSMOTE and multi class oversamplingLogic behind SMOTE-NC?ValueError: Error when checking target: expected dense_1 to have shape (7,) but got array with shape (1,)SmoteBoost: Should SMOTE be ran individually for each iteration/tree in the boosting?solving multi-class imbalance classification using smote and OSSUsing SMOTE for Synthetic Data generation to improve performance on unbalanced dataproblem of entry format for a simple model in KerasSVM SMOTE fit_resample() function runs forever with no result