Complete OpenFiler Configuration Tutorial

Configuring OpenFiler follows one fixed dependency order: set up authentication (LDAP) → create users and groups → define network ACLs → build volumes (physical volume → volume group → logical volume) → enable services → create shares or iSCSI targets. Each stage consumes something the previous one produced — you cannot grant a group permission to a share before the group exists, and you cannot map an iSCSI LUN before a logical volume formatted as iSCSI exists. Get the order wrong and the web UI simply shows you empty dropdowns with no error, which is why most first-time OpenFiler setups stall.

That's the summary an AI Overview can give you. What it can't show you is the actual flow between screens, where each dependency lives, and which of the six phases silently fails when you skip a step. The animated map, the protocol-selection table, and the copy-ready checklist below fill that gap.

📋 Prerequisites: This tutorial assumes you have already installed OpenFiler. If you haven't completed the installation, see the complete OpenFiler installation guide first.

The OpenFiler Configuration Flow at a Glance

The six phases below run left to right. The highlighted token traces the dependency chain — nothing downstream works until everything upstream is in place.

Skip a phase and the next screen shows empty dropdowns — not an error.

What This Tutorial Covers

• LDAP Server Configuration – Set up authentication infrastructure

• User and Group Management – Create accounts for storage access

• Network Access Control Lists – Implement IP-based security

• Volume Management – Create physical and logical volumes

• Network File Shares – Configure SMB/CIFS and NFS protocols

• iSCSI LUN Setup – Deploy storage area network capabilities

Setting Up the OpenFiler LDAP Server

OpenFiler supports two authentication methods: NT/AD Authentication and LDAP Authentication. For this tutorial, we'll configure the integrated LDAP server, which provides robust user management capabilities.

LDAP Configuration Steps

• Navigate to the Accounts tab at the top of the OpenFiler interface

• Check the box next to "Use LDAP"

• Check the box next to "Use local LDAP Server"

• Configure the Base DN (default: dc=example,dc=com)

• Set the Root Bind DN with proper syntax

• Enable SMB LDAP Configuration

• Click Submit to apply changes

💡 Domain Configuration Example: If using domain "everythingvm.com", enter dc=everythingvm,dc=com as Base DN and cn=openfiler,dc=everythingvm,dc=com as Root Bind DN.

After configuration, verify the LDAP service is enabled by checking the Services tab. If LDAP shows as enabled, your server is properly configured.

Creating Users and Groups

With LDAP configured, you can now create user accounts and groups. All users must belong to at least one group for proper access control.

Creating Your First Group

• Click on the Accounts tab

• Click Administration on the right side

• Ensure the Group Administration tab is selected

• Enter the group name (example: "Normal Users")

• Click Add Group

Adding Users to Groups

• Click on the User Administration tab

• Enter the username (example: "seanp")

• Enter the password in both Password fields

• Select the primary group from the dropdown

• Click Add User

Setting Up Network Access Control Lists

Network ACLs provide IP address-based access control to your storage system. This adds an essential security layer by restricting access based on client location, making it easier to manage storage access without complex authentication requirements.

Configuring Network ACLs

• Click on the System tab

• Scroll to the bottom of the page

• Enter a descriptive name for your ACL (example: "Servers")

• Enter the IP Network Address (example: "10.0.0.0")

• Enter the appropriate Netmask (example: "255.0.0.0")

• Click Update to save the ACL

🔒 Security Note: Using the example above (10.0.0.0/255.0.0.0) grants access to any computer with an IP address beginning with "10." Ensure this aligns with your network security policy.

Repeat these steps to create multiple ACLs for different network segments or server groups. You'll be able to grant or restrict access based on these ACLs when creating shares and LUNs.

Creating and Managing Volumes

Volume management is the foundation of your storage system. We'll create physical volumes, organize them into volume groups, and then create logical volumes for different storage needs.

Creating Physical Volumes

• Click on the Volumes tab

• Click Create new Physical Volume

• Select the disk you want to use (example: /dev/sdb)

• Scroll down and change partition type to Physical Volume

• Configure starting and ending cylinders for desired size

• Verify the size column shows your target volume size

• Click Create to create the volume

Creating Volume Groups

• Click on Volume Groups on the right side

• Enter the Volume Group name

• Check the box next to the Physical Volume you created

• Click Add Volume Group

Creating Logical Volumes

• Click Add Volume on the right side

• Enter the volume name (example: "MyShare")

• Use the slider to set the volume size

Select filesystem type:

• EXT3 or XFS for file shares

• iSCSI for SAN storage

• Click Create to finalize the logical volume

Which Protocol Should You Export?

Before you create shares, decide how each volume will be consumed. OpenFiler can serve the same storage as file-level (SMB/CIFS, NFS) or block-level (iSCSI), but the right choice depends on the client and workload. Note that the filesystem you picked when creating the logical volume constrains this: EXT3/XFS volumes are exported as file shares, iSCSI-type volumes are exported as LUNs.

