Re: IPSEC

From: -S (email_at_email.com)
Date: 10/18/03


Date: Fri, 17 Oct 2003 22:20:21 GMT

this is EXACTLY what i was looking for.... THANKS A MILLION!!
;o)

http://www.analogx.com/contents/articles/ipsec.htm

On Fri, 17 Oct 2003 20:30:49 GMT, -S <email@email.com> wrote:

>i really do appreciate your insight and the link you have provided. i
>am looking at this site now.
>thank you for taking the time to reply to this post.
>:o)
>
>
>
>
>On Fri, 17 Oct 2003 21:20:31 +0100, "ClareOldie"
><ClareOldie@nowhere.ie> wrote:
>
>>
>>"ClareOldie" <ClareOldie@nowhere.ie> wrote in message
>>news:95Yjb.1539$bD.5476@news.indigo.ie...
>>> Forgot this
>>> http://www.analogx.com/contents/articles/ipsec.htm
>>>
>>>
>>> Seán
>>>
>>>
>>Seems I was wrong earlier - sorry
>>
>>Quote:
>>How IPSec rules works
>>
>> Rules in IPSec are handled in very simple approach, the closest match to
>>the incoming packet determines how it is handled overriding everything above
>>it. So if you have two rules, one that denies all TCP traffic and another
>>that permits HTTP traffic (port 80 TCP), then your server is effectively
>>blocking everything that doesn't connect on port 80. Running a FTP server on
>>the same machine? Not anymore... If you want it accessible, then you need to
>>add another rule permitting FTP traffic (port 20/21 TCP).
>>
>>Seán
>>



Relevant Pages

  • Re: IPSEC
    ... i really do appreciate your insight and the link you have provided. ... >How IPSec rules works ... >the incoming packet determines how it is handled overriding everything above ...
    (comp.security.firewalls)
  • Re: How to close on IIS any port except 443?
    ... That still leaves port ... firewall/router (either software on the box -or- hardware device. ... IPSec rules: ... > thanks for advice, but it is not clear how to bind site to port 443 only, ...
    (microsoft.public.inetserver.iis)

Quantcast