This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
nas-samba [2023/04/26 17:44] – [Samba File Sharing] -Condense, formatting hogwild | nas-samba [2024/11/27 17:15] (current) – [Samba File Sharing] -Formatting hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== File sharing ====== | ====== File sharing ====== | ||
- | The File sharing menu allows | + | In the File sharing 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 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 you need additional security, it's recommended you select //Yes, Authentication required//. Doing so will display additional fields to set a single username and password. |
+ | |||
+ | \\ {{: | ||
**Samba protocol version**: | **Samba protocol version**: | ||
Line 27: | Line 30: | ||
* SMBv1 + SMBv2 | * SMBv1 + SMBv2 | ||
- | This allows you to select the maximum SMB version that will be supported. It is good practice to enable both SMB1 and SMB2. Imposing a specific version could lead to situations in which client devices aren't running a compatible version and therefore aren't supported. This may generate unwanted log errors, such as the one seen below: | + | \\ |
- | \\\\ {{: | + | This lets you select the highest SMB version supported. It's good practice to enable both SMB1 and SMB2. Imposing a specific version can cause client devices running an incompatible version to be unsupported. This may generate log errors, such as the one seen below: |
- | **Disable GRO**: GRO (Generic Receive Offload) essentially combines together small packets to then be sent as a single large packet. This optimizes network utilization, | + | \\ \\ {{:pasted: |
- | **Workgroup Name**: Here, specify the WORKGROUP name (logical grouping) of PCs for devices | + | **Disable GRO:** Generic Receive Offload combines small packets |
- | **Client Codepage**: DOS and Windows clients use Code pages to determine rules for mapping lowercase letters to uppercase letters. Undefined by default | + | This optimizes network utilization, |
- | **Network Interfaces**: Defines | + | \\ |
+ | |||
+ | **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 ones. Undefined, by default, can be set in cases where case sensitivity is an issue. To check your Windows Codepage, run '' | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Network Interfaces:** here, define | ||
{{: | {{: | ||
Line 43: | Line 60: | ||
\\ | \\ | ||
- | **Samba Custom Configuration**: Here, you can pass user-defined | + | **Samba Custom Configuration:** here, specify |
- | **Auto-share all USB Partitions**: | + | Consult samba documentation before using this field: [[https:// |
- | * Disabled | + | \\ |
- | * Read Only | + | |
- | * Read-Write | + | |
- | * Hidden Read-Write. | + | |
- | This allows | + | **Auto-share all USB Partitions: **lets |
- | * Read only: Users can only open files and browse the storage | + | As soon compatible USB filesystem |
- | * 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 a dot (.) . | + | |
- | **Options**: Instruct your Samba server | + | * Disabled - automatic sharing will be disabled. |
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Options:** configures | ||
+ | |||
+ | * Master Browser | ||
+ | * 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' | ||
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||