• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 420
  • Last Modified:

1 IP, 1 Router(Linksys 4-port): How to split network into two subnets that cannot see each other.

I've been in a quandry to complete this networking task, but have gotten confused on how to create a subnet on an existing network. Resources available include a single IP 4-port router servng off of a T1 modem.  Beind the router, one port goes off to one department, while another router port goes off to another department; each has their own hub systems serving their machines.

We are currently using local IP (device IP) and (subnet mask).  Neither department is supposed to see or access each other.  Unfortunately, both are currently being blinded from each other only by means of protocol settings, but, periodically the protocols are reset and each department can see each other until the protocols are reset.  I need to stop this.  First, the protocol method does not create any real security (obviously), and secondly, because these settings prevent either side from using the networks workgroup and sharing features adequitely.  

First method: I have thought of using a hub to split the T1 feed then run two routers off the hub, each with their own global IP (I'd get a second IP from our ISP), then each department could keep their current local IP configuration without my needing to change anything.  

Second method: I have also thought of trying to set up a subnet, but I can't quite figure out how to resolve the breakdown of how to reconfigure the subnet masks or how to confirm what local IP sets would be available.  The existing router already has a menu for choosing 2, 4, and 6 subnet masks, but then I don't know what IPs would be available.  I am also concerned that a subnet would not create the separation of the departments that I need.

Well, that's my quandry. I am looking for input as to the doability of my first method, or some direction for accomplishing the second method. No splitsies on this one.  Best response get all the points.

Also, please, I am not a technician, so try not to use too much techspeak.  You may give a great answer, but if I cannot decipher your remarks then it does me no good.

Thank you.
  • 3
  • 2
  • 2
  • +4
2 Solutions
Does your router have VLAN ability?  This give the router to act as two seperate lans and not allow data to be passed between the two.

Unless I am having a brain-fart this will be hard to do unless you purchase a second router and do something like the following

T1 with  WAN public address and LAN private address (

Department #1
Router #1 WAN address, mask, gateway
                  LAN address, mask
Router #1 LAN devices connect via hub. 192.168.10.x subnet with gateway

Department #2
Router #2 WAN address, mask, gateway
                  LAN address, mask
Router #2 LAN devices connect via hub. 192.168.20.x subnet with gateway
As plain English as I can get:
you cannot do it with the hardware that you have.

Your first method is your most viable alternative.

Another alternative is to swap the Linksys for a Cisco router, and add a switch to the inside. Create VLAN's on the switch, sub-interfaces on the router, and apply access-lists to the sub-interfaces

Another alternative would be to use a multi-interface firewall where traffic flows from internal interfaces out, but not to each other.

Isn't is possible if you setup your router as - subnet ... NO DHCP.

LAN1 - Hard code all machines to IPs in 192.168.10.x - subnet - Gateway

LAN1 - Hard code all machines to IPs in 192.168.20.x - subnet - Gateway

All machine should be able to talk to and transfer internet traffic, but should only be able to talk to .10.x or .20.x but not eachother.. (make sense?)

You may have to setup static routes in the linksys to get the traffic to pass from 1.1 to 10.x or 20.x
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Your option will not work. Your default gateway must be on the same subnet as your interface. The router may see the PC as being on the same local network, but the PC won't know how to get to the gateway.

>LAN1 - Hard code all machines to IPs in 192.168.10.x - subnet - Gateway
                                                                         ^^                           ^^^                             ^^
Ummm.. tested... and it works.
Well, I'm certainly never too old to learn a new trick....

It does not appear to work if doing it at the command prompt (on XP) as demonstrated here:
Windows IP Configuration
Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . : xxx.com
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :

C:\WINDOWS>route add mask
The route addition failed: Either the interface index is wrong or the gateway does not lie
 on the same network as the interface. Check the IP Address Table for the machine.

However, using the GUI for TCP/IP properties, I can set the gateway to anything outside my local network...
> Ummm.. tested... and it works.

Then not adequately tested.  Although you've given the subnets different subranges, they're not really on different networks.  A sniffer will reveal some of the other subnet's traffic (especially broadcasts, but possibly other stuff as well), and the fact that users can reach the same gateway address means they can actually reach each other's machines as well.

(A hub will not work with a T1.  Don't even go there.)

> you cannot do it with the hardware that you have.

I concur.  The four ports on the router are switch ports on a single VLAN/subnet, and do not offer the kind of separation needed.

lmoore should have been right:
If you mix different subnet types like and it shouldn't work. In fact it works sometimes - but it is unpredictable!
As an ISP you could use this as a feature called supernetting and you use it as a routing option - but you never tell different machines on the same LAN to be in mix-type networks.
Even if it may work it isn't right... that means not reliable.

Second thought - you want to break possible connections... so you should't use an unreliable TCP/IP-protocol (an possibly MicroSoft specific) failure (MS called feature) that you have no control of!

You can try a solution I offered at another ee-question:
LAN1 ---Router1
             LAN3 --- Router3 --- Internet
LAN2 ---Router2

Create an intermediate LAN (LAN3) and NAT both of your LANs to it... route that LAN3 to the internet... is that too simple?

i.e. use for LAN1 ("/24" means "subnet is")
use for LAN2
use for LAN3
You can use two NATing cheap routers to separate each other and using a third cheap router to lead the packets to the internet.
If you use such a router for every departement you're ready

Hope that helps
I simple switch that supports VLAN (from either Cisco or 3com) between the 2 networks and the router would easily solve your problem.

Assign each network a different VLAN and tada!  They can't see or hear each other =) No special configurations on each desktop no special router configs....saves LOADS of headache later on when something doesn't work
aindelicato, sometimes microsoft will allow you to route across subnets incorrectly however according to ip subnet standards you should not be able to communicate with a gateway that is not on the same subnet as the device. ie gateway

holger12345, isn't that the same thing I suggested?

primeradminAuthor Commented:
I am currently investigating/testing some of the responses posted above.  I'll be back to respond soon.
I think primeradmin wanted to give us the result of his testings... else all should work fine, no?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 2
  • 2
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now