Site Tools


nas-samba

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
nas-samba [2022/01/26 02:49] – formatting, grammar hogwildnas-samba [2023/07/01 01:48] (current) – [Additional Share List] -grammar, formatting hogwild
Line 1: Line 1:
 ====== File sharing ====== ====== File sharing ======
  
-The File sharing menu allows you to enable and configure Samba filesharing. Samba is a Linux clone/replica of Microsoft's SMB (Server Message Block) filesharing protocol. Samba allows FreshTomato to "speak" the same language as Windows so files can be exchanged between Windows and Linux-based systems (such as FreshTomato). This can allow you to use your FreshTomato router as a NAS drive, if you connect USB storage, such as an external hard drive or flash drive.+The File sharing menu allows you to enable and configure Samba filesharing. Samba is a Linux clone/replica of Microsoft's SMB (Server Message Block) filesharing protocol. Samba allows FreshTomato to "speak" the same language as Windows for file sharing between Windows and Linux-based systems (such as FreshTomato). This allows you to use your FreshTomato router as a NAS drive, if you connect USB storage, such as an external hard drive or flash drive
 + 
 +Microsoft's SMB protocol was recently upgraded to v3. FreshTomato's implementation supports v1 and v2 only. However, these are more than adequate for basic file sharing operations.
  
-Microsoft's SMB protocol has been upgraded in recent years to v3. FreshTomato's implementation supports v1 and v2 only. This is more than adequate for basic filesharing operations. 
  
 ===== Samba File Sharing ===== ===== Samba File Sharing =====
Line 14: Line 15:
  
   * No   * No
-  * Yes, no Authentication+  * Yes, (with) no Authentication
   * Yes Authentication Required   * Yes Authentication Required
 +
 + \\
  
 For a basic setup, select //Yes no authentication. //If additional security is needed, it's recommended you select the //Yes, Authentication required// . Doing so will display two additional fields where a single username and password can be entered. For a basic setup, select //Yes no authentication. //If additional security is needed, it's recommended you select the //Yes, Authentication required// . Doing so will display two additional fields where a single username and password can be entered.
  
- \\\\  {{:pasted:20220110-125127.png}}\\  \\+ \\ {{:pasted:20220110-125127.png}}\\  \\
  
-**Samba protocol version**: SMBv1/SMBv2/SMBv1 + SMBv2 - defined the maximum level of SMB supported. Please note it is good practice to enable both SMB1 and SMB2, imposing a version might be a good idea but could lead into scenarios where clients support only one version. This might generate to unwanted logs e.g. like this:+**Samba protocol version**:
  
- \\\\  {{:pasted:20220111-092133.png}}\\  \\+  * SMBv1 
 +  * SMBv2 
 +  * SMBv1 + SMBv2
  
-**Disable GRO**: GRO (Generic Receive Offload) essentially combines together small packets to then be sent as a single large packet. This optimizes network utilization, but involves extra (sometime unwanted) Reassembly functions. This option is enabled by default, which disables this feature. This is the recommended setting unless you have other, specific requirements.+ \\
  
-**Workgroup Name**: Here, specify the WORKGROUP name (logical grouping) of PCs for devices to be displayed/organized (for Windows peer-to-peer network browsing). Note that the Windows 10 April 2018 (ver1803) update eliminated the use of Windows 10 HomegroupsWorkgroups, however, still exist in Windows 10/Windows 11.+This allows you to select the maximum SMB version supportedIt is good practice to enable both SMB1 and SMB2Imposing a specific version could lead to situations in which client devices aren't running a compatible version and so are not supportedThis may generate unwanted log errors, such as the one seen below:
  
-**Client Codepage**Code pages are used by DOS and Windows clients to determine rules for mapping lowercase letters to uppercase letters. Undefined by default can be set in case of case sensitivity issue. To check what Codepage your systems are on (in Windows) run ''cmd.exe'' and type ''chcp'' to see the current code page.+ \\ \\ {{:pasted:20220111-092133.png}}\\  \\
  
