Re: IPSEC
From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 01/28/05
- Next message: Kerodo: "Re: IPSEC"
- Previous message: Steven L Umbach: "Re: Event Logs"
- In reply to: Kerodo: "IPSEC"
- Next in thread: Kerodo: "Re: IPSEC"
- Reply: Kerodo: "Re: IPSEC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 27 Jan 2005 19:20:57 -0600
There is no way to do general logging with ipsec in Windows 2000. W2003 does
offer some logging such as for dropped packets. You would need to use a
software firewall such as Sygate to have some logging. Sygate is free for
personal user, is a stateful firewall [unlike ipsec] , and has extensive
logging capabilities. Ipsec is not meant to be a first line internet
firewall. One weakness of a packet filtering firewall is that due to the
rules it is possible for a user to scan your internal network by
manipulating the source port of the scan. For instance you may be allowing
all traffic from port 80 to your computer from the internet. I could use a
program such as Supercan 4 to scan your network by using port 80 as the
source port for my scan. A stateful firewall would not allow that. I think
ipsec is great for what it is good at, particularly on the lan, but I would
not use it as a permanent primary internet firewall. --- Steve
"Kerodo" <loopback@localhost.com> wrote in message
news:MPG.1c6316fa67ddee29989681@news.west.cox.net...
> I'm using IPSEC as a basic packet filter here on my Win2k machine. Is
> there any way to do any kind of logging with IPSEC so I can see what
> packets are being blocked?
>
> --
> Kerodo
- Next message: Kerodo: "Re: IPSEC"
- Previous message: Steven L Umbach: "Re: Event Logs"
- In reply to: Kerodo: "IPSEC"
- Next in thread: Kerodo: "Re: IPSEC"
- Reply: Kerodo: "Re: IPSEC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|