I can sympathise with you but can't offer any real suggestions. New simple
LAN routers have gone the way of hubs - ie to that great electronic
graveyard in the sky.
As suggested earlier you can use an old PC. You don't even need a server
OS and RRAS. You can use NT/XP workstation or Linux as a simple LAN router,
which is all you would need for this exercise.
If you are looking at this as a "proof of concept" exercise you could
always use a virtual machine and virtual networks and routers (using VPC or
Virtual Server). It could even be all you need in any case. Just plug the
host machine into your existing switch and either use the host as a router
to your vm or build a vm to route between the physical and virtual networks.
You don't even need the second switch. You use a virtual one. You don't need
any additional hardware but you would need an additional OS licence or two
for the vms. VPC and Virtual Server are both free.
Regardless of what hardware/software solution you use, the actual
routing is straight-forward. You put the new machines in their own subnet
(say 192.168.17.0/24). You set the 192.168.17 address of the router as the
default gateway for the new subnet. You will probably need to add some extra
routing to the existing subnet to get the traffic for your new subnet to
your LAN router if the existing subnet is set up to use some other router as
its default gateway.
That got a bit convoluted. Simple IP routing just works without adding
anything if the router is the default gateway for both subnets. If one
subnet uses another gateway you need extra routing to get the traffic for
the "other" private subnet to the LAN router instead of to the default
gateway.
"Chris White" <(E-Mail Removed)> wrote in message
news:AE2E000B-0441-406B-8AD6-(E-Mail Removed)...
> Well I spoke with Anthony over at the DFS & FRS groups about this but it
> looked like a Layer 2 / Layer 3 switch was going to be very expensive.
>
> Our current switches (Netgear GS725T's x 3) have been very very reliable
> and
> efficient to be honest. They do support VLAN's but you can't assign IP's
> and
> Subnets to them. Just group ports together to create better efficiency.
>
> The plan is something along the lines of this plan i knocked up: -
> http://i34.photobucket.com/albums/d1...-O-Deathv2.gif
>
> --
> Chris White
> United Kingdom
>
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Chris White <(E-Mail Removed)> wrote:
>> > Hey all,
>> >
>> > I need a router to go between two switches.
>> >
>> > One switch is on a different subnet to the other and they need to be
>> > linked like a remote site link, only all in the same rack.
>> > Essencially a fake remote site.
>> >
>> > Out of all the routers i've seen, they all seem to be WAN, ADSL or
>> > Routers with Switches in. Am I missing something? Can you not just
>> > buy a straightforward router and stick it between two
>> > different-subnet switches?
>> >
>> > I dont want to route anything to ADSL or WAN. Just want to connect two
>> > networks/switches together that are on seperate subs.
>> >
>> > What do I need? Small Business here so we dont have a meaty budget.
>> >
>> > Cheers.
>> > -------------
>> > Chris White
>> > United Kingdom
>>
>> In addition to the other reply, perhaps what you might better use is an
>> Ethernet switch capable of creating VLANs.
>>
>>
>>