Recommended Posts

Hi,

we use an IP-range 10.130.60.X with a 255.255.255.0 subnetmask

(so 254 addresses)

I would like to add another subnet by changing the subnetmask.

of course I could use 255.255.0.0 but this isn't good for broadcast I think.

Something ideal would be:

10.130.60.X

10.130.61.X

What subnetmask do I need ?

585188578[/snapback]

What you really need is a router (a real one not a broadband router) between the two networks and leave it subnetted the way it is.

I wouldn't recommend it, but you could use the subnet mask of 255.255.240.0

this would put 10.130.60.0 and 10.130.61.0 in the same subnet.

the networks would be subnetting like so:

10.130.0.0 - 10.130.8.0

10.130.9.0 - 10.130.16.0

10.130.17.0 - 10.130.24.0

10.130.25.0 - 10.130.32.0

10.130.33.0 - 10.130.40.0

10.130.41.0 - 10.130.48.0

10.130.49.0 - 10.130.56.0

10.130.57.0 - 10.130.64.0 <- your new subnet

10.130.65 - 10.130.72.0

10.130.73 - 10.130.80.0

etc...

you lose the first and last address for network and broadcast addresses.

This will give you a total of 2046 nodes on your logical network. Like I said, i dont recommend it.

Link to comment
https://www.neowin.net/forum/topic/263716-subnet/#findComment-585188670
Share on other sites

^ I am quite sure I know what I'm doing when it comes to networking. But from the question asked, it would seem the poster is lacking even the basics. So how is asking the man for more detail of what his trying to do not professional?

Does he just need more hosts on his current wire, ie change the mask. Or should he route between segments? How many more hosts are we talking? Too many hosts on one wire may degrade his performance, would depend on his hardware setup and type of traffic, etc.. Shoot depending on his system, why is he not using the classful mask of 8 bit for his 10.x address scheme? Is he talking to other private networks?

Depending on what he is attempting to do - changing the mask could quite easy BREAK some connectivity. I would guess he has other connections - or did he just pull the 10.130.60 address scheme out of his ass? If he changes the mask, with not understanding the address space around him, possible changes to routing, etc.. He could quite easy overlap an existing network - and not only have issues with is local machines, but the network he steps on may have issues - or people connecting to them, etc..

Nothing against experts-exchange, but I am quite sure there are more than a few people here that can help him.

Link to comment
https://www.neowin.net/forum/topic/263716-subnet/#findComment-585204146
Share on other sites

How can you use Router without those address on the router nodes!

I guess i am talkin about High End Routers!

585195576[/snapback]

Yes, and I was talking about home routers, which technically aren't routers. On a Cisco router, assigning the first address of any subnet to an interface is custom :p

Link to comment
https://www.neowin.net/forum/topic/263716-subnet/#findComment-585229590
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!