Networking : Connect 2 subnets ?

bertie40

Well-Known Member
Reaction score
426
Location
Leeds, UK
I thought long and hard about posting this, but here goes..........

Question : I want to access files on one subnet, from another.

Situation.
I have 2 routers, on separate subnets. (192.168.0.1 & 192.168.2.1)

The idea being to isolate my home network from any nasty found on a customers machine.

Now then......

On occasion, I'd like to access my repair machine or NAS (192.168.0.2 & 09) from my admin machine (192.168.2.2)

I've tied myself up in knots over this. There may be a simple solution.... or not.

I appreciate the whole idea of having subnets is to prevent the very action I am trying to perform.

The simplest solution is to ditch one subnet entirely, but would this be ok from a security point of view?

Regards.
 

Attachments

  • My Network.jpg
    My Network.jpg
    51.1 KB · Views: 76
This is something I am going to do soon. But don't know how so will be instrested in the answer.

The only thing I have thought about is under the network adapter, you can specify a second IP addess under Alternative config?

attachment.php
 

Attachments

  • ip.png
    ip.png
    13.3 KB · Views: 149
Would this not just be an allow rule on the 192.168.0.x router firewall to allow traffic from 192.168.2.2? Only enable this when you want to send traffic between subnets. You may also need to add a persistent route to your admin machine's routing table to tell it how to find the 192.168.0.x subnet.
 
I thought long and hard about posting this, but here goes..........

Question : I want to access files on one subnet, from another.

Situation.
I have 2 routers, on separate subnets. (192.168.0.1 & 192.168.2.1)

The idea being to isolate my home network from any nasty found on a customers machine.

Now then......

On occasion, I'd like to access my repair machine or NAS (192.168.0.2 & 09) from my admin machine (192.168.2.2)

I've tied myself up in knots over this. There may be a simple solution.... or not.

I appreciate the whole idea of having subnets is to prevent the very action I am trying to perform.

The simplest solution is to ditch one subnet entirely, but would this be ok from a security point of view?

Regards.

Most NAS's can permit remote access. So why not that and some form of RDP (MS, Teamviewer, etc.) into the repair machine?

Rick
 
Most NAS's can permit remote access. So why not that and some form of RDP (MS, Teamviewer, etc.) into the repair machine?



Rick


Yep. That's definitely an option, but I'm after something a bit more elegant than data transfer via the web. Regarding speed particularly.

I'm busting a gut replacing my old cat5 with cat6 atm, so I would like to retain this level of speed.
 
That's a new one on me.

I've been messing with 255.255.0.0

I'll give it a shot when I get home.
Cheers

That should work as well. But it leaves the network open to many more subnets. No an issue in your situation I'm sure but not a best practices thing.
 
We accomplished this by setting up a Freenas with two nics. One nic for private LAN and one for bench LAN. There are two shares, admin which is more for the private LAN side and is tied to our AD server. Bench LAN has no access to this folder. The bench LAN has a folder which is mostly read only for access to apps while working on machines. We do have a local Freenas account with a folder we can login to when we need to save something from a client PC to the Freenas.

Our Sonicwall ACLs prevent any traffic from bench LAN to private LAN. The shop folder on Freenas is accessible from private LAN to allow downloading apps and updates for the shop techs.
 
Back
Top