{Side note: it's so nice to be able to type 'L' to reply to the list in
mutt again. (^chewie hugs his procmail filters.)}
In referencing the release notes for the Cisco 1605R, it looks like they
do provide a Firewall image for the router. This is not the simplest or
cheapest route for the library to take, but I would be comfortable in
saying that it'd probably be the most secure (if we exclude the SNMP
bugs that "ALL" Cisco equipment is succeptable to) and most supported.
Cisco has some nice Windoze management software for the router, and if
all else fails, can be accessed from the serial port for the IOS command
line. An added bonus may be that the ISP the library is currently
getting service from could manage the router as well. The library
wouldn't have to worry about configuring things or screwing things up,
and can rely upon the ISP's expertise in this field. That alone would
offset the cost of having someone develop an in-house expertise for such
things. Libraries, I can assume, don't really have the buget or
personel to spare.
I would only suggest such an organization take on Linux if they have
either in-house expertise with time to manage it, or if they can find
someone to provide service for them in either a per-incident/hourly
basis or some sort of contract basis.
The cheapest solution isn't always the best solution. I learned that
the hard way.
--
^chewie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://shadowknight.real-time.com/pipermail/tclug-list/attachments/20020227/77bc8e9a/attachment.pgp