the meaning of static routes and next hop

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












3














i configured a network topology on cisco packet tracer to learn about the static routing, as shown in figure belowenter image description here



i spent a lot of time to ensure the connectivity between server0 and server2(cause i'm new to networking) and it worked eventually. the servers can access each other's http web.



my questions are:



  1. do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...

  2. for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?

  3. for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?

  4. does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(

thanks for any reply! i hope these questions are not so dumb :|










share|improve this question


























    3














    i configured a network topology on cisco packet tracer to learn about the static routing, as shown in figure belowenter image description here



    i spent a lot of time to ensure the connectivity between server0 and server2(cause i'm new to networking) and it worked eventually. the servers can access each other's http web.



    my questions are:



    1. do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...

    2. for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?

    3. for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?

    4. does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(

    thanks for any reply! i hope these questions are not so dumb :|










    share|improve this question
























      3












      3








      3







      i configured a network topology on cisco packet tracer to learn about the static routing, as shown in figure belowenter image description here



      i spent a lot of time to ensure the connectivity between server0 and server2(cause i'm new to networking) and it worked eventually. the servers can access each other's http web.



      my questions are:



      1. do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...

      2. for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?

      3. for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?

      4. does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(

      thanks for any reply! i hope these questions are not so dumb :|










      share|improve this question













      i configured a network topology on cisco packet tracer to learn about the static routing, as shown in figure belowenter image description here



      i spent a lot of time to ensure the connectivity between server0 and server2(cause i'm new to networking) and it worked eventually. the servers can access each other's http web.



      my questions are:



      1. do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...

      2. for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?

      3. for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?

      4. does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(

      thanks for any reply! i hope these questions are not so dumb :|







      routing next-hop






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 26 '18 at 9:20









      user53815user53815

      312




      312




















          1 Answer
          1






          active

          oldest

          votes


















          3














          Routers learn networks by one of three methods:



          1. directly attached - this network can directly be talked to through one the router's interfaces

          2. static route - remote network reachable through another router/gateway is configured by a static configuration entry; static routes need to point to an interface in a common network between the two routers

          3. routing protocol - remote network reachable through a gateway and route is dynamically exchanged via a routing protocol


          do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...




          Since you're not using a routing protocol, all remote networks on each router need to be set up with static routes. With only a single upstream router, you can alternatively use that as gateway of last resort.



          R0 needs either R1' 192.168.2.1/24 as default gateway or separate routes for 10.90.2.0/28, 172.18.6.0/24 and 192.168.200.0/28.



          R1 could use a default route to R2'2 10.90.2.2 (or separate routes for the right-hand leg) but always requires a separate route to 10.1.1.0/24 via R0's 192.168.1.1.



          And so on.




          for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?




          R0's gateways need to be interfaces in one of its local networks, so 192.168.1.2 is the next hop for any of R0's routes.



          You can't use 10.9.2.2 or 172.18.6.2 because they're not adjacent to R0.




          for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?




          Yes. If any of the routers doesn't have a gateway to the destination it'll drop the packet.




          does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(




          Each router's gateway of last resort aka default gateway can be used to simplify the routing table as pointed out above. Especially R0 and R3 face only one gateway to all other subnets and that could be their default gateway.






          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%2f55674%2fthe-meaning-of-static-routes-and-next-hop%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            Routers learn networks by one of three methods:



            1. directly attached - this network can directly be talked to through one the router's interfaces

            2. static route - remote network reachable through another router/gateway is configured by a static configuration entry; static routes need to point to an interface in a common network between the two routers

            3. routing protocol - remote network reachable through a gateway and route is dynamically exchanged via a routing protocol


            do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...




            Since you're not using a routing protocol, all remote networks on each router need to be set up with static routes. With only a single upstream router, you can alternatively use that as gateway of last resort.



            R0 needs either R1' 192.168.2.1/24 as default gateway or separate routes for 10.90.2.0/28, 172.18.6.0/24 and 192.168.200.0/28.



            R1 could use a default route to R2'2 10.90.2.2 (or separate routes for the right-hand leg) but always requires a separate route to 10.1.1.0/24 via R0's 192.168.1.1.



            And so on.




            for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?




            R0's gateways need to be interfaces in one of its local networks, so 192.168.1.2 is the next hop for any of R0's routes.



            You can't use 10.9.2.2 or 172.18.6.2 because they're not adjacent to R0.




            for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?




            Yes. If any of the routers doesn't have a gateway to the destination it'll drop the packet.




            does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(




            Each router's gateway of last resort aka default gateway can be used to simplify the routing table as pointed out above. Especially R0 and R3 face only one gateway to all other subnets and that could be their default gateway.






            share|improve this answer

























              3














              Routers learn networks by one of three methods:



              1. directly attached - this network can directly be talked to through one the router's interfaces

              2. static route - remote network reachable through another router/gateway is configured by a static configuration entry; static routes need to point to an interface in a common network between the two routers

              3. routing protocol - remote network reachable through a gateway and route is dynamically exchanged via a routing protocol


              do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...




              Since you're not using a routing protocol, all remote networks on each router need to be set up with static routes. With only a single upstream router, you can alternatively use that as gateway of last resort.



              R0 needs either R1' 192.168.2.1/24 as default gateway or separate routes for 10.90.2.0/28, 172.18.6.0/24 and 192.168.200.0/28.



              R1 could use a default route to R2'2 10.90.2.2 (or separate routes for the right-hand leg) but always requires a separate route to 10.1.1.0/24 via R0's 192.168.1.1.



              And so on.




              for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?




              R0's gateways need to be interfaces in one of its local networks, so 192.168.1.2 is the next hop for any of R0's routes.



              You can't use 10.9.2.2 or 172.18.6.2 because they're not adjacent to R0.




              for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?




              Yes. If any of the routers doesn't have a gateway to the destination it'll drop the packet.




              does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(




              Each router's gateway of last resort aka default gateway can be used to simplify the routing table as pointed out above. Especially R0 and R3 face only one gateway to all other subnets and that could be their default gateway.






              share|improve this answer























                3












                3








                3






                Routers learn networks by one of three methods:



                1. directly attached - this network can directly be talked to through one the router's interfaces

                2. static route - remote network reachable through another router/gateway is configured by a static configuration entry; static routes need to point to an interface in a common network between the two routers

                3. routing protocol - remote network reachable through a gateway and route is dynamically exchanged via a routing protocol


                do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...




                Since you're not using a routing protocol, all remote networks on each router need to be set up with static routes. With only a single upstream router, you can alternatively use that as gateway of last resort.



                R0 needs either R1' 192.168.2.1/24 as default gateway or separate routes for 10.90.2.0/28, 172.18.6.0/24 and 192.168.200.0/28.



                R1 could use a default route to R2'2 10.90.2.2 (or separate routes for the right-hand leg) but always requires a separate route to 10.1.1.0/24 via R0's 192.168.1.1.



                And so on.




                for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?




                R0's gateways need to be interfaces in one of its local networks, so 192.168.1.2 is the next hop for any of R0's routes.



                You can't use 10.9.2.2 or 172.18.6.2 because they're not adjacent to R0.




                for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?




                Yes. If any of the routers doesn't have a gateway to the destination it'll drop the packet.




                does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(




                Each router's gateway of last resort aka default gateway can be used to simplify the routing table as pointed out above. Especially R0 and R3 face only one gateway to all other subnets and that could be their default gateway.






                share|improve this answer












                Routers learn networks by one of three methods:



                1. directly attached - this network can directly be talked to through one the router's interfaces

                2. static route - remote network reachable through another router/gateway is configured by a static configuration entry; static routes need to point to an interface in a common network between the two routers

                3. routing protocol - remote network reachable through a gateway and route is dynamically exchanged via a routing protocol


                do all the static routes settings on the routers necessary? cause there are so many lines which took me quite a while to configure for the connections between servers...




                Since you're not using a routing protocol, all remote networks on each router need to be set up with static routes. With only a single upstream router, you can alternatively use that as gateway of last resort.



                R0 needs either R1' 192.168.2.1/24 as default gateway or separate routes for 10.90.2.0/28, 172.18.6.0/24 and 192.168.200.0/28.



                R1 could use a default route to R2'2 10.90.2.2 (or separate routes for the right-hand leg) but always requires a separate route to 10.1.1.0/24 via R0's 192.168.1.1.



                And so on.




                for the R0 router, the next hop address should be set to 192.168.1.2 (for the dest. network)rather than addresses such as 10.90.2.2 or 172.18.6.2, why?




                R0's gateways need to be interfaces in one of its local networks, so 192.168.1.2 is the next hop for any of R0's routes.



                You can't use 10.9.2.2 or 172.18.6.2 because they're not adjacent to R0.




                for all the routers, is it necessary to configure static routes and next hop for all the dest. network(which located on other routers) to enable the accessibility between server0 & server2?




                Yes. If any of the routers doesn't have a gateway to the destination it'll drop the packet.




                does "gateway of last resort" meaningful in this network topology? i don't see a way to use it :(




                Each router's gateway of last resort aka default gateway can be used to simplify the routing table as pointed out above. Especially R0 and R3 face only one gateway to all other subnets and that could be their default gateway.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 26 '18 at 9:50









                Zac67Zac67

                26.4k21352




                26.4k21352



























                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f55674%2fthe-meaning-of-static-routes-and-next-hop%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

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay