From: chuck gelm <chuck@gelm.net>
To: eatley@wowcorp.com
Cc: linux-admin@vger.kernel.org
Subject: Re: Red Hat Enterprise Linux WS or ES for server?
Date: Wed, 22 Dec 2004 20:19:56 -0500 [thread overview]
Message-ID: <41CA1D3C.5030702@gelm.net> (raw)
In-Reply-To: <000001c4e867$ce7b9e60$1f0aa8c0@lanadmin>
Eve Atley wrote:
> We are a small company (less then 20 people) that is currently running
> Redhat Linux 9 as a fileserver. We have a firewall router set up currently
> that is wreaking havoc, and we had previously had used the Linux box as a
> firewall and router hooked up to our shared T1 line. We're looking to return
> to that system again. With cost as a factor, can we get away with Redhat
> Linux WS for this purpose?
>
> Additionally, we had abandoned the Linux system as a firewall/router for 2
> reasons: to be less machine dependent, and because our ethernet cards kept
> insisting on switching upon reboots (thereby causing all sorts of problems).
> If we upgrade to ANY version of Redhat Enterprise, would this solve our
> issues at all, or are we totally barking up the wrong tree? The system
> should probably be upgraded anyway as the GUI is as slow as molasses.
>
>
> Thanks so much,
> Eve
Hi, Eve:
I see that there are several reponses already, but I thought I'd add my
2 cents... It seems to me that there was some unclear statements and
some assumptions or myths expressed. You didn't explain
'wreaking havoc', but then again, you didn't request help with that
topic.
Probably, any 'enterprise' distribution would suffice, so yes,
Redhat Linux WS would probably suffice.
I would like to understand more about:
"ethernet cards kept insisting on switching upon reboots",
before responding about whether:
"ANY version of Redhat Enterprise would...solve our issues".
Please explain, more fully, your 'issues'.
I do not understand your reference to 'the GUI' on a file server
(or router) unless it is also being used as a workstation. One
might use a GUI application to configure a
'firewall/router/file-server', but a GUI is not needed for those
services to run.
I am using an 80486dx33 system as a firewall/router with my home
cable-modem network. I get just under 3 Megabit downloads, so anthing
equal or better should be enough for your shared 1 Megabit T1 service.
You didn't mention any hardware issues, so this information may not be
relevant to your situation.
I am using Slackware v9.1, default kernel 2.4.22,
default IPTABLES v1.2.8, and an IPTABLES script slightly modified
from one I found posted on the internet.
http://newbiedoc.sourceforge.net/networking/homegateway.html#IPMASQSETTINGSETH
See the part 9.2.2 For iptables Users. Your particular situation would
probably be satisfied by the appropriate configuration of IPTABLES.
In short, I think your solution is applications, tools, and
configuration
dependant
and not distribution dependant.
HTH, Chuck
prev parent reply other threads:[~2004-12-23 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 20:50 Red Hat Enterprise Linux WS or ES for server? Eve Atley
2004-12-22 20:48 ` Hal Wigoda
2004-12-22 21:07 ` Jens Knoell
2004-12-22 21:24 ` Scott Taylor
2004-12-23 1:19 ` chuck gelm [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41CA1D3C.5030702@gelm.net \
--to=chuck@gelm.net \
--cc=eatley@wowcorp.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.