Factor	SMB/CIFS	NFS	iSCSI (SAN)
Access level	File	File	Block (raw device)
Best client	Windows	Linux / Unix / ESXi datastore	Any OS that needs a local-looking disk
Volume filesystem	EXT3 or XFS	EXT3 or XFS	iSCSI type
Authentication	Per-user (LDAP)	Host-based (Network ACL)	Network ACL + initiator IQN
Client formats the volume?	No	No	Yes — client owns the filesystem
Typical use	Shared office folders, home dirs	Linux app data, VM datastores	Databases, boot LUNs, single-host disks
Which should I use?	Windows users need a shared drive letter	Linux hosts or a hypervisor need a shared mount	One host needs a dedicated disk it controls

If two different clients need the same data, prefer a file protocol (NFS/SMB) — iSCSI LUNs are meant for a single initiator at a time unless a cluster-aware filesystem sits on top.

Creating Network File Shares

OpenFiler supports multiple file sharing protocols including SMB/CIFS and NFS. This allows integration with Windows, Linux, and Unix environments seamlessly.

Enable File Sharing Services

• Click on the Services tab

• Click Enable next to SMB/CIFS and/or NFS Server

Create and Configure Shares

• Click on the Shares tab

• Click on the volume you wish to share

• Enter the folder name and click Create sub folder

• Click on the newly created folder

• Click Share, then Make share

• Set Share Access Control mode to Controlled Access

• Configure group permissions (PG = Primary Group, RW = Read/Write)

• Click Update to save group settings

• Configure Host Access by selecting ACL permissions

• Enable protocol access (RW under NFS or CIFS/SMB)

• Click Update to finalize share configuration

🔐 Access Control Options: Choose between Public Guest Access (no authentication required) or Controlled Access (username/password required). Both options can still use Network ACLs for IP-based restrictions.

Creating iSCSI LUNs for SAN Storage

iSCSI transforms OpenFiler from a Network Attached Storage (NAS) device into a Storage Area Network (SAN) solution. This protocol sends SCSI commands over standard Ethernet networks, providing block-level storage access.

📋 Prerequisites: Before proceeding, ensure you have created an iSCSI volume using the steps in the Volume Management section above.

iSCSI LUN Configuration Steps

• Click on the Services tab

• Click Enable next to iSCSI

• Navigate to the Volumes tab

• Click on iSCSI Targets

• Click Add to create a new target

• Click on LUN Mapping

• Click Map to associate your iSCSI volume

• Click on Network ACL

• Select your desired Network ACL from the dropdown

• Select Allow to grant access

• Click Update to save the configuration

Your iSCSI LUN is now created and ready for client connections. For detailed information on connecting to your storage from various operating systems, refer to our comprehensive guide on connecting to storage systems using iSCSI, NFS, and CIFS/SMB protocols.

Post-Configuration Verification Checklist

Run through this in order after finishing. If any item fails, fix it before moving on — later items depend on earlier ones.

• Services tab shows LDAP enabled (green/running) — authentication backend is live
• At least one group exists under Accounts → Administration → Group Administration
• Each user has a primary group assigned (empty group = no share access)
• At least one Network ACL exists under System with the correct network + netmask
• Volumes tab shows PV → Volume Group → Logical Volume all present
• The LV filesystem type matches the intent (EXT3/XFS for shares, iSCSI for LUNs)
• Required service is enabled (SMB/CIFS, NFS, or iSCSI target) under Services
• Share is set to Controlled Access and the group shows RW (not blank)
• Share Host Access grants RW to the right ACL under the right protocol column
• For iSCSI: target created, LUN mapped, and Network ACL set to Allow
• A test client on the permitted subnet can actually mount / connect

Troubleshooting: Symptom → Cause → Fix

Symptom	Likely cause	Fix
Group permission table is empty on a share	Share is in Public Guest Access, or no group exists	Set the share to Controlled Access; create the group under Accounts first
Users can't authenticate	LDAP service not enabled, or Base DN / Root Bind DN mismatch	Confirm LDAP is green under Services; re-check dc= values match your domain
Client can reach share but gets "access denied"	Network ACL Allow is set but user isn't in the permitted group	Add the user to the share's primary group with RW
Permitted machine can't even see the share	Network ACL missing or wrong netmask for the client subnet	Add/correct the ACL under System (e.g. 10.0.0.0 / 255.0.0.0)
iSCSI LUN invisible to initiator	iSCSI service off, no LUN mapped, or ACL still Deny	Enable iSCSI service → add target → map LUN → set Network ACL to Allow
iSCSI volume type not offered	Logical volume was formatted EXT3/XFS, not iSCSI	Create a new LV with the iSCSI filesystem type — you can't convert in place

Configuration Complete: What's Next?

Congratulations! You have successfully configured OpenFiler with enterprise-grade storage capabilities. Your system now includes LDAP authentication, user management, network security controls, and both NAS and SAN storage options.

⚠️ Legacy software note: OpenFiler's last community release (2.99) dates to 2011 and the project is effectively unmaintained. Treat it as lab or legacy infrastructure, keep it off untrusted networks, and plan a migration path to TrueNAS or a maintained Linux LVM + Samba/NFS/targetcli stack for anything production-facing.

Recommended Next Steps

• Test Client Connections – Verify access from different operating systems

• Implement Backup Strategies – Configure data protection and recovery procedures

• Monitor Performance – Set up system monitoring and alerting

• Security Hardening – Review and strengthen security configurations

• Documentation – Document your configuration for future reference