[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] What would you do
- Subject: Re: [cobalt-users] What would you do
- From: josh <josh@xxxxxxxxxx>
- Date: Sun Jul 23 14:29:37 2000
If you were also looking at software solutions, I would recomend setting
up a dedicated openbsd mechine to do pat/nat/ipf/routeing/whatever. It
gives you basicly all the features you would get from an ios device ( A
moi avis, it's easier). It's opensource, and you don't need a mechine with
that much resources. That old 486 kicking around under your bed would do
fine. And on top of that, you could use snort for an NIDS solution
(http://www.snort.org). Which is a rule based sniffer, that can detect all
kinds of evil traffic, and you can create your own custom rule set
usinging the cgi program on their page.
On Sun, 23 Jul 2000, Robert G. Fisher wrote:
> On Sun, Jul 23, 2000 at 11:52:46AM -0700, Jimmy Gross wrote:
> > We host on a RADSL line (1M X 1M). Our ISP is very supportive and has
>
> Umm, RADSL is typically 7Mb up by 1Mb down. If you have lower line
> quality you can see service degradations.
>
> > > Also are there any issues with using a RAQ on a ADSl line that any one has
> > > seen? Right now they are wanting me to use a Cisco ADLS modem with PAT.
> > > I am trying to get them to allow me to install a better router with NAT on
> > it.
>
> Using Cisco PAT/NAT isn't a bad idea. I know several companies that use
> it for mail servers...Including a fortune 500 company who is one of our
> frame relay customers.
>
> The real issue is the actual connection to you.
>
> Now on to Jeff's comments.
>
> > First reason: adsl is SLOWER upstream than down.
>
> This is important. Your upstream is what matters if you're hosting
> since the server 'uploads' what the user downloads to his PC..still,
> if you actually do have a 1Mb upstream, that can still be comparable
> to a T1's 1.5Mb upstream...
>
> > Second reason: adsl usually doesn't come with static IP
>
> This really depends on your provider.
>
> > Third reason: adsl usually comes with NO support foranything but
> > Windows.
>
> Jeff, I hate to say it -- but you haven't looked hard enough. The
> vast majority of DSL offerings are not PCI cards but are standalone
> devices or unit cards to act as an ethernet-dsl bridge or to function
> as a router. And if you look at they are trying to get him to use
> a cisco router with Pat...err, makes this mute.
>
> > Fourth reason: many companies supplying adsl won't even install if your
> > system is anything BUT Windows.
>
> This is an issue for anyone who doesn't understand their routers --
> and if he's looking for something 'better' than cisco...it makes me
> wonder as Cisco is pretty much the defacto standard for routing on
> everything higher than a dsl which they came into the market rather
> late while waiting on standards to settle.
>
> > Fifth reason: people supporting adsl usually have NO CLUE at all.
>
> True enough, although I can't say the people I talk to supporting my
> T1s tend to have a clue either...<grin>
>
> > Sixth reason: when adsl is down, it's absolutely LAST PRIORITY for
> > bringing back up.
>
> This is true -- ADSL connections tend to be low on a totem pole for
> a lot of service providers as it is not generally viewed as business
> hosting -- if you have that clear, that's one thing.
>
> Umm...Seventh Reason: Plenty of people on this list can offer you
> nice co-location costs? I know that both my company and Jeff offer
> co-location :).
>
> --
> Robert G. Fisher NEOCOM Microspecialists Inc.
> System Administrator/Programmer (540) 666-9533 x 116
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>