-**Network Interfaces**: Defines to which local interface the samba service should be bound. (Default: br0).\\+**Disable GRO:**  GRO (Generic Receive Offload) combines small packets to be sent as a one large packetThis optimizes network utilization, but involves extra reassembly functions. The default, (Enableddisables the feature. Enabling this is recommended unless you have other requirements.
  
-{{:pasted:20220110-130832.png}}\\  \\   \\+**Workgroup Name:**  Here, specify the WORKGROUP name (logical grouping) of PCs for devices to be displayed/organized (for Windows peer-to-peer network browsing). Note that the Windows 10 April 2018 (ver. 1803) update eliminated the use of Windows 10 Homegroups. However, workgroups, still exist in Windows 10/11.
  
-**Samba Custom Configuration**: Here you can pass user-defined parameters to the samba process (configured in the smb.conf file)Consult the official samba documentation prior to entering options in this field.+**Client Codepage:**  DOS and Windows clients use code pages to determine rules for mapping lowercase letters to uppercase letters. Undefined, by default, can be set in scenarios where case sensitivity is an issueTo check what Windows Codepage your systems are on, run ''cmd.exe'' and type ''chcp'' to see the current code page.
  
-**Auto-share all USB Partitions**:+**Network Interfaces:**  In this field, you define to which local interface the samba service will be bound. (Default: br0).\\  \\ 
 + 
 +{{:pasted:20220110-130832.png}} 
 + 
 + \\ 
 + 
 +**Samba Custom Configuration:** Here, you can specify user-defined parameters for the samba process (configured in the smb.conf file). Consult samba documentation before using this field: [[https://www.samba.org|https://www.samba.org]]/ 
 + 
 +**Auto-share all USB Partitions:  **This lets you configure automatic sharing. As soon as storage with a compatible file system is connected to the USB port, its contents will be shared. 
 + 
 +  * Disabled - Automatic sharing will be disabled. 
 +  * Read Only - Users can only open files and browse the storage content 
 +  * Read-Write - Users have full control on visible content. 
 +  * Hidden Read-Write - While similar to Read-Write, this allows access to hidden content (such as files starting with a period). 
 + 
 + \\ 
 + 
 +**Options:** Configures your Samba server to perform additional network roles: 
 + 
 +  * Master Browser - If enabled, participate in the Master Browser election (when WINS is not available/defined). 
 + 
 + WINS Server - If enabled, act as WINS server on the network. DHCP clients will receive the data via DHCP. Static clients can be configured with FreshTomato's LAN IP address as their WINS server setting.\\ 
 + 
 + 
 +===== Additional Share List ===== 
 + 
 +In this table, you can define custom network shares that map to physical filesystems. These may overlap, or even conflict with the //Auto-share all Partition //function described above. 
 + 
 +**Share name:**  This is the share name that appears under the [[\\WORKGROUP\$routerhostname]]. 
 + 
 +**Directory:**  This defines where the share maps in the real filesystem. 
 + 
 +**Description:**  This is for description only, and appears when browsing the network. It has no functional role other than naming the share. 
 + 
 +**Access Level:**  This specifies the network-level access rights
  
-  * Disabled 
   * Read Only   * Read Only
   * Read-Write   * Read-Write
-  * Hidden Read-Write. 
  
-This allows you to configure automatic sharing. As soon as a storage medium is connected to the USB port (with a compatible filesystem) its contents will be shared.+ \\
  
-  * Read only: Users can only open files and browse the storage content. +Do not confuse this setting with the filesystem rightsTotal security is determined by executing logical AND operator on the Access Level rights and the filesystem rights.
-  * Read-Write: Users have full control on visible content. +
-  * Hidden Read-Write: This is similar to Read-Write, but allows access to hidden content (for example, files starting with dot (.) .+
  
- **Options**: Instruct your Samba server on additional network roles:\\  Master Browser: If enable it participate in the Master Browser election (when WINS is not available/defined).\\  WINS Server: Perform the role of Wins Server on the network. When enable clients will receive this info via DHCP but client with static addressing can point their WINS Server settings to FreshTomato's LAN IP.\\+**Hidden:**  A hidden share is not visible when browsing the network, but will still be available/usable if called directly (such as by the "net use" command in Windows).
  
-{{:pasted:20220110-134020.png}}\\ Additional Share List+ \\
  
-is where you define custom network shares mapping to physical filesystem. Remember this somehow would overlap with the Auto-share all Partition described above.\\ **Share name**: This is the share name appearing under the [[\\WORKGROUP\$routerhostname]].\\ **Directory**: Defines where the share maps in the real filesystem.\\ **Description**: This is a description only and appears when browsing the network. It has no functional role.\\ **Access Level**: This is the network level access right (Read Only / Read-Write). You must not confuse this with the filesystem rights, the two interact in a logical AND way (e.g. write on the filesystem AND write on the share is needed).\\ **Hidden**: Yes/No - If a share is hidden it will not be visible browsing the network but it will be available/usable if called directly.+ \\
  
  
nas-samba.1643165346.txt.gz · Last modified: 2022/01/26 02:49 by hogwild