Subnet Mask Setting

Associate
Joined
20 May 2004
Posts
138
Hi. I have a local network with ips in the range 192.168.7.x which is working fine.
I want to add IPs with range 10.1.1.x to the network.

What should my subnet mask be set to please?

Thanks
 
255.0.0.0 (/8) if I'm correct although I think I remember seeing that 255.255.255.0 (/24) will sometimes work
 
I think you need to be more clear about what you're trying to do, unless you're planning to have separate subnets and route between them you would want to keep everything on the same network in the same ip range. Bare in mind that if you want to keep things away from each other this having separate ranges won't work since they'll still see the same broadcast traffic. You'll also have difficulties getting both ranges to see the internet.
 
Solution is not as you depict; you need routing between two descrete subnets which can only realistically be completed if we know what kit you have to hand. May be easier to just readdress one subnet, to align to the other.
 
10.1.1.x would be a /24 or 255.255.255.0, but as overs have said you can't just add that subnet to an existing 192.168.7.0/24 subnet and expect anything to work properly.

Explain what you want to actually achieve and I am sure someone will be able to offer useful advise.
 
If you can set a subnet mask of 0.0.0.0 then that is the only one that will work in this situation - but then you have no way of setting a default gateway for internet-bound traffic.

Use a router.
 
Hi. I have a local network with ips in the range 192.168.7.x which is working fine.
I want to add IPs with range 10.1.1.x to the network.

What should my subnet mask be set to please?

Thanks

If you want them to talk to each other without routing, then that won't work.

If you want both subnets as separate subnets, then /24 or 255.255.255.0 for both will be OK.

If you want the networks to talk to each other without routing... your best option would be to expand the current subnet.

Your current /24 255.255.255.0 has 254 usable IPs.

/23 255.255.254.0 would give you 510
/22 255.255.252.0 would give you 1022

Unless there's a limitation to the broadcast in a more open range that I'm forgetting about... changing your current subnet to:

192.168.7.0/23 would allow you to use 192.168.7.1-192.168.8.254
192.168.7.0/22 would allow you to use 192.168.7.1-192.168.10.254


Otherwise just activate inter-lan routing on your router, or setup the routes manually.
 
Hi, thanks for the replies.

We have a draytek 2830n. We already have 3 VLANs set up for different departments, each VLAN is connected to the router through separate NIC ports and we have a network switch from there for our machines.

I am using the 192.168.7.x range.

We've just purchased an Antsle virtual cloud server which spins up VMs each with an IP within the 10.1.1.x range. I could always change the IPs of the VMs once they are running but thought it would be easier to use the 10.1.1.x that they are assigned.

Again, thanks for all this help
 
http://docs.antsle.com/bridgevnic/

So lookng at their support site, you would just add a static route on your router so the 10.1.1.0/24 is routed via the interface of br0 (the interface of the antsle box), presumably it's management IP which resides in your local 192.168.7.0/24 subnet.

So you'd be routing 10.1.1.0 255.255.255.0 via 192.168.7.X where 7.x is the BR0 interface of the antsle box. Looks like your router can add routes easily.

https://www.draytek.co.uk/archive/kb_vigor_staticroute.html
 
Last edited:
As the OP already has port based VLANs running on the DrayTek it'll be a very quick job to add another that uses the 10.1.1.x range he wants.

Inter-LAN routing will only require the ticking a few check boxes.
 
As the OP already has port based VLANs running on the DrayTek it'll be a very quick job to add another that uses the 10.1.1.x range he wants.

Inter-LAN routing will only require the ticking a few check boxes.

Should be that easy, yes... it's there on the 2960 & 3900... I'm not sure about the 2830 the OP mentions... but I'd guess it's there.

If it's not... adding a static route should be easy enough.

Even if it is though, given his use-case... I'd be more interested in changing the IPs of the new server(s) to add them to the existing range or simply updating the subnet to give it a wider range.
 
Pretty sure there will be a setting in that box to change the IP range that things are deployed on.

Yeah, I'd guess that too... there should be some ability to change the default deployment IP, rather than changing each manually... otherwise... surely it will only be a handful of new servers that need their IP manually adjusting... so the time investment will be low.
 
As the OP already has port based VLANs running on the DrayTek it'll be a very quick job to add another that uses the 10.1.1.x range he wants.

Inter-LAN routing will only require the ticking a few check boxes.

Reading the docs it suggests to me that the solution is design with bridging; its for developers to fire up VMs and containers quickly - direct lan connection id suggest could break some of the functionality. It's not a production grade hypervisor / private cloud solution its a plug in, configure for 5 minutes and create short lived instances in a semi sandbox like area.
 
Last edited:
Back
Top Bottom