RE: [cobalt-users] Why do cobalts have two ethernets anyhow?

["Paulick, Jim" <jpaulick@xxxxxxx>]

some businesses like to have a "production" side and a "backup side", and connect the "backup" side, to the isolated "backup network".  It's quite common in large environments, when it doesn't make sense to use your production network to transfer gigs and gigs of backup data.

Others like to have a nice for "production", and one for "management"  so that maybe only the production network is only accessible via http, but the "management nic" is accessible via telnet, and other protocols..





-----Original Message-----
From: Josh Kuperman [mailto:josh@xxxxxxxxxxxxxxxxxx]
Sent: Friday, June 06, 2003 4:26 PM
To: cobalt users
Subject: [cobalt-users] Why do cobalts have two ethernets anyhow?


I am curious why (some, eg.xtr, 550) cobalts have two ethernet
interfaces. You can alias many ips to a single interface, which is how
virtually hosted sites do it.

I ask for two reasons. They seem designed to provide ISPs with
hardware on which to host many sites to be remotely managed. So
security would not seem to be the issue. [It's not like a linksys
cable router where you can only manage it from your own lan by
default.] They don't seem designed to serve lans in any respect. Most
of the features if you were using them to run a school or business
workgroup, etc. aren't there -- (printing, X, etc.); though some like
samba are.

In any case what to do interfaces gain you? Anything with security or
ipchains/iptables configurability. Anything with greater throughput?
It just seems like they are almost designed to have one interface that
is hardly used or they stopped developing before they added enough
software for it to all make sense.


-- 
Josh Kuperman                       
josh@xxxxxxxxxxxxxxxxxx

_____________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users