This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| nas-samba [2023/04/26 18:32] – [Samba File Sharing] -format hogwild | nas-samba [2025/07/11 16:47] (current) – [File sharing] -Grammar, condense hogwild | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== File sharing ====== | ====== File sharing ====== | ||
| - | The File sharing | + | In this menu, you can enable and configure Samba filesharing. Samba is a Linux clone of Microsoft' |
| + | |||
| + | Microsoft' | ||
| - | Microsoft' | ||
| ===== Samba File Sharing ===== | ===== Samba File Sharing ===== | ||
| Line 17: | Line 18: | ||
| * Yes Authentication Required | * Yes Authentication Required | ||
| - | For a basic setup, select //Yes no authentication. //If additional security | + | \\ |
| + | |||
| + | For a basic setup, select //Yes no authentication. //If you need additional security, it's recommended you select //Yes, Authentication required//. Doing so will display additional fields | ||
| \\ {{: | \\ {{: | ||
| Line 27: | Line 30: | ||
| * SMBv1 + SMBv2 | * SMBv1 + SMBv2 | ||
| - | This allows | + | \\ |
| + | |||
| + | This lets you select the highest | ||
| \\ \\ {{: | \\ \\ {{: | ||
| - | **Disable GRO**: GRO (Generic Receive Offload) essentially | + | **Disable GRO:** Generic Receive Offload combines small packets to be sent as a one large one. |
| - | **Workgroup Name**: Here, specify the WORKGROUP name (logical grouping) of PCs for devices to be displayed/ | + | This optimizes network utilization, but involves extra reassembly. The default, |
| - | **Client Codepage**: DOS and Windows clients use Code pages to determine rules for mapping lowercase letters to uppercase | + | \\ |
| + | |||
| + | **Workgroup Name:** here, enter the Windows WORKGROUP name for PCs to be displayed/ | ||
| + | |||
| + | Note that the Windows 10 April 2018 (v.1803) update eliminated Windows Homegroups. However, workgroups still exist in Windows 10/11. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Client Codepage:** sets the Windows code page. | ||
| + | |||
| + | Windows clients use code pages to determine rules for mapping lowercase letters to uppercase | ||
| + | |||
| + | \\ | ||
| - | **Network Interfaces**: Defines | + | **Network Interfaces:** here, define |
| {{: | {{: | ||
| Line 43: | Line 60: | ||
| \\ | \\ | ||
| - | **Samba Custom Configuration**: Here, you can specify user-defined | + | **Samba Custom Configuration:** here, specify user-defined |
| - | **Auto-share all USB Partitions**: | + | Consult samba documentation before using this field: [[https:// |
| - | This allows you to configure automatic sharing. As soon as a storage medium is connected to the USB port, its contents will be shared. The storage medium must use a compatible filesystem. | + | \\ |
| - | | + | **Auto-share all USB Partitions: **lets you configure automatic sharing. |
| - | | + | |
| - | * Read-Write: Users have full control on visible content. | + | |
| - | | + | |
| - | **Options**: | + | As soon compatible USB filesystem storage is connected, its contents are shared. |
| - | * Master Browser: If enabled, participate in the Master Browser election (when WINS is not available/ | + | |
| - | * WINS Server: When enabled, act as a WINS server | + | * Read Only - users can only open files and browse \\ the storage content. |
| + | * Read-Write - users have full control of visible content. | ||
| + | * Hidden Read-Write - Read-Write privileges plus access to \\ hidden content (such as files starting with a period). | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Options: | ||
| + | |||
| + | | ||
| + | * WINS Server | ||
| ===== Additional Share List ===== | ===== Additional Share List ===== | ||
| - | In this table, you can define custom network shares that map to physical filesystems. These may overlap, or possibly | + | In this table, you can define custom network shares that map to physical filesystems. These may overlap, or even conflict with the // |
| - | **Share name**: This is the share name which appears under the [[\\WORKGROUP\$routerhostname]]. | + | \\ |
| - | **Directory**: This defines where the share maps in the real filesystem. | + | **Share name:** |
| - | **Description**: | + | \\ |
| - | **Access Level**: This is the network level access rights | + | **Directory: |
| + | |||
| + | \\ | ||
| + | |||
| + | **Description: | ||
| + | |||
| + | **Access Level:** | ||
| * Read Only | * Read Only | ||
| * Read-Write | * Read-Write | ||
| - | Do not confuse this setting with the filesystem rights. Total security is determined by executing a logical AND operator on the Access Level rights and the filesystem rights. | + | \\ |
| - | **Hidden**: A hidden share will not be visible when browsing | + | Don't confuse this with filesystem rights. Total security is calculated by executing a logical AND operation on the Access Level rights and filesystem rights. |
| + | |||
| + | \\ | ||
| + | |||
| + | **Hidden:** A hidden share isn' | ||
| + | |||
| + | \\ | ||
| + | |||
| + | \\ | ||