- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Access list not behaving properly
Switches, Hubs, and Modems
1753774
Members
6977
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2005 07:19 AM
03-31-2005 07:19 AM
Access list not behaving properly
I have the following line in a short access list that allows web traffic to go to a particular server:
permit tcp 172.16.5.0 0.0.0.255 172.16.1.3 255.255.255.255 eq 80
This access list only contains 2 more lines, they allow traffic to DNS on the same server and symantec web security on another server (ports 53 and 8002.
The whole list looks like the following:
ip access-list extended "guest"
permit tcp 172.16.5.0 0.0.0.255 172.16.1.9 255.255.255.255 eq 8002
permit udp 172.16.5.0 0.0.0.255 172.16.1.3 255.255.255.255 eq 53
permit tcp 172.16.5.0 0.0.0.255 172.16.1.3 255.255.255.255 eq 80
exit
This list should block everything except for the 3 things that are explicitly allowed. It
The list works except for the fact that it lets everything through port 80. You can access any server through port 80.
This is not right, the list is configured to only allows traffic to the 172.16.1.3 server. There is no wildcard....
Can anyone explain this behavior?
permit tcp 172.16.5.0 0.0.0.255 172.16.1.3 255.255.255.255 eq 80
This access list only contains 2 more lines, they allow traffic to DNS on the same server and symantec web security on another server (ports 53 and 8002.
The whole list looks like the following:
ip access-list extended "guest"
permit tcp 172.16.5.0 0.0.0.255 172.16.1.9 255.255.255.255 eq 8002
permit udp 172.16.5.0 0.0.0.255 172.16.1.3 255.255.255.255 eq 53
permit tcp 172.16.5.0 0.0.0.255 172.16.1.3 255.255.255.255 eq 80
exit
This list should block everything except for the 3 things that are explicitly allowed. It
The list works except for the fact that it lets everything through port 80. You can access any server through port 80.
This is not right, the list is configured to only allows traffic to the 172.16.1.3 server. There is no wildcard....
Can anyone explain this behavior?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2005 07:24 AM
03-31-2005 07:24 AM
Re: Access list not behaving properly
bah, the solution is to use 0.0.0.0 instead of 255.255.255.255...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP