You know, super super cheap solution is a WRT54GS running DD-WRT/Tomato/Open-WRT with each interface setup as a separate network. Extra cheap is that this is a low power system with no fan or moving parts.<br><br>I'm all about low power these days... Another low power but more than the above solution: take an Aspire Revo install some sort of firewall distro on (or adapt any other one as below) and put a bunch of USB ethernet ports on it and there you go. Not pretty but it would do the job :)<br>
<br>In any case if you need help I may have some time soon, contact me off list and maybe I could help implement whatever solution you decide to go with.<br><br>--j<br><br><div class="gmail_quote">On Sun, Jun 28, 2009 at 10:44 PM, Bob De Mars <span dir="ltr"><<a href="mailto:bob@grunners.com">bob@grunners.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">>> If one has a managed switch, they generally support 802.1q VLANs.<br>
<br>
</div>I agree with this setup using a managed switch. Don't get me wrong, I like IPcop, and have been running its evil older brother Smoothwall @ my house on a Pent pro 200 since almost the first beta release back in the day. The long term problem with this setup is the box factor. Old (and new) power supplies fail, fans will die, raid 1 is better but an old (or new) hdd might fail, etc.... I guess my point is the linux router is a bit more fragile than a switch (hardware wise in the long run). Sure switches can die, but they are (forgive the M$ speak) slightly more Robust usually. IMHO keep the Linux router at home, or setup somewhere where you will be often. When things break, and your not around this sucks for you (& them). It easier to get the call that the network/internet is down & all you have to tell someone to shutoff the switch or yank the powercord - count to 10, and plug it back it.<br>
<br>
I recently dehodgepodged two of our offices networks, and have a few managed switches I could probably sell to you cheap if you decide to go this route. I am pretty sure they are all 10/100 speed though. I believe I have a couple 3-Com's, and a couple HP's all 24 port. They are located in Oakdale, but I could bring them home to NE Mpls if you want to take a road trip. I guess if your interested, just contact me off list.<br>
<br>
Good Luck Brother.<br>
<br>
B-o-B<br>
<br>
<br>
GlobeRunners, Inc.<br>
IT Manager<br>
600 Inwood Ave. N., Suite 160 | Oakdale, MN 55128 | Direct (651) 925-1500 | Cell: (612) 850-6940 | Fax: (651) 925-1560 | Email: <a href="mailto:bob@grunners.com">bob@grunners.com</a><br>
<div><div></div><div class="h5"><br>
-----Original Message-----<br>
From: <a href="mailto:tclug-list-bounces@mn-linux.org">tclug-list-bounces@mn-linux.org</a> [mailto:<a href="mailto:tclug-list-bounces@mn-linux.org">tclug-list-bounces@mn-linux.org</a>] On Behalf Of Jima<br>
Sent: Sunday, June 28, 2009 6:50 PM<br>
To: tclug-list<br>
Subject: Re: [tclug-list] OT network solution<br>
<br>
Tony Yarusso wrote:<br>
> On Sun, Jun 28, 2009 at 4:29 PM, swede<<a href="mailto:danyberg@gmail.com">danyberg@gmail.com</a>> wrote:<br>
>> This was short notice and is my first attempt at setting up anything other a<br>
>> home network, so any other ideas for the layout would be appreciated.<br>
><br>
> If security is your concern, you want to take the switch out of the<br>
> equation (unless it's a smart/managed switch) and add more interfaces<br>
> to the IPCop router (one for each of the 4 places that need to be kept<br>
> separated).<br>
<br>
If one has a managed switch, they generally support 802.1q VLANs.<br>
Rather than having a NIC for each network, you can just assign each port<br>
on the switch to a separate VLAN, and trunk all of the VLANs to the<br>
Linux box. For that matter, you can connect the uplink to a VLAN of its<br>
own on the switch, too.<br>
I have such a setup running six disparate networks to a Linux router<br>
with only one ethernet interface, which can therefore be replaced by any<br>
hardware if needed (and not just a device with sufficient PCI* slots).<br>
Also, adding additional networks is a breeze as long as you have enough<br>
switch ports (and you could always trunk to another switch).<br>
<br>
It's a tad bit involved, but I'm pretty fond of the setup, myself.<br>
<br>
Jima<br>
<br>
_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
<br>
<br>
_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
</div></div></blockquote></div><br>