I just started a new job and my first order is to create a new subnet. The company has been working on the 192.168.1.0/24 network for some time and have used up all but 4 IP addresses. I wanted to make a /23 network and put certain devices on the 192.168.0.0 network. I'm still feeling out all the equipment that was there when I started. One router, one switch, no Vlans (small business). I've played around with it a bit but I'm having a hard time having any device on the 0.0/23 subnet be able to communicate with the 0.1/24 network or access any network resources.
Basically only certain devices will be on the 0.0/23 network but need to be able to access resources on the 1.0/24 network. Only certain devices on the 1.0/24 network need to be able to access the devices on the 0.1/23 network (so far I've changed the subnet mask to 255.255.254.0 on certain user devices on the 1.0/24 network and am able to access devices on the 0.1/23 network, but not vice versa).
Your phrasing of the question suggests that you believe that 192.168.1.0/24 is a network separate and different from 192.168.0.0/23. Actually 192.168.1.0/24 is part of network 192.168.0.0/23. If you change the netmask on devices from /24 to /23 then they all should communicate without difficulty. Your post indicates that there are some problems in that communication. Can you verify that both devices that are having problems in communicating have /23 netmasks?
If the devices do have /23 netmasks and still do not communicate then you need to supply more information about how things are set up in this network.
If you have a subnet of 192.168.0.0 /23 then it contains 192.168.0.0 and 192.168.1.0 subnet too. You see, when you take that one bit from 24 mask thus making it 23 the subnet will double the size.
192.168.0.0 means there are 512 addresses(510 usable).
So there has to be range from 192.168.0.0 - 192.168.1.255.
Therefore these two networks are overlapping - or to put in in another way - the /24 network is just part of the /23. Change all masks to /23 and make default gateway the same and that should resolve the problem.
If you want them on separate subnets just make them both /24's , 192.168.0.0/24 and 192.168.1.0/24 . You would create subinterfaces on the router to trunk to the switch on which you would create new vlans and setup trunking back to the router. The switch has to be manageable and be able to create vlans and trunking. If its a unmanaged switch you are out of luck and it would have to be replaced with something more advanced. This gives you an idea.
Thank you all for the ideas/suggestions. I'm headed in the right direction and believe just needs some tweaking (and learning more about the current set up). I'll definitely add in some VLANs as devices on the /23 subnet should only be accessible to certain people. Thanks again.
On the router you have a statement that says ip address 192.168.1.254 255.255.254.0 on the internal interface? Make sure you changed it from the /24 subnet mask you had previously. Replace the ip address above with your ip address that your clients use for default gateway.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.