Access my router's gateway network?Configuring network route between two routers on home networkCreate second...

Is it possible that AIC = BIC?

It's a yearly task, alright

Can elves maintain concentration in a trance?

Why are the outputs of printf and std::cout different

Why does Deadpool say "You're welcome, Canada," after shooting Ryan Reynolds in the end credits?

Splitting string ID code into various parts

Provisioning profile doesn't include the application-identifier and keychain-access-groups entitlements

At what level can a dragon innately cast its spells?

Welcoming 2019 Pi day: How to draw the letter π?

Make a transparent 448*448 image

Does this property of comaximal ideals always holds?

How to write cleanly even if my character uses expletive language?

Making a sword in the stone, in a medieval world without magic

Do I need life insurance if I can cover my own funeral costs?

Why do passenger jet manufacturers design their planes with stall prevention systems?

Why are there 40 737 Max planes in flight when they have been grounded as not airworthy?

Use of プラトニック in this sentence?

Theorems like the Lovász Local Lemma?

How to deal with taxi scam when on vacation?

How could a scammer know the apps on my phone / iTunes account?

Can anyone tell me why this program fails?

Why do Australian milk farmers need to protest supermarkets' milk price?

The use of "touch" and "touch on" in context

What is this large pipe coming out of my roof?



Access my router's gateway network?


Configuring network route between two routers on home networkCreate second wireless network isolated from existing wireless networkHow to determine Linksys router's IP when it is in gateway mode?Two routers network routing settingsHow can i configure my network so i can access a linux box behind 2 routers (4G and wifi)Cannot access devices connected to primary router from access pointStatic Routing IssueHow to setup a static route between wireless routersLocal network - multiple internet accessNetworking : Setting up multiple gateway network













0















I have two routers in my place.



Main router (connected to the Internet) - 192.168.1.1



Secondary router (connected to the main router) - 192.168.0.1



I have a Network storage device and a few shared directories connected to the main router.



(Network storage - 192.168.1.16)



How can I access one of them using a PC connected to the secondary router?



Home Network diagram:



Home Network



I currently have access to the internet using both laptop and main PC, but I want to get access from my laptop to the storage and to my shared directories.



The problem is the my main router always forwards all packets straight to the WAN.. (Internet)










share|improve this question

























  • Do you kbow, that DuobleNATing is very bad idea?

    – Lazy Badger
    Mar 24 '12 at 5:29
















0















I have two routers in my place.



Main router (connected to the Internet) - 192.168.1.1



Secondary router (connected to the main router) - 192.168.0.1



I have a Network storage device and a few shared directories connected to the main router.



(Network storage - 192.168.1.16)



How can I access one of them using a PC connected to the secondary router?



Home Network diagram:



Home Network



I currently have access to the internet using both laptop and main PC, but I want to get access from my laptop to the storage and to my shared directories.



The problem is the my main router always forwards all packets straight to the WAN.. (Internet)










share|improve this question

























  • Do you kbow, that DuobleNATing is very bad idea?

    – Lazy Badger
    Mar 24 '12 at 5:29














0












0








0


2






I have two routers in my place.



Main router (connected to the Internet) - 192.168.1.1



Secondary router (connected to the main router) - 192.168.0.1



I have a Network storage device and a few shared directories connected to the main router.



(Network storage - 192.168.1.16)



How can I access one of them using a PC connected to the secondary router?



Home Network diagram:



Home Network



I currently have access to the internet using both laptop and main PC, but I want to get access from my laptop to the storage and to my shared directories.



The problem is the my main router always forwards all packets straight to the WAN.. (Internet)










share|improve this question
















I have two routers in my place.



Main router (connected to the Internet) - 192.168.1.1



Secondary router (connected to the main router) - 192.168.0.1



I have a Network storage device and a few shared directories connected to the main router.



(Network storage - 192.168.1.16)



How can I access one of them using a PC connected to the secondary router?



Home Network diagram:



Home Network



I currently have access to the internet using both laptop and main PC, but I want to get access from my laptop to the storage and to my shared directories.



The problem is the my main router always forwards all packets straight to the WAN.. (Internet)







networking router ip storage gateway






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 14 mins ago









karel

9,27293139




9,27293139










asked Mar 23 '12 at 9:47









DanpeDanpe

5731512




5731512













  • Do you kbow, that DuobleNATing is very bad idea?

    – Lazy Badger
    Mar 24 '12 at 5:29



















  • Do you kbow, that DuobleNATing is very bad idea?

    – Lazy Badger
    Mar 24 '12 at 5:29

















Do you kbow, that DuobleNATing is very bad idea?

– Lazy Badger
Mar 24 '12 at 5:29





Do you kbow, that DuobleNATing is very bad idea?

– Lazy Badger
Mar 24 '12 at 5:29










3 Answers
3






active

oldest

votes


















7















How can i acces one of them using a PC connected to the Secondery Router?




Make sure both the routers are properly configured. Each should have a routing table entry for both LANs (192.168.1.x and 192.168.0.x). Such routes can be statically configured or dynamic (using a routing protocol such as RIP).



Properly configured routers will let PCs know what to do when PCs contact the wrong router (typically by issuing ICMP redirects).





