Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".


Subnet possible overlap for S2S VPN setup

Current config:


Gateway is

Want to expand DHCP scope because we are out of IPs, but need to go up in the 3rd octet and not down.

Because the 3rd octet is odd for the subnet, going to a,,, the new scope goes backwards.

So if I change the scope to 255.255.254, then the available subnets become –

If I change it to, then available subnets become –

If I change it to, then available subnets become –


If I change the subnet to, then the available subnets become –

That takes care of going up on the available subnet. I can then set DHCP to be only in the range of to, keeping the gateway on

Question is, we have other locations that are set to subnets of 10.15.22.x, 10.15.21.x, etc. that are setup with S2S VPN to our HQ, but not to each other because we are on a hub/spoke design. If we are not giving out IPs in those ranges for this expanded IP site, but the new subnet is still within those ranges for the other sites, will it cause a conflict with the other S2S VPNs and possibly devices in those subnets? I don’t think so because we are not giving out those IP ranges but I just need confirmation that this will be Ok.

Category: Entry Level Firewalls


  • Options
    BWCBWC Cybersecurity Overlord ✭✭✭

    @radiman subnet will collide with your other locations, because it'll make an ARP request when it's in your subnet boundaries. It will not even try to route it over your VPN, except all endpoints getting an explicit route, but that's not really good.

    Best option would be a renumbering of to something more future proof, like, etc.


Sign In or Register to comment.