Allow two subnets to talk to each other over a wireless bridge Announcing the arrival of...

How to find all the available tools in mac terminal?

How to bypass password on Windows XP account?

Storing hydrofluoric acid before the invention of plastics

The logistics of corpse disposal

When a candle burns, why does the top of wick glow if bottom of flame is hottest?

Can inflation occur in a positive-sum game currency system such as the Stack Exchange reputation system?

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?

How to tell that you are a giant?

Why is "Consequences inflicted." not a sentence?

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

Echoing a tail command produces unexpected output?

How does debian/ubuntu knows a package has a updated version

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

How to align text above triangle figure

List of Python versions

Bete Noir -- no dairy

Why are Kinder Surprise Eggs illegal in the USA?

How do I keep my slimes from escaping their pens?

What causes the vertical darker bands in my photo?

What is Arya's weapon design?

Is it fair for a professor to grade us on the possession of past papers?

When were vectors invented?

Seeking colloquialism for “just because”

What is the meaning of the new sigil in Game of Thrones Season 8 intro?



Allow two subnets to talk to each other over a wireless bridge



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Crossing two subnets on home networkConfiguring network route between two routers on home networkWhy are computers not seeing each other over Wifi?Troubleshooting wireless client-bridged networks between two DD-WRT routers?2 Subnets see each otherConfiguring 2 routers on same home LANTwo routers for two subnetsRunning a network of two wireless routers on a switch and two different DHCP servers plus some static ip addressesHow to setup two-way routing with Tomato Wireless Client mode (different subnets)how to configure isc dchp server with different subnets with different wl-access points





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have two subnets connected over a wireless bridge and I'm trying to figure out how to get them to talk to each other.



Subnet 1




  • Router: Netgear wireless

  • Router IP: 192.168.1.1

  • DHCP range: 192.168.1.2 - 192.168.1.254

  • Subnet mask: 255.255.255.0

  • Internet: Connected directly to cable modem


Subnet 2




  • Router: Linksys running dd-wrt

  • Router IP: 192.168.2.1

  • DHCP range: 192.168.2.2 - 192.168.2.254

  • Internet: Connected to the Netgear router via a wireless bridge

  • WAN IP: 192.168.1.10


When I'm on Subnet 1, I can't connect to anything on Subnet 2 (even the wireless bridge IP of 192.168.1.10).



When I'm on Subnet 2, I can connect to everything on 192.168.2.* as well as the Subnet 1 router on 192.168.1.1. But I can't connect to any other machines on Subnet 1.



The physical limitations of my house make the wireless bridge a requirement. I don't think making a wired connection between the two subnets is an option.



How can I set things up so machines on both subnets can communicate with each other and still get to the Internet?










share|improve this question























  • You could set the subnet mask on all machines to 255.255.224.0 This way your host IP address range is 192.168.0.1 - 192.168.31.254, which includes both subnets you mention.

    – user421696
    Jan 31 '16 at 14:21






  • 2





    Wired or wireless is just a medium, the "network" it carriers is mostly not relevant to the actual medium. If this is a wireless bridge, why is the second router providing DHCP and not just transparently passing the 192.168.1.0/24 network through? That would make this so much simpler, router one provides DHCP to everything, and router 2 just acts a bridge passing the wireless network to the wired ports. Sounds to me like this is misconfigured since this is a SOHO environment.

    – acejavelin
    Jan 31 '16 at 14:31











  • I tried changing the subnet at one point and it still wasn't working. Would I have to do anything in terms of setting the Gateway on Subnet 2 for that to work?

    – Mark Biek
    Jan 31 '16 at 14:31













  • I'll take a look and see about disabling the secondary DHCP and just making it all one big 192.168.1.0 network.

    – Mark Biek
    Jan 31 '16 at 14:32






  • 2





    Your router 2 is misconfigured, it should not be doing any router or DHCP functions, everything should be handled by router 1. Router 2 should be just a pass-though of the network. Everything should be one 192.168.1.0/24 subnet with a gateway of 192.168.1.1

    – acejavelin
    Jan 31 '16 at 14:33


















0















I have two subnets connected over a wireless bridge and I'm trying to figure out how to get them to talk to each other.