Here's a scenario using one router to support two LANs and Internet access



  (Internet)
|
+---o-----+ +------+ +------+
|DSL Modem| |switch| |switch|
+---O-----+ +-OOOO-+ +-OOOO-+
| | | | |
+---O--+ | +O-+ | +O-+
|Router| | |PC| | |PC|
+-O-O--+ | +--+ | +--+
| | | |
| `-------------' |
`----------------------------'

|<--------->| |<--------->|
192.168.1.x 192.168.0.x


The router connects both LANs to the INternet and allows all PCs on both LANs to contact each other. The router provides DHCP service to both LANs, That DHCP service tells PCs in each LAN the "gateway address" is the IP-address of the router's interface on that PC's LAN.





Here's a scenario using a second router to link the two LANs



  (Internet)
|
+---o-----+ +------+ +------+
|DSL Modem| |switch| |switch|
+---O-----+ +-OOOO-+ +-OOOO-+
| || | | |
+---O--+ || `-. | +O-+
|Router| || | | |PC|
+---O--+ || +O-+ | +--+
| || |PC| |
`-------------'| +--+ |
| |
`----. .----'
| |
+--O-O--+
|Router2|
+-------+

|<--------->|<--------->|
192.168.1.x 192.168.0.x


This is more complicated. Router2 will have a default gateway pointing to the Internet router but will have interfaces in both LANs. If the Internet Router provides DHCP service for the 192.168.1.x LAN, we must make sure that Router2 is configured so it does not also try to provide DHCP service for that LAN. Router 2 should provide DHCP service for 192.168.0.x. Administratively it might be better to make Router 2 provide DHCP service for both LANS and disable DHCP service on the Internet Router - but this may be a less resilient configuration.



If a PC in 192.168.1.x tries to use Router2 to contact the Internet, Router2 will redirect the PC by sending back an ICMP redirect. If a PC in 192.168.1.x tries to use the Internet router to contact the PC in 192.168.0.x, the Internet router will issue a redirect but to do this it has to first be configured to know that router2 is the nearest route to that LAN. I'd typically do this by static config but you could let the routers communicate using RIP or another routing protocol and work it out for themselves.





Update:



You have routers with built-in ethernet switches (pretty common nowadays for small-office/home routers). So you can probably use the "secondary router" as a dumb switch and save yourself a lot of problems.



 (Internet)
|
+--o--+ +--------+ +--------+
|DSL | | Router | | Router |
|modem| | .------| | .------|
+--O--+ | |switch| | |Switch|
| +O--OOOO-+ +O--OOOO-+
| | | || | | ||
`------' | || x | ||
| || | |`-----.
,-' |`-----------' | |
| `--. | |
+O-+ | +O-+ +O-+
|PC| +-O-+ |PC| |PC|
+--+ |NAS| +--+ +--+
+---+

|<---------------------------------->|
all 192.168.1.x


I added another PC on the right hand side, as there's no need for a second switch to serve a single PC. In fact with only four PCs/NAS, you probably have enough LAN ports on the main router alone. But perhaps the right-hand-side PCs are in another room and you only have provision for one cable between rooms.






share|improve this answer


























  • What should i configure in my router, i'm currently on a PC connected to the main router, when im trying to access 192.168.0.1 (Secondery) i get no response. (Request timed out)

    – Danpe
    Mar 23 '12 at 10:05






  • 1





    @RedGrittyBrick Kind of Interest, did you use a program for your nice network layout, or was it created manual? I assume you draw it by yourself. If it so, well done :)

    – JohannesM
    Mar 23 '12 at 10:14











  • @Danpe, it depends on how your LANs and router's are connected - draw us a network diagram and update your question. Specific instructions depend on make and model of routers.

    – RedGrittyBrick
    Mar 23 '12 at 10:35






  • 2





    @JohannesM: The program I used was Notepad :-) It's kind of a little challenge I set myself.

    – RedGrittyBrick
    Mar 23 '12 at 10:35








  • 2





    @Danpe: You can check roting tables in your router's configuration/administration interface (usually a web-page for home routers). My best guess at the cause of the current problem is that the main router doesn't have a route entry for the LAN segment hidden behind your secondary router. HOWEVER - I suspect you would be better off reconfiguring the secondary router as a plain old dumb Ethernet switch. This might mean moving a cable from a port labelled "WAN" to a port labelled "LAN" and disabling all it's DHCP and other services. Two routers and two LANs seems overkill for the average home.

    – RedGrittyBrick
    Mar 23 '12 at 11:24



















2














You may be better off using a single network instead and configuring the second router as a regular switch. If you need seperate LANs however, there is an alternate setup that provides basic functionality but requires less configuration and is available on routers where routing tables are not or hardly manageable.



Connect the second router's WAN interface to the main router's LAN and enable DHCP on both. Make sure both are using the correct LAN IP-addresses and subnets, 192.168.1.1 and 192.168.1.0/24 for the first, 192.168.0.1 and 192.168.0.0/24 for the second. Hosts on seperate networks will probably not be able to see each other, but hosts on the second network can connect to machines on the first.



For instance, the laptop can connect to the network share using \192.168.1.16share. It will not know how to reach this host directly, thus passing on the request to the standard gateway, the second router. The second router will pass it on to its standard gateway, being the main router, which will in turn connect to the known host 192.168.1.16.



The same connection cannot be initiated from the main network, as those machines have no way of reaching the 192.168.0.0/24 subnet without forwarding ports on the second router.






share|improve this answer
























  • "enable DHCP on both" you forgot about (possible) collateral damage - slave router may act as DCHP-relay and transfer DHCP requests on master. I'll not predict exact results (environment- and HW-dependent)

    – Lazy Badger
    Mar 24 '12 at 5:35











  • A DHCP relay would be trouble, but that's exactly why the second network needs a DHCP server of its own, unless you're going for static IP settings. The main router will not properly traverse the second in handing out IPs.

    – Marcks Thomas
    Mar 24 '12 at 10:25



















2














Simplest way is to use only 1 LAN: disable DHCP on 2nd router and plug the cable that come from main router into a LAN port instead of WAN port. All your IPs will be in same subnet and you'll be able to reach everything from everywhere.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f403931%2faccess-my-routers-gateway-network%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









    7















    How can i acces one of them using a PC connected to the Secondery Router?




    Make sure both the routers are properly configured. Each should have a routing table entry for both LANs (192.168.1.x and 192.168.0.x). Such routes can be statically configured or dynamic (using a routing protocol such as RIP).



    Properly configured routers will let PCs know what to do when PCs contact the wrong router (typically by issuing ICMP redirects).





    Here's a scenario using one router to support two LANs and Internet access



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | | | | |
    +---O--+ | +O-+ | +O-+
    |Router| | |PC| | |PC|
    +-O-O--+ | +--+ | +--+
    | | | |
    | `-------------' |
    `----------------------------'

    |<--------->| |<--------->|
    192.168.1.x 192.168.0.x


    The router connects both LANs to the INternet and allows all PCs on both LANs to contact each other. The router provides DHCP service to both LANs, That DHCP service tells PCs in each LAN the "gateway address" is the IP-address of the router's interface on that PC's LAN.





    Here's a scenario using a second router to link the two LANs



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | || | | |
    +---O--+ || `-. | +O-+
    |Router| || | | |PC|
    +---O--+ || +O-+ | +--+
    | || |PC| |
    `-------------'| +--+ |
    | |
    `----. .----'
    | |
    +--O-O--+
    |Router2|
    +-------+

    |<--------->|<--------->|
    192.168.1.x 192.168.0.x


    This is more complicated. Router2 will have a default gateway pointing to the Internet router but will have interfaces in both LANs. If the Internet Router provides DHCP service for the 192.168.1.x LAN, we must make sure that Router2 is configured so it does not also try to provide DHCP service for that LAN. Router 2 should provide DHCP service for 192.168.0.x. Administratively it might be better to make Router 2 provide DHCP service for both LANS and disable DHCP service on the Internet Router - but this may be a less resilient configuration.



    If a PC in 192.168.1.x tries to use Router2 to contact the Internet, Router2 will redirect the PC by sending back an ICMP redirect. If a PC in 192.168.1.x tries to use the Internet router to contact the PC in 192.168.0.x, the Internet router will issue a redirect but to do this it has to first be configured to know that router2 is the nearest route to that LAN. I'd typically do this by static config but you could let the routers communicate using RIP or another routing protocol and work it out for themselves.





    Update:



    You have routers with built-in ethernet switches (pretty common nowadays for small-office/home routers). So you can probably use the "secondary router" as a dumb switch and save yourself a lot of problems.



     (Internet)
    |
    +--o--+ +--------+ +--------+
    |DSL | | Router | | Router |
    |modem| | .------| | .------|
    +--O--+ | |switch| | |Switch|
    | +O--OOOO-+ +O--OOOO-+
    | | | || | | ||
    `------' | || x | ||
    | || | |`-----.
    ,-' |`-----------' | |
    | `--. | |
    +O-+ | +O-+ +O-+
    |PC| +-O-+ |PC| |PC|
    +--+ |NAS| +--+ +--+
    +---+

    |<---------------------------------->|
    all 192.168.1.x


    I added another PC on the right hand side, as there's no need for a second switch to serve a single PC. In fact with only four PCs/NAS, you probably have enough LAN ports on the main router alone. But perhaps the right-hand-side PCs are in another room and you only have provision for one cable between rooms.






    share|improve this answer


























    • What should i configure in my router, i'm currently on a PC connected to the main router, when im trying to access 192.168.0.1 (Secondery) i get no response. (Request timed out)

      – Danpe
      Mar 23 '12 at 10:05






    • 1





      @RedGrittyBrick Kind of Interest, did you use a program for your nice network layout, or was it created manual? I assume you draw it by yourself. If it so, well done :)

      – JohannesM
      Mar 23 '12 at 10:14











    • @Danpe, it depends on how your LANs and router's are connected - draw us a network diagram and update your question. Specific instructions depend on make and model of routers.

      – RedGrittyBrick
      Mar 23 '12 at 10:35






    • 2





      @JohannesM: The program I used was Notepad :-) It's kind of a little challenge I set myself.

      – RedGrittyBrick
      Mar 23 '12 at 10:35








    • 2





      @Danpe: You can check roting tables in your router's configuration/administration interface (usually a web-page for home routers). My best guess at the cause of the current problem is that the main router doesn't have a route entry for the LAN segment hidden behind your secondary router. HOWEVER - I suspect you would be better off reconfiguring the secondary router as a plain old dumb Ethernet switch. This might mean moving a cable from a port labelled "WAN" to a port labelled "LAN" and disabling all it's DHCP and other services. Two routers and two LANs seems overkill for the average home.

      – RedGrittyBrick
      Mar 23 '12 at 11:24
















    7















    How can i acces one of them using a PC connected to the Secondery Router?




    Make sure both the routers are properly configured. Each should have a routing table entry for both LANs (192.168.1.x and 192.168.0.x). Such routes can be statically configured or dynamic (using a routing protocol such as RIP).



    Properly configured routers will let PCs know what to do when PCs contact the wrong router (typically by issuing ICMP redirects).





    Here's a scenario using one router to support two LANs and Internet access



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | | | | |
    +---O--+ | +O-+ | +O-+
    |Router| | |PC| | |PC|
    +-O-O--+ | +--+ | +--+
    | | | |
    | `-------------' |
    `----------------------------'

    |<--------->| |<--------->|
    192.168.1.x 192.168.0.x


    The router connects both LANs to the INternet and allows all PCs on both LANs to contact each other. The router provides DHCP service to both LANs, That DHCP service tells PCs in each LAN the "gateway address" is the IP-address of the router's interface on that PC's LAN.





    Here's a scenario using a second router to link the two LANs



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | || | | |
    +---O--+ || `-. | +O-+
    |Router| || | | |PC|
    +---O--+ || +O-+ | +--+
    | || |PC| |
    `-------------'| +--+ |
    | |
    `----. .----'
    | |
    +--O-O--+
    |Router2|
    +-------+

    |<--------->|<--------->|
    192.168.1.x 192.168.0.x


    This is more complicated. Router2 will have a default gateway pointing to the Internet router but will have interfaces in both LANs. If the Internet Router provides DHCP service for the 192.168.1.x LAN, we must make sure that Router2 is configured so it does not also try to provide DHCP service for that LAN. Router 2 should provide DHCP service for 192.168.0.x. Administratively it might be better to make Router 2 provide DHCP service for both LANS and disable DHCP service on the Internet Router - but this may be a less resilient configuration.



    If a PC in 192.168.1.x tries to use Router2 to contact the Internet, Router2 will redirect the PC by sending back an ICMP redirect. If a PC in 192.168.1.x tries to use the Internet router to contact the PC in 192.168.0.x, the Internet router will issue a redirect but to do this it has to first be configured to know that router2 is the nearest route to that LAN. I'd typically do this by static config but you could let the routers communicate using RIP or another routing protocol and work it out for themselves.





    Update:



    You have routers with built-in ethernet switches (pretty common nowadays for small-office/home routers). So you can probably use the "secondary router" as a dumb switch and save yourself a lot of problems.



     (Internet)
    |
    +--o--+ +--------+ +--------+
    |DSL | | Router | | Router |
    |modem| | .------| | .------|
    +--O--+ | |switch| | |Switch|
    | +O--OOOO-+ +O--OOOO-+
    | | | || | | ||
    `------' | || x | ||
    | || | |`-----.
    ,-' |`-----------' | |
    | `--. | |
    +O-+ | +O-+ +O-+
    |PC| +-O-+ |PC| |PC|
    +--+ |NAS| +--+ +--+
    +---+

    |<---------------------------------->|
    all 192.168.1.x


    I added another PC on the right hand side, as there's no need for a second switch to serve a single PC. In fact with only four PCs/NAS, you probably have enough LAN ports on the main router alone. But perhaps the right-hand-side PCs are in another room and you only have provision for one cable between rooms.






    share|improve this answer


























    • What should i configure in my router, i'm currently on a PC connected to the main router, when im trying to access 192.168.0.1 (Secondery) i get no response. (Request timed out)

      – Danpe
      Mar 23 '12 at 10:05






    • 1





      @RedGrittyBrick Kind of Interest, did you use a program for your nice network layout, or was it created manual? I assume you draw it by yourself. If it so, well done :)

      – JohannesM
      Mar 23 '12 at 10:14











    • @Danpe, it depends on how your LANs and router's are connected - draw us a network diagram and update your question. Specific instructions depend on make and model of routers.

      – RedGrittyBrick
      Mar 23 '12 at 10:35






    • 2





      @JohannesM: The program I used was Notepad :-) It's kind of a little challenge I set myself.

      – RedGrittyBrick
      Mar 23 '12 at 10:35








    • 2





      @Danpe: You can check roting tables in your router's configuration/administration interface (usually a web-page for home routers). My best guess at the cause of the current problem is that the main router doesn't have a route entry for the LAN segment hidden behind your secondary router. HOWEVER - I suspect you would be better off reconfiguring the secondary router as a plain old dumb Ethernet switch. This might mean moving a cable from a port labelled "WAN" to a port labelled "LAN" and disabling all it's DHCP and other services. Two routers and two LANs seems overkill for the average home.

      – RedGrittyBrick
      Mar 23 '12 at 11:24














    7












    7








    7








    How can i acces one of them using a PC connected to the Secondery Router?




    Make sure both the routers are properly configured. Each should have a routing table entry for both LANs (192.168.1.x and 192.168.0.x). Such routes can be statically configured or dynamic (using a routing protocol such as RIP).



    Properly configured routers will let PCs know what to do when PCs contact the wrong router (typically by issuing ICMP redirects).





    Here's a scenario using one router to support two LANs and Internet access



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | | | | |
    +---O--+ | +O-+ | +O-+
    |Router| | |PC| | |PC|
    +-O-O--+ | +--+ | +--+
    | | | |
    | `-------------' |
    `----------------------------'

    |<--------->| |<--------->|
    192.168.1.x 192.168.0.x


    The router connects both LANs to the INternet and allows all PCs on both LANs to contact each other. The router provides DHCP service to both LANs, That DHCP service tells PCs in each LAN the "gateway address" is the IP-address of the router's interface on that PC's LAN.





    Here's a scenario using a second router to link the two LANs



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | || | | |
    +---O--+ || `-. | +O-+
    |Router| || | | |PC|
    +---O--+ || +O-+ | +--+
    | || |PC| |
    `-------------'| +--+ |
    | |
    `----. .----'
    | |
    +--O-O--+
    |Router2|
    +-------+

    |<--------->|<--------->|
    192.168.1.x 192.168.0.x


    This is more complicated. Router2 will have a default gateway pointing to the Internet router but will have interfaces in both LANs. If the Internet Router provides DHCP service for the 192.168.1.x LAN, we must make sure that Router2 is configured so it does not also try to provide DHCP service for that LAN. Router 2 should provide DHCP service for 192.168.0.x. Administratively it might be better to make Router 2 provide DHCP service for both LANS and disable DHCP service on the Internet Router - but this may be a less resilient configuration.



    If a PC in 192.168.1.x tries to use Router2 to contact the Internet, Router2 will redirect the PC by sending back an ICMP redirect. If a PC in 192.168.1.x tries to use the Internet router to contact the PC in 192.168.0.x, the Internet router will issue a redirect but to do this it has to first be configured to know that router2 is the nearest route to that LAN. I'd typically do this by static config but you could let the routers communicate using RIP or another routing protocol and work it out for themselves.





    Update:



    You have routers with built-in ethernet switches (pretty common nowadays for small-office/home routers). So you can probably use the "secondary router" as a dumb switch and save yourself a lot of problems.



     (Internet)
    |
    +--o--+ +--------+ +--------+
    |DSL | | Router | | Router |
    |modem| | .------| | .------|
    +--O--+ | |switch| | |Switch|
    | +O--OOOO-+ +O--OOOO-+
    | | | || | | ||
    `------' | || x | ||
    | || | |`-----.
    ,-' |`-----------' | |
    | `--. | |
    +O-+ | +O-+ +O-+
    |PC| +-O-+ |PC| |PC|
    +--+ |NAS| +--+ +--+
    +---+

    |<---------------------------------->|
    all 192.168.1.x


    I added another PC on the right hand side, as there's no need for a second switch to serve a single PC. In fact with only four PCs/NAS, you probably have enough LAN ports on the main router alone. But perhaps the right-hand-side PCs are in another room and you only have provision for one cable between rooms.






    share|improve this answer
















    How can i acces one of them using a PC connected to the Secondery Router?




    Make sure both the routers are properly configured. Each should have a routing table entry for both LANs (192.168.1.x and 192.168.0.x). Such routes can be statically configured or dynamic (using a routing protocol such as RIP).



    Properly configured routers will let PCs know what to do when PCs contact the wrong router (typically by issuing ICMP redirects).





    Here's a scenario using one router to support two LANs and Internet access



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | | | | |
    +---O--+ | +O-+ | +O-+
    |Router| | |PC| | |PC|
    +-O-O--+ | +--+ | +--+
    | | | |
    | `-------------' |
    `----------------------------'

    |<--------->| |<--------->|
    192.168.1.x 192.168.0.x


    The router connects both LANs to the INternet and allows all PCs on both LANs to contact each other. The router provides DHCP service to both LANs, That DHCP service tells PCs in each LAN the "gateway address" is the IP-address of the router's interface on that PC's LAN.





    Here's a scenario using a second router to link the two LANs



      (Internet)
    |
    +---o-----+ +------+ +------+
    |DSL Modem| |switch| |switch|
    +---O-----+ +-OOOO-+ +-OOOO-+
    | || | | |
    +---O--+ || `-. | +O-+
    |Router| || | | |PC|
    +---O--+ || +O-+ | +--+
    | || |PC| |
    `-------------'| +--+ |
    | |
    `----. .----'
    | |
    +--O-O--+
    |Router2|
    +-------+

    |<--------->|<--------->|
    192.168.1.x 192.168.0.x


    This is more complicated. Router2 will have a default gateway pointing to the Internet router but will have interfaces in both LANs. If the Internet Router provides DHCP service for the 192.168.1.x LAN, we must make sure that Router2 is configured so it does not also try to provide DHCP service for that LAN. Router 2 should provide DHCP service for 192.168.0.x. Administratively it might be better to make Router 2 provide DHCP service for both LANS and disable DHCP service on the Internet Router - but this may be a less resilient configuration.



    If a PC in 192.168.1.x tries to use Router2 to contact the Internet, Router2 will redirect the PC by sending back an ICMP redirect. If a PC in 192.168.1.x tries to use the Internet router to contact the PC in 192.168.0.x, the Internet router will issue a redirect but to do this it has to first be configured to know that router2 is the nearest route to that LAN. I'd typically do this by static config but you could let the routers communicate using RIP or another routing protocol and work it out for themselves.





    Update:



    You have routers with built-in ethernet switches (pretty common nowadays for small-office/home routers). So you can probably use the "secondary router" as a dumb switch and save yourself a lot of problems.



     (Internet)
    |
    +--o--+ +--------+ +--------+
    |DSL | | Router | | Router |
    |modem| | .------| | .------|
    +--O--+ | |switch| | |Switch|
    | +O--OOOO-+ +O--OOOO-+
    | | | || | | ||
    `------' | || x | ||
    | || | |`-----.
    ,-' |`-----------' | |
    | `--. | |
    +O-+ | +O-+ +O-+
    |PC| +-O-+ |PC| |PC|
    +--+ |NAS| +--+ +--+
    +---+

    |<---------------------------------->|
    all 192.168.1.x


    I added another PC on the right hand side, as there's no need for a second switch to serve a single PC. In fact with only four PCs/NAS, you probably have enough LAN ports on the main router alone. But perhaps the right-hand-side PCs are in another room and you only have provision for one cable between rooms.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 23 '12 at 17:01

























    answered Mar 23 '12 at 9:55









    RedGrittyBrickRedGrittyBrick

    67.2k13106163




    67.2k13106163













    • What should i configure in my router, i'm currently on a PC connected to the main router, when im trying to access 192.168.0.1 (Secondery) i get no response. (Request timed out)

      – Danpe
      Mar 23 '12 at 10:05






    • 1





      @RedGrittyBrick Kind of Interest, did you use a program for your nice network layout, or was it created manual? I assume you draw it by yourself. If it so, well done :)

      – JohannesM
      Mar 23 '12 at 10:14











    • @Danpe, it depends on how your LANs and router's are connected - draw us a network diagram and update your question. Specific instructions depend on make and model of routers.

      – RedGrittyBrick
      Mar 23 '12 at 10:35






    • 2





      @JohannesM: The program I used was Notepad :-) It's kind of a little challenge I set myself.

      – RedGrittyBrick
      Mar 23 '12 at 10:35








    • 2





      @Danpe: You can check roting tables in your router's configuration/administration interface (usually a web-page for home routers). My best guess at the cause of the current problem is that the main router doesn't have a route entry for the LAN segment hidden behind your secondary router. HOWEVER - I suspect you would be better off reconfiguring the secondary router as a plain old dumb Ethernet switch. This might mean moving a cable from a port labelled "WAN" to a port labelled "LAN" and disabling all it's DHCP and other services. Two routers and two LANs seems overkill for the average home.

      – RedGrittyBrick
      Mar 23 '12 at 11:24



















    • What should i configure in my router, i'm currently on a PC connected to the main router, when im trying to access 192.168.0.1 (Secondery) i get no response. (Request timed out)

      – Danpe
      Mar 23 '12 at 10:05






    • 1





      @RedGrittyBrick Kind of Interest, did you use a program for your nice network layout, or was it created manual? I assume you draw it by yourself. If it so, well done :)

      – JohannesM
      Mar 23 '12 at 10:14











    • @Danpe, it depends on how your LANs and router's are connected - draw us a network diagram and update your question. Specific instructions depend on make and model of routers.

      – RedGrittyBrick
      Mar 23 '12 at 10:35






    • 2





      @JohannesM: The program I used was Notepad :-) It's kind of a little challenge I set myself.

      – RedGrittyBrick
      Mar 23 '12 at 10:35








    • 2





      @Danpe: You can check roting tables in your router's configuration/administration interface (usually a web-page for home routers). My best guess at the cause of the current problem is that the main router doesn't have a route entry for the LAN segment hidden behind your secondary router. HOWEVER - I suspect you would be better off reconfiguring the secondary router as a plain old dumb Ethernet switch. This might mean moving a cable from a port labelled "WAN" to a port labelled "LAN" and disabling all it's DHCP and other services. Two routers and two LANs seems overkill for the average home.

      – RedGrittyBrick
      Mar 23 '12 at 11:24

















    What should i configure in my router, i'm currently on a PC connected to the main router, when im trying to access 192.168.0.1 (Secondery) i get no response. (Request timed out)

    – Danpe
    Mar 23 '12 at 10:05





    What should i configure in my router, i'm currently on a PC connected to the main router, when im trying to access 192.168.0.1 (Secondery) i get no response. (Request timed out)

    – Danpe
    Mar 23 '12 at 10:05




    1




    1





    @RedGrittyBrick Kind of Interest, did you use a program for your nice network layout, or was it created manual? I assume you draw it by yourself. If it so, well done :)

    – JohannesM
    Mar 23 '12 at 10:14





    @RedGrittyBrick Kind of Interest, did you use a program for your nice network layout, or was it created manual? I assume you draw it by yourself. If it so, well done :)

    – JohannesM
    Mar 23 '12 at 10:14













    @Danpe, it depends on how your LANs and router's are connected - draw us a network diagram and update your question. Specific instructions depend on make and model of routers.

    – RedGrittyBrick
    Mar 23 '12 at 10:35





    @Danpe, it depends on how your LANs and router's are connected - draw us a network diagram and update your question. Specific instructions depend on make and model of routers.

    – RedGrittyBrick
    Mar 23 '12 at 10:35




    2




    2





    @JohannesM: The program I used was Notepad :-) It's kind of a little challenge I set myself.

    – RedGrittyBrick
    Mar 23 '12 at 10:35







    @JohannesM: The program I used was Notepad :-) It's kind of a little challenge I set myself.

    – RedGrittyBrick
    Mar 23 '12 at 10:35






    2




    2





    @Danpe: You can check roting tables in your router's configuration/administration interface (usually a web-page for home routers). My best guess at the cause of the current problem is that the main router doesn't have a route entry for the LAN segment hidden behind your secondary router. HOWEVER - I suspect you would be better off reconfiguring the secondary router as a plain old dumb Ethernet switch. This might mean moving a cable from a port labelled "WAN" to a port labelled "LAN" and disabling all it's DHCP and other services. Two routers and two LANs seems overkill for the average home.

    – RedGrittyBrick
    Mar 23 '12 at 11:24





    @Danpe: You can check roting tables in your router's configuration/administration interface (usually a web-page for home routers). My best guess at the cause of the current problem is that the main router doesn't have a route entry for the LAN segment hidden behind your secondary router. HOWEVER - I suspect you would be better off reconfiguring the secondary router as a plain old dumb Ethernet switch. This might mean moving a cable from a port labelled "WAN" to a port labelled "LAN" and disabling all it's DHCP and other services. Two routers and two LANs seems overkill for the average home.

    – RedGrittyBrick
    Mar 23 '12 at 11:24













    2














    You may be better off using a single network instead and configuring the second router as a regular switch. If you need seperate LANs however, there is an alternate setup that provides basic functionality but requires less configuration and is available on routers where routing tables are not or hardly manageable.



    Connect the second router's WAN interface to the main router's LAN and enable DHCP on both. Make sure both are using the correct LAN IP-addresses and subnets, 192.168.1.1 and 192.168.1.0/24 for the first, 192.168.0.1 and 192.168.0.0/24 for the second. Hosts on seperate networks will probably not be able to see each other, but hosts on the second network can connect to machines on the first.



    For instance, the laptop can connect to the network share using \192.168.1.16share. It will not know how to reach this host directly, thus passing on the request to the standard gateway, the second router. The second router will pass it on to its standard gateway, being the main router, which will in turn connect to the known host 192.168.1.16.



    The same connection cannot be initiated from the main network, as those machines have no way of reaching the 192.168.0.0/24 subnet without forwarding ports on the second router.






    share|improve this answer
























    • "enable DHCP on both" you forgot about (possible) collateral damage - slave router may act as DCHP-relay and transfer DHCP requests on master. I'll not predict exact results (environment- and HW-dependent)

      – Lazy Badger
      Mar 24 '12 at 5:35











    • A DHCP relay would be trouble, but that's exactly why the second network needs a DHCP server of its own, unless you're going for static IP settings. The main router will not properly traverse the second in handing out IPs.

      – Marcks Thomas
      Mar 24 '12 at 10:25
















    2














    You may be better off using a single network instead and configuring the second router as a regular switch. If you need seperate LANs however, there is an alternate setup that provides basic functionality but requires less configuration and is available on routers where routing tables are not or hardly manageable.



    Connect the second router's WAN interface to the main router's LAN and enable DHCP on both. Make sure both are using the correct LAN IP-addresses and subnets, 192.168.1.1 and 192.168.1.0/24 for the first, 192.168.0.1 and 192.168.0.0/24 for the second. Hosts on seperate networks will probably not be able to see each other, but hosts on the second network can connect to machines on the first.



    For instance, the laptop can connect to the network share using \192.168.1.16share. It will not know how to reach this host directly, thus passing on the request to the standard gateway, the second router. The second router will pass it on to its standard gateway, being the main router, which will in turn connect to the known host 192.168.1.16.



    The same connection cannot be initiated from the main network, as those machines have no way of reaching the 192.168.0.0/24 subnet without forwarding ports on the second router.






    share|improve this answer
























    • "enable DHCP on both" you forgot about (possible) collateral damage - slave router may act as DCHP-relay and transfer DHCP requests on master. I'll not predict exact results (environment- and HW-dependent)

      – Lazy Badger
      Mar 24 '12 at 5:35











    • A DHCP relay would be trouble, but that's exactly why the second network needs a DHCP server of its own, unless you're going for static IP settings. The main router will not properly traverse the second in handing out IPs.

      – Marcks Thomas
      Mar 24 '12 at 10:25














    2












    2








    2







    You may be better off using a single network instead and configuring the second router as a regular switch. If you need seperate LANs however, there is an alternate setup that provides basic functionality but requires less configuration and is available on routers where routing tables are not or hardly manageable.



    Connect the second router's WAN interface to the main router's LAN and enable DHCP on both. Make sure both are using the correct LAN IP-addresses and subnets, 192.168.1.1 and 192.168.1.0/24 for the first, 192.168.0.1 and 192.168.0.0/24 for the second. Hosts on seperate networks will probably not be able to see each other, but hosts on the second network can connect to machines on the first.



    For instance, the laptop can connect to the network share using \192.168.1.16share. It will not know how to reach this host directly, thus passing on the request to the standard gateway, the second router. The second router will pass it on to its standard gateway, being the main router, which will in turn connect to the known host 192.168.1.16.



    The same connection cannot be initiated from the main network, as those machines have no way of reaching the 192.168.0.0/24 subnet without forwarding ports on the second router.






    share|improve this answer













    You may be better off using a single network instead and configuring the second router as a regular switch. If you need seperate LANs however, there is an alternate setup that provides basic functionality but requires less configuration and is available on routers where routing tables are not or hardly manageable.



    Connect the second router's WAN interface to the main router's LAN and enable DHCP on both. Make sure both are using the correct LAN IP-addresses and subnets, 192.168.1.1 and 192.168.1.0/24 for the first, 192.168.0.1 and 192.168.0.0/24 for the second. Hosts on seperate networks will probably not be able to see each other, but hosts on the second network can connect to machines on the first.



    For instance, the laptop can connect to the network share using \192.168.1.16share. It will not know how to reach this host directly, thus passing on the request to the standard gateway, the second router. The second router will pass it on to its standard gateway, being the main router, which will in turn connect to the known host 192.168.1.16.



    The same connection cannot be initiated from the main network, as those machines have no way of reaching the 192.168.0.0/24 subnet without forwarding ports on the second router.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Mar 23 '12 at 12:16









    Marcks ThomasMarcks Thomas

    5,55411736




    5,55411736













    • "enable DHCP on both" you forgot about (possible) collateral damage - slave router may act as DCHP-relay and transfer DHCP requests on master. I'll not predict exact results (environment- and HW-dependent)

      – Lazy Badger
      Mar 24 '12 at 5:35











    • A DHCP relay would be trouble, but that's exactly why the second network needs a DHCP server of its own, unless you're going for static IP settings. The main router will not properly traverse the second in handing out IPs.

      – Marcks Thomas
      Mar 24 '12 at 10:25



















    • "enable DHCP on both" you forgot about (possible) collateral damage - slave router may act as DCHP-relay and transfer DHCP requests on master. I'll not predict exact results (environment- and HW-dependent)

      – Lazy Badger
      Mar 24 '12 at 5:35











    • A DHCP relay would be trouble, but that's exactly why the second network needs a DHCP server of its own, unless you're going for static IP settings. The main router will not properly traverse the second in handing out IPs.

      – Marcks Thomas
      Mar 24 '12 at 10:25

















    "enable DHCP on both" you forgot about (possible) collateral damage - slave router may act as DCHP-relay and transfer DHCP requests on master. I'll not predict exact results (environment- and HW-dependent)

    – Lazy Badger
    Mar 24 '12 at 5:35





    "enable DHCP on both" you forgot about (possible) collateral damage - slave router may act as DCHP-relay and transfer DHCP requests on master. I'll not predict exact results (environment- and HW-dependent)

    – Lazy Badger
    Mar 24 '12 at 5:35













    A DHCP relay would be trouble, but that's exactly why the second network needs a DHCP server of its own, unless you're going for static IP settings. The main router will not properly traverse the second in handing out IPs.

    – Marcks Thomas
    Mar 24 '12 at 10:25





    A DHCP relay would be trouble, but that's exactly why the second network needs a DHCP server of its own, unless you're going for static IP settings. The main router will not properly traverse the second in handing out IPs.

    – Marcks Thomas
    Mar 24 '12 at 10:25











    2














    Simplest way is to use only 1 LAN: disable DHCP on 2nd router and plug the cable that come from main router into a LAN port instead of WAN port. All your IPs will be in same subnet and you'll be able to reach everything from everywhere.






    share|improve this answer




























      2














      Simplest way is to use only 1 LAN: disable DHCP on 2nd router and plug the cable that come from main router into a LAN port instead of WAN port. All your IPs will be in same subnet and you'll be able to reach everything from everywhere.






      share|improve this answer


























        2












        2








        2







        Simplest way is to use only 1 LAN: disable DHCP on 2nd router and plug the cable that come from main router into a LAN port instead of WAN port. All your IPs will be in same subnet and you'll be able to reach everything from everywhere.






        share|improve this answer













        Simplest way is to use only 1 LAN: disable DHCP on 2nd router and plug the cable that come from main router into a LAN port instead of WAN port. All your IPs will be in same subnet and you'll be able to reach everything from everywhere.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 23 '12 at 12:35









        laurentlaurent

        4,1081522




        4,1081522






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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%2fsuperuser.com%2fquestions%2f403931%2faccess-my-routers-gateway-network%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

            VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

            Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

            looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...