This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
nas-samba [2022/01/26 03:15] – hogwild | nas-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/ | + | The File sharing menu allows you to enable and configure Samba filesharing. Samba is a Linux clone/ |
+ | |||
+ | Microsoft' | ||
- | Microsoft' | ||
===== Samba File Sharing ===== | ===== Samba File Sharing ===== | ||
Line 14: | Line 15: | ||
* No | * No | ||
- | * Yes, no Authentication | + | * Yes, (with) |
* 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. | ||
\\ | \\ | ||
- | {{: | ||
- | **Samba protocol version**: | + | 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. |
- | SMBv1 | + | \\ {{: |
- | SMBv2 | + | **Samba protocol version**: |
- | SMBv1 + SMBv2 | + | * SMBv1 |
+ | * SMBv2 | ||
+ | * SMBv1 + SMBv2 | ||
- | This allows you to select the maximum version of SMB that will be supported. Note that it is good practice to enable both SMB1 and SMB2. Imposing a specific version might seem like a good idea, but could lead to situations in which clients support only one version. This may generate unwanted log errors, such as the one in the image below: | + | \\ |
- | \\\\ {{: | + | This allows you to select the maximum SMB version 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 so are not supported. This may generate unwanted 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:** |
- | **Client Codepage**: Code pages are used by DOS and Windows clients to determine rules for mapping lowercase letters | + | **Workgroup Name:** Here, specify the WORKGROUP name (logical grouping) of PCs for devices |
- | **Network Interfaces**: Defines | + | **Client Codepage: |
+ | |||
+ | **Network Interfaces:** In this field, you define | ||
{{: | {{: | ||
Line 45: | Line 48: | ||
\\ | \\ | ||
- | **Samba Custom Configuration**: Here you can pass user-defined parameters | + | **Samba Custom Configuration:** Here, you can specify |
- | **Auto-share all USB Partitions**: | + | **Auto-share all USB Partitions: |
- | * Disabled | + | * Disabled |
- | * Read Only | + | * Read Only - Users can only open files and browse the storage content |
- | * Read-Write | + | * Read-Write |
- | * Hidden 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. | + | \\ |
- | | + | **Options:** Configures your Samba server to perform additional network roles: |
- | | + | |
- | * Hidden Read-Write: This is similar to Read-Write, but allows access to hidden content (for example, files starting with a dot (.) . | + | * 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]]. | + | **Share name:** This is the share name that appears under the [[\\WORKGROUP\$routerhostname]]. |
- | **Directory**: This defines where the share maps in the real filesystem. | + | **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. | + | **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 is the network level access rights | + | **Access Level:** This specifies |
* 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. | 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 the network, but will still be available/ | + | **Hidden:** A hidden share is not visible when browsing the network, but will still be available/ |
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||