Subnet 1




  • Router: Netgear wireless

  • Router IP: 192.168.1.1

  • DHCP range: 192.168.1.2 - 192.168.1.254

  • Subnet mask: 255.255.255.0

  • Internet: Connected directly to cable modem


Subnet 2




  • Router: Linksys running dd-wrt

  • Router IP: 192.168.2.1

  • DHCP range: 192.168.2.2 - 192.168.2.254

  • Internet: Connected to the Netgear router via a wireless bridge

  • WAN IP: 192.168.1.10


When I'm on Subnet 1, I can't connect to anything on Subnet 2 (even the wireless bridge IP of 192.168.1.10).



When I'm on Subnet 2, I can connect to everything on 192.168.2.* as well as the Subnet 1 router on 192.168.1.1. But I can't connect to any other machines on Subnet 1.



The physical limitations of my house make the wireless bridge a requirement. I don't think making a wired connection between the two subnets is an option.



How can I set things up so machines on both subnets can communicate with each other and still get to the Internet?










share|improve this question























  • You could set the subnet mask on all machines to 255.255.224.0 This way your host IP address range is 192.168.0.1 - 192.168.31.254, which includes both subnets you mention.

    – user421696
    Jan 31 '16 at 14:21






  • 2





    Wired or wireless is just a medium, the "network" it carriers is mostly not relevant to the actual medium. If this is a wireless bridge, why is the second router providing DHCP and not just transparently passing the 192.168.1.0/24 network through? That would make this so much simpler, router one provides DHCP to everything, and router 2 just acts a bridge passing the wireless network to the wired ports. Sounds to me like this is misconfigured since this is a SOHO environment.

    – acejavelin
    Jan 31 '16 at 14:31











  • I tried changing the subnet at one point and it still wasn't working. Would I have to do anything in terms of setting the Gateway on Subnet 2 for that to work?

    – Mark Biek
    Jan 31 '16 at 14:31













  • I'll take a look and see about disabling the secondary DHCP and just making it all one big 192.168.1.0 network.

    – Mark Biek
    Jan 31 '16 at 14:32






  • 2





    Your router 2 is misconfigured, it should not be doing any router or DHCP functions, everything should be handled by router 1. Router 2 should be just a pass-though of the network. Everything should be one 192.168.1.0/24 subnet with a gateway of 192.168.1.1

    – acejavelin
    Jan 31 '16 at 14:33














0












0








0








I have two subnets connected over a wireless bridge and I'm trying to figure out how to get them to talk to each other.



Subnet 1




  • Router: Netgear wireless

  • Router IP: 192.168.1.1

  • DHCP range: 192.168.1.2 - 192.168.1.254

  • Subnet mask: 255.255.255.0

  • Internet: Connected directly to cable modem


Subnet 2




  • Router: Linksys running dd-wrt

  • Router IP: 192.168.2.1

  • DHCP range: 192.168.2.2 - 192.168.2.254

  • Internet: Connected to the Netgear router via a wireless bridge

  • WAN IP: 192.168.1.10


When I'm on Subnet 1, I can't connect to anything on Subnet 2 (even the wireless bridge IP of 192.168.1.10).



When I'm on Subnet 2, I can connect to everything on 192.168.2.* as well as the Subnet 1 router on 192.168.1.1. But I can't connect to any other machines on Subnet 1.



The physical limitations of my house make the wireless bridge a requirement. I don't think making a wired connection between the two subnets is an option.



How can I set things up so machines on both subnets can communicate with each other and still get to the Internet?










share|improve this question














I have two subnets connected over a wireless bridge and I'm trying to figure out how to get them to talk to each other.



Subnet 1




  • Router: Netgear wireless

  • Router IP: 192.168.1.1

  • DHCP range: 192.168.1.2 - 192.168.1.254

  • Subnet mask: 255.255.255.0

  • Internet: Connected directly to cable modem


Subnet 2




  • Router: Linksys running dd-wrt

  • Router IP: 192.168.2.1

  • DHCP range: 192.168.2.2 - 192.168.2.254

  • Internet: Connected to the Netgear router via a wireless bridge

  • WAN IP: 192.168.1.10


