- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: 5406zl ACL Guest Wlan
Switches, Hubs, and Modems
1752795
Members
5987
Online
108789
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
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
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-01-2010 03:28 AM
тАО03-01-2010 03:28 AM
5406zl ACL Guest Wlan
Hi there,
I just want to create a simple ACL for one of our Customers. They want tu build a Wlan Infrastructure with a Guest Wlan.
The Guest Wlan should be seperated from the other VLANS:
ip access-list extended "Guest_Wlan"
10 permit ip 192.168.137.0 0.0.0.0
20 deny any any
exit
vlan 3
name "Guest_Wlan"
ip helper-address 192.168.137.1
untagged A3
ip access-group "Guest_Wlan" in
exit
Is it right, that I only have to deny the hole traffic? The GW for the Clients is the Lancom Wlan Controller...
Thank you for helping :)
I just want to create a simple ACL for one of our Customers. They want tu build a Wlan Infrastructure with a Guest Wlan.
The Guest Wlan should be seperated from the other VLANS:
ip access-list extended "Guest_Wlan"
10 permit ip 192.168.137.0 0.0.0.0
20 deny any any
exit
vlan 3
name "Guest_Wlan"
ip helper-address 192.168.137.1
untagged A3
ip access-group "Guest_Wlan" in
exit
Is it right, that I only have to deny the hole traffic? The GW for the Clients is the Lancom Wlan Controller...
Thank you for helping :)
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2010 06:10 AM
тАО03-01-2010 06:10 AM
Re: 5406zl ACL Guest Wlan
Hi,
Ok, there are a few issues there.
> 10 permit ip 192.168.137.0 0.0.0.0
That line isn't complete, it specifies a source but not a destination.
Also your mask is wrong. ACL's use wildcards that aren't the same as a normal network mask (they're the inverse really). So if you want to specify the 192.168.137.0/24 subnet you use the statement 192.168.137 0.0.0.255.
You haven't really said what you _do_ want to give the guest VLAN access to so I'll just give you an example I've made up :)
1) Allow the hosts access to your DNS server
permit tcp 0.0.0.0 255.255.255.255 DNS_SRV_IP 0.0.0.0 eq 53
permit udp 0.0.0.0 255.255.255.255 DNS_SRV_IP 0.0.0.0 eq 53
2) Deny them access to any other IPs on your subnet (replace the 192.168 with your address range or add in multiple lines for all your ranges)
deny ip 0.0.0.0 255.255.255.255 192.168.0.0 0.0.255.255
3) Allow the guest clients any other access you want, e.g web access
permit tcp 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 eq 80
4) There is an implicit "deny any any" rule at the end of every acl
Now just apply this to the VLAN in the correct direction (the direction is with respect to the switch)
ip access-group "guest_acl" in
If you have any issues the manual pages for ACL's are quite detailed and useful:
http://cdn.procurve.com/training/Manuals/2610-Security-Oct2008-59918642.pdf
Ok, there are a few issues there.
> 10 permit ip 192.168.137.0 0.0.0.0
That line isn't complete, it specifies a source but not a destination.
Also your mask is wrong. ACL's use wildcards that aren't the same as a normal network mask (they're the inverse really). So if you want to specify the 192.168.137.0/24 subnet you use the statement 192.168.137 0.0.0.255.
You haven't really said what you _do_ want to give the guest VLAN access to so I'll just give you an example I've made up :)
1) Allow the hosts access to your DNS server
permit tcp 0.0.0.0 255.255.255.255 DNS_SRV_IP 0.0.0.0 eq 53
permit udp 0.0.0.0 255.255.255.255 DNS_SRV_IP 0.0.0.0 eq 53
2) Deny them access to any other IPs on your subnet (replace the 192.168 with your address range or add in multiple lines for all your ranges)
deny ip 0.0.0.0 255.255.255.255 192.168.0.0 0.0.255.255
3) Allow the guest clients any other access you want, e.g web access
permit tcp 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 eq 80
4) There is an implicit "deny any any" rule at the end of every acl
Now just apply this to the VLAN in the correct direction (the direction is with respect to the switch)
ip access-group "guest_acl" in
If you have any issues the manual pages for ACL's are quite detailed and useful:
http://cdn.procurve.com/training/Manuals/2610-Security-Oct2008-59918642.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2010 07:03 AM
тАО03-01-2010 07:03 AM
Re: 5406zl ACL Guest Wlan
Hi,
thank you.
I only want the Clients to get access to our Firewall (192.168.137.1/24). The Firewall has only one allow rule (allow hhtp), all other traffic isn├В┬┤t allowed. DHCP Server for our Clients is the Firewall.
ip access-list extended "wlan_gues"
10 permit tcp 0.0.0.0 255.255.255.255 192.168.137.1 0.0.0.0
20 permit udp 0.0.0.0 255.255.255.255 192.168.137.1 0.0.0.0
30 deny ip 0.0.0.0 255.255.255.255 192.168.0.0 0.255.255.255
permit tcp 0.0.0.0 255.255.255.255
vlan 3
name "WLAN_Guest"
no ip address
ip access-group "wlan_guest" vlan
ip access-group "wlan_guest" in
exit
thank you.
I only want the Clients to get access to our Firewall (192.168.137.1/24). The Firewall has only one allow rule (allow hhtp), all other traffic isn├В┬┤t allowed. DHCP Server for our Clients is the Firewall.
ip access-list extended "wlan_gues"
10 permit tcp 0.0.0.0 255.255.255.255 192.168.137.1 0.0.0.0
20 permit udp 0.0.0.0 255.255.255.255 192.168.137.1 0.0.0.0
30 deny ip 0.0.0.0 255.255.255.255 192.168.0.0 0.255.255.255
permit tcp 0.0.0.0 255.255.255.255
vlan 3
name "WLAN_Guest"
no ip address
ip access-group "wlan_guest" vlan
ip access-group "wlan_guest" in
exit
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