From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Randolph Jones <jonesrf1@qwest.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: need for stateful packet inspection
Date: Thu, 27 May 2004 04:04:05 -0400 [thread overview]
Message-ID: <1085645044.10045.3.camel@localhost> (raw)
In-Reply-To: <40B126AA.3050106@qwest.net>
On Sun, 2004-05-23 at 18:33, Randolph Jones wrote:
> I am ignorant re iptables.
>
> I am considering buying a linksys router. It seems to have statefull
> packet inspection that blocks nonmatching incoming packets.
>
> If I do not have a server exposed to the internet, do I need any
> packet inspection other than checking that all incoming packets match an
> earlier outgoing request?
>
> TIA
> rfjones
In short, no. If your needs are minimal and you do not need to managed
multiple devices a linksys may be fine for you. I cannot speak to the
quality of Linksys; I have not used them. However, not all stateful
inspection engines are created equal. Consider what functionality you
may need in the future. Consider how important reliability is, i.e.,
if the device occasionally fails and needs to be reset, is that a
problem. However, for very simple needs, a Linksys will probably be
fine.
Does anyone else have any thoughts, comments or insults?
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-05-27 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 22:33 need for stateful packet inspection Randolph Jones
2004-05-27 8:04 ` John A. Sullivan III [this message]
2004-05-28 0:06 ` Chris Brenton
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=1085645044.10045.3.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=jonesrf1@qwest.net \
--cc=netfilter@lists.netfilter.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.