When I'm on Subnet 1, I can't connect to anything on Subnet 2 (even the wireless bridge IP of 192.168.1.10).



When I'm on Subnet 2, I can connect to everything on 192.168.2.* as well as the Subnet 1 router on 192.168.1.1. But I can't connect to any other machines on Subnet 1.



The physical limitations of my house make the wireless bridge a requirement. I don't think making a wired connection between the two subnets is an option.



How can I set things up so machines on both subnets can communicate with each other and still get to the Internet?







networking wireless-networking wireless-router dd-wrt






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 31 '16 at 14:11









Mark BiekMark Biek

20315




20315













  • You could set the subnet mask on all machines to 255.255.224.0 This way your host IP address range is 192.168.0.1 - 192.168.31.254, which includes both subnets you mention.

    – user421696
    Jan 31 '16 at 14:21






  • 2





    Wired or wireless is just a medium, the "network" it carriers is mostly not relevant to the actual medium. If this is a wireless bridge, why is the second router providing DHCP and not just transparently passing the 192.168.1.0/24 network through? That would make this so much simpler, router one provides DHCP to everything, and router 2 just acts a bridge passing the wireless network to the wired ports. Sounds to me like this is misconfigured since this is a SOHO environment.

    – acejavelin
    Jan 31 '16 at 14:31











  • I tried changing the subnet at one point and it still wasn't working. Would I have to do anything in terms of setting the Gateway on Subnet 2 for that to work?

    – Mark Biek
    Jan 31 '16 at 14:31













  • I'll take a look and see about disabling the secondary DHCP and just making it all one big 192.168.1.0 network.

    – Mark Biek
    Jan 31 '16 at 14:32






  • 2





    Your router 2 is misconfigured, it should not be doing any router or DHCP functions, everything should be handled by router 1. Router 2 should be just a pass-though of the network. Everything should be one 192.168.1.0/24 subnet with a gateway of 192.168.1.1

    – acejavelin
    Jan 31 '16 at 14:33



















  • You could set the subnet mask on all machines to 255.255.224.0 This way your host IP address range is 192.168.0.1 - 192.168.31.254, which includes both subnets you mention.

    – user421696
    Jan 31 '16 at 14:21






  • 2





    Wired or wireless is just a medium, the "network" it carriers is mostly not relevant to the actual medium. If this is a wireless bridge, why is the second router providing DHCP and not just transparently passing the 192.168.1.0/24 network through? That would make this so much simpler, router one provides DHCP to everything, and router 2 just acts a bridge passing the wireless network to the wired ports. Sounds to me like this is misconfigured since this is a SOHO environment.

    – acejavelin
    Jan 31 '16 at 14:31











  • I tried changing the subnet at one point and it still wasn't working. Would I have to do anything in terms of setting the Gateway on Subnet 2 for that to work?

    – Mark Biek
    Jan 31 '16 at 14:31













  • I'll take a look and see about disabling the secondary DHCP and just making it all one big 192.168.1.0 network.

    – Mark Biek
    Jan 31 '16 at 14:32






  • 2





    Your router 2 is misconfigured, it should not be doing any router or DHCP functions, everything should be handled by router 1. Router 2 should be just a pass-though of the network. Everything should be one 192.168.1.0/24 subnet with a gateway of 192.168.1.1

    – acejavelin
    Jan 31 '16 at 14:33

















You could set the subnet mask on all machines to 255.255.224.0 This way your host IP address range is 192.168.0.1 - 192.168.31.254, which includes both subnets you mention.

– user421696
Jan 31 '16 at 14:21





You could set the subnet mask on all machines to 255.255.224.0 This way your host IP address range is 192.168.0.1 - 192.168.31.254, which includes both subnets you mention.

– user421696
Jan 31 '16 at 14:21




2




2





Wired or wireless is just a medium, the "network" it carriers is mostly not relevant to the actual medium. If this is a wireless bridge, why is the second router providing DHCP and not just transparently passing the 192.168.1.0/24 network through? That would make this so much simpler, router one provides DHCP to everything, and router 2 just acts a bridge passing the wireless network to the wired ports. Sounds to me like this is misconfigured since this is a SOHO environment.

