
Controlling Network Access Permissions
Configuring Application Denial Policies
138
Ruckus Wireless, Inc.
•
“www.corporate.com” – This will block access to the host web server at the
organization “corporate.com” i.e. the FQDN. It will not block access to any other
hosts such as ftp, ntp, smtp, etc. at the organization “corporate.com”.
•
“corporate.com” – this will block access to all hosts at the domain “corpo-
rate.com” i.e. it will block access to www.corporate.com, ftp.corporate.com,
smtp.corporate.com, etc.
•
“corporate” – This will block access to any FQDN containing the text “corporate”
in any part of the FQDN. Care should be taken to use as long as possible string
for matching to prevent inadvertently blocking sites that may contain a shorter
string match i.e. if the rule is “net” then this will block access to any sites that
have the text “net” in any part of the FQDN or .net as the FQDN suffix.
•
*.corporate.com – This is an invalid rule. Wildcard “*” and other regular expres-
sions cannot be used in any part of the FQDN.
•
“www.corporate.com/games” - This is an invalid rule. The filter cannot parse and
block access on text after the FQDN, i.e., in this example it cannot filter the micro-
site “/games”.
Notes:
•
Many global organizations have both a “.com” suffix and country specific suffix
such as “.co.uk”, “.fr”, “.au”.etc. To block access to say the host web server in
all regional specific web sites for an organization a rule like “www.corporate”
could be used.
•
Many global organizations use distributed content delivery networks such as
Akamai. In such cases creating a rule such as “www.corporate.com” may not
prevent access to the entire site. Further investigation of the content network
behavior may need to be undertaken to fully prevent access.
When using Port based rules:
There is no distinction between the TCP and UDP protocols, so care should be
taken if wishing to block a specific application port as that will apply to both IP
protocols and may inadvertently block another application using the other protocol.
Содержание ZoneDirector 3000
Страница 2: ......
Страница 4: ...4 Ruckus Wireless Inc...
Страница 16: ...Documentation Feedback 16 Ruckus Wireless Inc...
Страница 106: ...Enabling Bonjour Gateway Example Network Setup 106 Ruckus Wireless Inc...
Страница 147: ...Controlling Network Access Permissions Blocking Client Devices ZoneDirector 9 8 User Guide 800 70599 001 Rev B 147...
Страница 298: ...Monitoring Location Services Access Point Sensor Information 298 Ruckus Wireless Inc...
Страница 342: ...Working with Guest Passes Delivering Guest Passes via SMS 342 Ruckus Wireless Inc...
Страница 364: ...Best Practices and Recommendations Recovering an Isolated Mesh AP 364 Ruckus Wireless Inc...
Страница 388: ...Support Entitlement Upgrading the License with Smart Redundancy 388 Ruckus Wireless Inc...
Страница 410: ...Restarting ZoneDirector Streaming Mode 410 Ruckus Wireless Inc...
Страница 420: ...Best Practice Checklist Elevation of RAPs and MAPs 420 Ruckus Wireless Inc...
Страница 428: ...428 Ruckus Wireless Inc band selection 236 255 ZoneFlex APs upgrading software 368...
Страница 429: ...ZoneDirector 9 8 User Guide 800 70599 001 Rev B 429...
Страница 430: ...Copyright 2006 2014 Ruckus Wireless Inc 350 West Java Dr Sunnyvale CA 94089 USA www ruckuswireless com...