NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Rachakondaashok's avatar
Dec 29, 2017

Communication between two switches with different subnets (M4100) M4100

Hi Team,

 

I am using 2 M4100 switches in our 2 offices which are located side by side and i am using 2 firewall. Here i enable DHCP in the firewalls and i am getting ip automatically from the firewall to the switches. I am using the different subnets in the different building. Now i am planning to connect a cable between 2 buildings and i want estabilish the communication between 2 buildings with different subnets. Need your help and please find the attached diagram setup.

2 Replies

  • StephenB's avatar
    StephenB
    Guru - Experienced User

    This is in the ReadyNAS area - I will move thiis for you to the right subforum for managed switches.

  • Hi Rachakondaashok

     

    The two subnets you describe (192.168.1.0 /24 and 192.168.0.0 /23) are in the same subnet range.

     

    You want to connect two network segments, but how do you avoid duplicate IPs in this case? Building A PC device could get and IP of 192.168.1.24, but so could a device in building B. That is a problem!

     

    Additionally, are you using VLANs or is everything in default VLAN1? If you are using just one VLAN, then you need to be careful because if you connect the switches together you will now have two DHCP servers for the same VLAN. That is never a good thing! But that could be solved with some quick DHCP snooping setup, however that still does not address the actual issue of duplicate IPs being a very likely problem.

     

    Due to the fact that you need two DHCP servers, because you need two different Gateways for clients, then you need to separate those networks. What you could do is:
    1. Create separate VLAN for people in building A, say VLAN10

    2. Create separate VLAN for people in building B, say VLAN20

    3. Use actual different subnets for those VLANs, say 192.168.0.0 /23 and 192.168.2.0 /23.

    4. Create a second routing VLAN and use that between the switches, say VLAN99.

    5. Setup some static routes on each router, to guide clients when they want to communicate with the other building.

     

    This way you can create a routing path between devices in building A and building B, while still maintaining two different networks.

     

     

    Cheers

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More