IPSEC BUG - Cannot filter - Subnet Mask invalid
From: Steven E. Adams (stevea1@home2offic.com)
Date: 12/06/02
- Next message: al: "Re: Null Sessions - Restrict Anonymous"
- Previous message: Oli Restorick: "Re: network client question"
- Next in thread: x y: "Re: IPSEC BUG - Cannot filter - Subnet Mask invalid"
- Reply: x y: "Re: IPSEC BUG - Cannot filter - Subnet Mask invalid"
- Reply: Q: "Re: IPSEC BUG - Cannot filter - Subnet Mask invalid"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Steven E. Adams" <stevea1@home2offic.com> Date: Fri, 6 Dec 2002 12:54:45 -0800
I have looked at this article before posting...
Traffic That Can--and Cannot--Be Secured by IPSec (253169)
Using IPSEC, I can not enter these addresses in the "IP
Filter List" to Filter ASIAN Networks:
200.0.0.0 / 255.0.0.0
203.0.0.0 / 255.0.0.0
211.0.0.0 / 255.0.0.0
212.0.0.0 / 255.0.0.0
213.0.0.0 / 255.0.0.0
218.0.0.0 / 255.0.0.0
219.0.0.0 / 255.0.0.0
(I am sure there are more)
I get an error "This is an invalid MASK for the specified
IP Address"
HOWEVER, When I enter in these IP Addresses, I DO NOT get
an error:
61.0.0.0 / 255.0.0.0
80.0.0.0 / 255.0.0.0
Is this a bug in the IPSEC Policy?
Is there a patch?
Am I doing something Wrong?
UNIX & LINUX Firewall rules do this no problem, IPCHAINS,
ETC... It would be great if Microsoft would get the IPSEC
to work they way I would like to use it.
Steven E. Adams
- Next message: al: "Re: Null Sessions - Restrict Anonymous"
- Previous message: Oli Restorick: "Re: network client question"
- Next in thread: x y: "Re: IPSEC BUG - Cannot filter - Subnet Mask invalid"
- Reply: x y: "Re: IPSEC BUG - Cannot filter - Subnet Mask invalid"
- Reply: Q: "Re: IPSEC BUG - Cannot filter - Subnet Mask invalid"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|