Firewall ConfigurationPage edited by Robbie GemmellChanges (3)
Full ContentConfigurationThe access restrictions apply either to the server as a whole or too a particular virtualhost. Rules are evaluated in the virtualhost first, then the server as a whole (most-specific to least-specific). This allows whole netblocks to be restricted from all but one virtualhost. A <firewall> element would appear in either the <broker><security> section or inside the equivalent <virtualhost><security> element. Elements inside <firewall> would be <rule> or <xml fileName="path"/> which can be used to include further rules at that point in the rule chain. <rule> must have action and either hostname or network attributes. The action attribute must be either allow or deny. Host contains a comma seperated list of regexps against which it would match the reverse dns lookup of the connecting IP. Network contains a comma seperated list of of CIDR networks against which the IP would be matched. The first <rule> which matched the connection would apply. If no rules applied, the default-action would apply. For example, the following could appear in config.xml: <broker> <security> <firewall default-action="" class="code-quote">"deny"> <rule access="allow" hostname="*.qpid.apache.org"/> <xml fileName="/path/to/file" /> <rule access="allow" network="192.168.1.0/24" /> <rule access="allow" network="10.0.0.0/8" /> </firewall > </security> </broker> And the following could appear in virtualhosts.xml: <virtualhosts> <virtualhost> <name>prod</name> <prod> <security> <firewall> <rule access="deny" network="192.168.1.0/24"/> </firewall> </security> </prod> </virtualhost> </virtualhosts> Any machine in the 192.168.1.0/24 network would be allowed access to any virtualhost other than prod
Change Notification Preferences
View Online
|
View Changes
|
Add Comment
|
- [CONF] Apache Qpid > Firewall Configuration confluence
- [CONF] Apache Qpid > Firewall Configuration confluence