ACL and Wildcard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 03:34 AM
Wildcard defaulting to the first value in the range of the wildcard and not allowing for any other value.
The default value of 0 in the third octet worked, but no other value worked with the ACL rule in place. The wildcard mask should have allowed for all values (0 - 255).
Can anyone explain to me why this is happening on my Cisco 9300 switch
- Labels:
-
Catalyst 9000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 04:20 AM
I need to see the ACL statement line you enter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 08:26 AM
And expected packet and expected results.
Also helpful is describing specific switch model, specific IOS being used and feature license(s).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 04:23 AM
permit 12.0.0.22 0.0.255.0
The above is the command used
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 04:42 AM - edited 03-14-2023 04:19 PM
...check my comment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 04:49 AM
I think you dont understand fully. the network range that i want to come across is 12.0.X.22 0.0.255.0 so the third octet will be the only one to change. I think I kinda know what the error is, and why that traffic cannot traverse the network.
The ACL should be written
permit IP 12.0.0.22 0.0.255.0
That should allow that intresting traffic to come through. right now it is written permit 12.0.0.22 0.0.255.0 which is not doing anything or allowing anything.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 05:00 AM - edited 03-14-2023 04:19 PM
check my comment ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 07:44 AM
Ah, finally some additional information.
Yes, you can write an ACL ACE such as permit IP 12.0.0.22 0.0.255.0, but will it provide the results you desire?
That ACL should match:
12.0.0.22
12.0.1.22
12.0.2.22
.
.
12.0.254.22
12.0.255.22
Is that the results you desire and if so, not obtaining?
If your looking for the network prefix 12.0.0.0/16 that would be:
permit IP 12.0.<0..255>.<0..255> 0.0.255.255 (as also described by @MHM Cisco World )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 07:25 AM
I am looking for the
12.0.0.22
12.0.1.22
12.0.2.22
....
12.0.254.22
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 07:25 AM
and i am not obtaining it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 09:10 AM
Ok then, post the actual ACL, in full, actual interface(s) config(s), src and dest packet IPs and expected flow for traffic through interface(s).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 10:08 AM
I can not post all that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 10:22 AM
Ok, no problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 04:31 AM
- You may find this tool useful : https://cway.cisco.com/tools/accesslist/
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
