Re: IPSEC Filter
From: Robin Twiggs (rstwiggs@lantic.net)
Date: 01/02/03
- Next message: Bryan: "Re: unable to logon"
- Previous message: Eddy: "Re: event logs"
- In reply to: Karl Levinson [x y] mvp: "Re: IPSEC Filter"
- Next in thread: jussi jaakonaho: "Re: IPSEC Filter"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Robin Twiggs" <rstwiggs@lantic.net> Date: Thu, 2 Jan 2003 18:00:31 +0200
Thanks for clarifying - I will script all the filter options.
Robin
"Karl Levinson [x y] mvp" <levinson_k@excite.com> wrote in message
news:us5a5ORsCHA.1656@TK2MSFTNGP09...
>
> "Toni Lassila" <mpao@mc-europe.com> wrote in message
> news:b11796dd.0212302318.2a4b51ae@posting.google.com...
>
> > IP address space from 192 up was originally reserved for Class C type
> > networks, i.e. /24. That means you can only have a netmask of
> > 255.255.255.0 and need to have 71 different entries for each Class C
> > network you want to cover in this case.
> >
> > Apparently someone at MS hasn't heard of CIDR, so you're SOL. This looks
> > like it should be fixed in a SP.
> >
> > > Am I missing something here?
> >
> > No, but Windows definitely is.
>
> I agree.
>
>
>
- Next message: Bryan: "Re: unable to logon"
- Previous message: Eddy: "Re: event logs"
- In reply to: Karl Levinson [x y] mvp: "Re: IPSEC Filter"
- Next in thread: jussi jaakonaho: "Re: IPSEC Filter"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|