Difference between revisions of "Firewall Configuration"
From OSNEXUS Online Documentation Site
m |
m (→Blocking iSCSI Access) |
||
| Line 14: | Line 14: | ||
service iptables restart | service iptables restart | ||
| − | == Blocking iSCSI Access == | + | == Blocking Storage Volume / iSCSI Access == |
If you're not using Storage Volumes via iSCSI you can block access to the iSCSI target service access like so: | If you're not using Storage Volumes via iSCSI you can block access to the iSCSI target service access like so: | ||
touch /etc/init.d/iptables.blockiscsi | touch /etc/init.d/iptables.blockiscsi | ||
service iptables restart | service iptables restart | ||
Revision as of 16:50, 15 May 2015
For most deployments there is no need to add firewall rules to block the standard storage services like NFS, CIFS, iSCSI. That said, for systems deployed with elevated security requirements or systems with ports that are facing public networks it is useful to block services that are not being used. The following sections outline how to block various storage services within QuantaStor using firewall rules.
Contents
Blocking NFS
If you're not using Network Shares with NFS you can block NFS service access like so:
touch /etc/init.d/iptables.blocknfs service iptables restart
Blocking CIFS/SMB
If you're not using Network Shares with CIFS/SMB Windows clients you can block SMB access to the Samba service access like so:
touch /etc/init.d/iptables.blocksmb service iptables restart
Blocking Storage Volume / iSCSI Access
If you're not using Storage Volumes via iSCSI you can block access to the iSCSI target service access like so:
touch /etc/init.d/iptables.blockiscsi service iptables restart
