What's new

Joining two networks togeather..help!

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

kipper

New Around Here
I have two subnets... 10.0.1.x and 10.0.2.x

Machine on network A is 10.0.1.100, Machine on network B is 10.0.2.100 both have a subnet of 255.255.0.0. These two machines need to talk.

Also connected to network A are clients ranging from 10.0.1.1>10.0.1.10 these will have a subnet of 255.255.255.0 and need to talk to 10.0.1.100

The same in on network B, client ranging from 10.0.2.1>10.0.2.10 (255.255.255.0) and need to talk to 10.0.2.100.

The two sets of machines on 255.255.255.0's dont need to talk to each other.

Will this work or will I have to have a bridge/router between 10.0.1.100 and 10.0.2.100 and limit there subnets to 255.255.255.0 for broadcast reasons?

Heeeeeelllllp :confused:
________
Honda CD125
 
Last edited:
It's a little hard to answer your question, because your subnetting is a little confusing. And a lot of this depends on your physical setup.

I have two subnets... 10.0.1.x and 10.0.2.x

Machine on network A is 10.0.1.100, Machine on network B is 10.0.2.100 both have a subnet of 255.255.0.0. These two machines need to talk.

By using that mask (255.255.0.0), those two 'networks' are already members of the same subnet. I don't know how well you know your subnetting, but based on the mask 255.255.0.0, basically any address beginning in 10.0 is in the same address range (subnet). Is it because these two machines are on different physical networks and you need to join the two?

Also connected to network A are clients ranging from 10.0.1.1>10.0.1.10 these will have a subnet of 255.255.255.0 and need to talk to 10.0.1.100

These addresses are all in the same subnet based on that masking, so they should be able to talk to each other already.

The same in on network B, client ranging from 10.0.2.1>10.0.2.10 (255.255.255.0) and need to talk to 10.0.2.100.

Same as above, these addresses are all in the same subnet based on that mask, so you're fine here.

The two sets of machines on 255.255.255.0's dont need to talk to each other.

What does your physical setup look like? Is everything on the same router? Are there multiple routers or networks involved? Subnetting and routing can be a bit difficult for people to understand, but as it stands, all of your IP addresses should be in a position to talk to each other, depending on the physical setup. Actual 'routing' becomes necessary when you need to forward packets between two networks, which doesn't seem necessary right now. But a lot of this depends on your physical setup.
 
Last edited:
Thanks for your excelent reply Scotty...

Topology wise, Its going to be a flat network.

Two switches, One to attach 10.0.1.x and one to attach 10.0.2.x there will be a single connection joining the two switches. There are currently no gateways (such as an internet connection)

Im hoping to setup some virtual machines today and test this and then progress to a physical test before implimentation.
________
Yamaha XV920R
 
Last edited:
Well then, based on your physical setup, everything should work as mentioned and all the machines that need to talk to each other should be able to.

Without any routers involved, devices connected together with a switch can talk to each other, as long as they are in the same subnet / broadcast domain. Thus, subnet masking plays a critical component of defining who can 'see' what. Devices with a mask of 255.255.255.0 (aka. /24) can talk to any device who's IP address is the same in the first 3 octets. Devices with a mask of 255.255.0.0 (aka. /16) can talk to any other device who's address is the same in the first 2 octets - just keep in mind that these /16 devices will be able to see the whole network, because all of your devices fall within the 10.0.0.0/16 subnet.

Your current setup will work as you envision based on your masking. Just keep in mind the caveats I mentioned, depending on the security/privacy needs.

Routers only become necessary when packets need to move from subnet to subnet (i.e. different subnets or the internet). If you want to learn more about subnetting, Google 'subnetting' and you'll see there's lots to learn! It's all very interesting though.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top