– acejavelin
Jan 31 '16 at 14:31





Wired or wireless is just a medium, the "network" it carriers is mostly not relevant to the actual medium. If this is a wireless bridge, why is the second router providing DHCP and not just transparently passing the 192.168.1.0/24 network through? That would make this so much simpler, router one provides DHCP to everything, and router 2 just acts a bridge passing the wireless network to the wired ports. Sounds to me like this is misconfigured since this is a SOHO environment.

– acejavelin
Jan 31 '16 at 14:31













I tried changing the subnet at one point and it still wasn't working. Would I have to do anything in terms of setting the Gateway on Subnet 2 for that to work?

– Mark Biek
Jan 31 '16 at 14:31







I tried changing the subnet at one point and it still wasn't working. Would I have to do anything in terms of setting the Gateway on Subnet 2 for that to work?

– Mark Biek
Jan 31 '16 at 14:31















I'll take a look and see about disabling the secondary DHCP and just making it all one big 192.168.1.0 network.

– Mark Biek
Jan 31 '16 at 14:32





I'll take a look and see about disabling the secondary DHCP and just making it all one big 192.168.1.0 network.

– Mark Biek
Jan 31 '16 at 14:32




2




2





Your router 2 is misconfigured, it should not be doing any router or DHCP functions, everything should be handled by router 1. Router 2 should be just a pass-though of the network. Everything should be one 192.168.1.0/24 subnet with a gateway of 192.168.1.1

– acejavelin
Jan 31 '16 at 14:33





Your router 2 is misconfigured, it should not be doing any router or DHCP functions, everything should be handled by router 1. Router 2 should be just a pass-though of the network. Everything should be one 192.168.1.0/24 subnet with a gateway of 192.168.1.1

– acejavelin
Jan 31 '16 at 14:33










1 Answer
1






active

oldest

votes


















1














Your setup is not a wireless bridge, just a way of using the wireless medium to carry a network connection to another router, the second "router" should be setup as a bridge to pass-thru all network traffic, making this all one subnet with one router handling all DHCP and routing functions for the entire LAN. This is called a Client-Bridge configuration and is a common DD-WRT application.



http://www.dd-wrt.com/wiki/index.php/Client_Bridged






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%2f1033793%2fallow-two-subnets-to-talk-to-each-other-over-a-wireless-bridge%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









    1














    Your setup is not a wireless bridge, just a way of using the wireless medium to carry a network connection to another router, the second "router" should be setup as a bridge to pass-thru all network traffic, making this all one subnet with one router handling all DHCP and routing functions for the entire LAN. This is called a Client-Bridge configuration and is a common DD-WRT application.



    http://www.dd-wrt.com/wiki/index.php/Client_Bridged






    share|improve this answer




























      1














      Your setup is not a wireless bridge, just a way of using the wireless medium to carry a network connection to another router, the second "router" should be setup as a bridge to pass-thru all network traffic, making this all one subnet with one router handling all DHCP and routing functions for the entire LAN. This is called a Client-Bridge configuration and is a common DD-WRT application.



      http://www.dd-wrt.com/wiki/index.php/Client_Bridged






      share|improve this answer


























        1












        1








        1







        Your setup is not a wireless bridge, just a way of using the wireless medium to carry a network connection to another router, the second "router" should be setup as a bridge to pass-thru all network traffic, making this all one subnet with one router handling all DHCP and routing functions for the entire LAN. This is called a Client-Bridge configuration and is a common DD-WRT application.



        http://www.dd-wrt.com/wiki/index.php/Client_Bridged






        share|improve this answer













        Your setup is not a wireless bridge, just a way of using the wireless medium to carry a network connection to another router, the second "router" should be setup as a bridge to pass-thru all network traffic, making this all one subnet with one router handling all DHCP and routing functions for the entire LAN. This is called a Client-Bridge configuration and is a common DD-WRT application.



        http://www.dd-wrt.com/wiki/index.php/Client_Bridged







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 31 '16 at 14:37









        acejavelinacejavelin

        5,10841531




        5,10841531






























            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%2f1033793%2fallow-two-subnets-to-talk-to-each-other-over-a-wireless-bridge%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...