smb ports = 139

	kernel oplocks = No
	ldap ssl = No

Samba recognises two special strings. %v will be replaced with the Samba version number. %h will be replaced with the hostname. Thus, a Server comment like Server %h with Samba %v will give you basic information about what version of Samba is running on your Slug.

Using server comment to gather version information

The NSLU2 web interface lets you set a "Server comment". This corresponds to the smb.conf parameter "Server string". This string will appear in browse lists next to the machine name.

Samba recognises two special strings. %v will be replaced with the Samba version number. %h will be replaced with the hostname. Thus, a Server comment like Server v will give you basic information about what version of Samba is running on your Slug.

Resolving 'Unable to open printcap file /opt/etc/printcap for read'

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

Resolving issue that file modification times aren't preserved when copying files

After a) unslinging my NSLU2 and b) upgrading my Mac OS X machine from Mac OS X 10.3 to 10.5, I noticed that when I copied files from my computer to the NSLU2's share, the modification times for the files were no longer preserved. They were reset to the current time. Also, the touch -t command from the Mac OS X command line to a file on the NSLU2's share failed to set the modtime to the specified value.

Adding a %v to my server comment, I discovered that I was running Samba 3.0.11. I upgraded Samba to the current (as of December 2009) version in ipkg, which was 3.2.15-1. After this, my Mac OS X system preserved modtimes when copying files to the NSLU2's share. Also, the touch -t command now succeeded. -- Jim DeLaHunt?, Vancouver, Canada, December 2009.

Testimonials

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

Configuring optional features

SWAT (Samba Web Administration Tool)

See the separate SWAT page.

Next, you will need to edit the smb.conf file so it will work with samba 3.0. The Samba project has a smb.conf man page which explains each of the parameters in detail. It is a useful reference to have while working on the configuration.

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

See the smb.conf man page on bind interfaces only for details.

	bind interfaces only = Yes

bind interfaces only = Yes

Further, it seems you MUST have "bind interfaces only = yes" in smb.conf, or else nmbd chokes. You can see the problem by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces only" line.

See [http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#id2535761|the smb.conf man page on bind interfaces only] for details.

No diversion script is required. However, you lose the ability to modify the configuration via the Linksys web interface. In the future, modify the Samba configuration either by directly editing /opt/etc/samba/smb.conf or via the SWAT web interface.

Another second example smb.conf file generated using the SWAT utility.

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

After upgrading to Samba 3, files created by user A (from a Linux client which mounted the Samba shares via CIFS) suddenly were not writable by user B, even though the configured share permissions gave write access to both users, and this worked flawlessly with Samba 2. This was caused by the following:

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions (when mounting as cifs, not smbfs). To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2.

unix extensions = no =]

Configuring optional features

SWAT (Samba Web Administration Tool)

See the separate SWAT page.

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients

 [=

unix charset = UTF-8 display charset = UTF-8 dos charset = 866

See SWAT.

smb.conf modifications for Samba 3

Starting Samba

Troubleshooting installation and configuration

interfaces configuration (Dec 2008, od3-ripe)

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo =]

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

interfaces configuration (Samba 3.2, July 2008)

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

 [=

interfaces = 192.168.1.77/24, ixp0, lo

bind interfaces

Further, it seems you MUST have "bind interfaces = ixp0" or else nmbd chokes. You can see it by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces" line.

Unable to connect in Samba 3.2.1-1 (9/27/08)

After struggling for days on end to get Samba running in Unslung 6.10 with an NTFS disk on Disk 1, I ran across this: http://www.nabble.com/Can%27t-Get-Upgrade-to-Samba-3.2.x-Working-td19361476.html

Basically, ran "ipkg install gconv-modules" and now my shares are working.

SWAT web config tool

See Optware/SWAT .

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

ipkg install samba3-swat =]

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

  [=

1. !/bin/sh
2. Diversion script: /unslung/rc.xinetd
3. Customize for your own use, do not delete your original content!

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then

  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf

fi

return 1

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

Configuring optional features

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

File size >= 2G and remote smbfs mount

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions (when mounting as cifs, not smbfs). To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2.

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

After upgrading to Samba 3, files created by user A (from a Linux client which mounted the Samba shares via CIFS) suddenly were not writable by user B, even though the configured share permissions gave write access to both users, and this worked flawlessly with Samba 2. This was caused by the following:

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions. To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2.

unix extensions = no

Notes for Samba 3.2

interfaces configuration (July 2008)

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
interfaces = 192.168.1.77/24, ixp0, lo
 

(:tableend:)

Notes for Samba 3

interfaces configuration (Dec 2008, od3-ripe)

International character support or Unicode support

File size >= 2G and remote smbfs mount

Notes for Samba 3.2

interfaces configuration (July 2008)

bind interfaces

Unable to connect in Samba 3.2.1-1 (9/27/08)

Samba configuration (smb.conf, smbpasswd)

If you've done the copying of the Samba 2 configuration to the new Samba 3 directory, you will find that /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/. After each reboot, the smb.conf and smbpasswd files in /share/hdd/conf/share/ are overwritten; files residing directly in /opt/etc/samba/ are not.

Samba 3 will read its configuration from /opt/etc/samba/, but the Linksys web interface will modify the Samba configuration in /share/hdd/conf/share/. This leaves the following options:

Option A: Remove the symlinks.

No diversion script is required. However, you lose the ability to modify the configuration via the Linksys web interface. In the future, modify the Samba configuration either by directly editing /opt/etc/samba/smb.conf or via the SWAT web interface.

To remove the symlinks, execute the following commands:

  
cd /opt/etc/samba
rm smb.conf
rm smbpasswd
cp /share/hdd/conf/share/smb.conf .
cp /share/hdd/conf/share/smbpasswd .
 

(:tableend:)

then update the /opt/etc/samba/smb.conf for Samba 3 as shown in the next section.

Option B: Diversion script.

When rebooting the system the symlinked smb.conf and smbpasswd will be overwritten with the original Samba 2 version. To keep the Samba 3 files, you need a copy of them in a location where they will not be touched. The best spot for this is /unslung/

First, copy the original files to /unslung/: (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

  
cp /share/hdd/conf/share/smb.conf /unslung/
cp /share/hdd/conf/share/smbpasswd /unslung/
 

(:tableend:)

You will need to remove the link to the old file and point to the new file with a diversion script.

rc.samba (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

1. !/bin/sh

ln -sf /unslung/smb.conf /opt/etc/samba/smb.conf ln -sf /unslung/smb.conf /etc/samba/smb.conf ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd ln -sf /unslung/smbpasswd /etc/samba/smbpasswd return 1 =] (:tableend:)

This should allow you to fully use the Linksys web interface, keep both file locations intact and not have to start the v2 server before starting the v3.

Modifications for Samba 3

Next, you will need to edit the smb.conf file so it will work with samba 3.0.

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

 An example smb.conf file that works is:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=

Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1.

(:tableend:)

SWAT web config tool

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

ipkg install samba3-swat

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

  [=

1. Diversion script: /unslung/rc.xinetd
2. Customize for your own use, do not delete your original content!

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then

  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf

fi

=]

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

... Samba 3.2 ...

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

 [=

interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

Dec 2008 (od3-ripe)

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients

unix charset = UTF-8 display charset = UTF-8 dos charset = 866 =]

I use these settings for support of Norwegian and Portugeese characters in filenames under Unslung 6.8 (samba 3): unix charset = UTF-8 dos charset = CP850 display charset = ISO-8859-1 I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

File size >= 2G and remote smbfs mount

When mounting smbfs the default does not include large file support, which limits files to less than 2 gigs. Using the lfs option will include large file support. Google "smbfs lfs option", since it seems to be missing from most documentation.

A better option is to use cifs, if it's supported by your kernel/distribution/version. When mounting cifs, large files are supported by default.

So either : mount -t smbfs //server/share /mountpoint -o lfs other-options or mount -t cifs //server/share /mountpoint -o options

Samba 3.2.0

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

interfaces = 192.168.1.77/24, ixp0, lo =]

July 2008

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

 
ipkg install samba3-swat

(:tableend:)

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

=]

Finally, edit /opt/etc/init.d/S08samba to activate Samba:

1. set samba_active=1 to activate samba

samba_active=1

[ 1 = $samba_active ] || exit 0 ...

• You have unslung to the first disk drive (sda1) or to a flash drive in port 2 (sda2)

cp -pR /etc/samba /opt/etc

... Samba 3.2 ...

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

Dec 2008 (od3-ripe)

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

... Samba 3.2 ...

Further, it seems you MUST have "bind interfaces = ixp0" or else nmbd chokes. You can see it by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces" line.

[On Unslung the command should be cp -pR /etc/samba /opt/etc]

After struggling for days on end to get Samba running in Unslung 6.10 with an NTFS disk on Disk 1, I ran across this:

Unable to connect in Samba 3.2.1-1 (9/27/08)

After struggling for days on end to get Samba running in Unslung 6.10, I ran across this: http://www.nabble.com/Can%27t-Get-Upgrade-to-Samba-3.2.x-Working-td19361476.html

Basically, ran "ipkg install gconv-modules" and now my shares are working.

cp -pR /etc/samba /opt/etc/samba

I recommend using the below conf file, change your workgroup name, the interface IP to your NSLU2 IP, hosts allow to your client IP range, don't use the Admin1 or Disk1 sections here. Instead copy only those 2 sections out of your old version 2 smb.conf file. If you do this, you should see the same shares behavior out of your Samba 3 install as you saw from Samba 2

For non-unslung firmware, like openwrt, you need to change guest account = nobody and force group = nogroup.

The file is configured with three accessible shares. 1. A users 'home' folder, 2. a 'public' folder which can be accessed by any connecting client using netbios, and 3. 'read only' access to the full NSLU-2 directory structure.

A users 'home' folder and read only access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (for security they are non browseable).

Mapping example using the NSLU-2 netbios name - \\netbios_name_goes_here\ADMIN 1

Notes - for Debain firmware, change the interfaces line to interfaces = eth0, lo

A users 'home' folder and 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (for security they are non browseable).

Notes - for Debain firmware change the interfaces line to interfaces = eth0, lo

For non-unslung firmware, like openwrt, you need to change guest account = nobody and force group = nobody.

The directory /opt/var/spool/samba may need to be created and flagged chmod 755 (there may be other Samba working directories missing).

	comment = Users Home Directories

	comment = Print Spooler Directory

The file is configured with three accessible shares. A users 'home' folder, a 'public' folder which can be accessed by any connecting client using netbios, and 'read only' access to the full NSLU-2 directory structure.

The file configures Samba in 'User' mode. In this mode, a users 'home' folder is only accessible if the 'user name' and 'password' are identical on both the server and client.

A users 'home' folder and 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (they are non browseable for security).

Mapping example using the NSLU-2 netbios name - \\netbios_name-goes_here\ADMIN 1

Mapping example using the NSLU-2 IP address - \\192.168.1.77\user_name_goes_here

Also note - for non-unslung firmware, like openwrt, you need to change 'guest account = nobody' and 'force group = nobody'.

Note the directory /opt/var/spool/samba may need to be created and flagged chmod 755.

The file is configured with three accessible shares. A users home folder. A public folder which can be accessed by any connection using netbios. And read only access to the full NSLU-2 directory structure

The file configures Samba in 'User' mode. In this mode, a users home folder is only accessible if the user name and password are identical on both the server and client.

A users home folder and also 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (they are non browsable).

Mapping example using the NSLU-2 netbios name \\netbios_name-goes_here\ADMIN 1

Another example using the NSLU-2 IP address \\192.168.1.77\user_name_goes_here

The file configures Samba in 'User' mode. In this mode, a users home folder is only accessible by a named user if the user name and password are identical on both the server and client. Incorrect user names or passwords will only have access to the public folder tree. A users home folder and also 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client - examples \\NSLU2\ADMIN 1 - \\192.168.1.77\user_name_goes_here

	path = /public

	browseable = No

	force group = everyone

	browseable = No

	read only = No

        security = USER

	path = /%S

	path = /%u

	invalid users = root

Optimised for Unslung firmware (added by RobHam Sept 2007 + Mod Sept 2008).

1. from 192.168.1.50 (192.168.1.50)
2. Date: 2008/09/10 21:01:20

        security = SHARE
	map to guest = Bad Password

[homes]

	comment = Home Directories
	valid users = %S
	create mask = 0700
	directory mask = 0700
	browseable = No

[printers]

	comment = All Printers
	path = /opt/var/spool/samba
	create mask = 0700
	printable = Yes
	browseable = No

	server string = %h Server

	hosts allow = 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8, localhost

July 2008

	interfaces = 192.168.1.77/24, ixp0, lo

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

Note that some users have reported seeing messages in the Samba error logs similar to 'Unable to open printcap file /opt/etc/printcap for read'. This is probably because Samba is trying to open a nonexistant file. Easily fixed by logging in as user 'root' at a console screen and then check if the file exists. If not, create a blank file using the two commands:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
touch /opt/etc/printcap
chmod 0644 /opt/etc/printcap

(:tableend:)

mount -t cifs //server/share /mountpoint -o options

Samba 3.2.0

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
interfaces = 192.168.1.77/24, ixp0, lo
 

(:tableend:)

RobHam July 2008

I found that using one charset for unix and another for display messes things up. If you access the same files from windows as you publish e.g. on your web server, they look differently. I now use ISO-8859-1 for unix charset as well as display charset. Works fine for danish characters.

Also note - for non-unslung firmware, like openwrt, you need to change guest account=nobody from guest

	path = /

	path = /public/

Another second example smb.conf file generated using the Swat utility. Optimised for Unslung firmware (added by RobHam Sept 2007).

Note - for Debain firmware change the interfaces line to interfaces = eth0, lo

 Another second example smb.conf file generated using the Swat utility.

Optimised for Unslung firmware (added by RobHam? Sept 2007).

 Another example smb.conf file generated using the Swat utility,  optimised for Unslung firmware (added by RobHam? Sept 2007).

1. Samba config file created using SWAT
2. from 192.168.2.50 (192.168.2.50)
3. Date: 2007/09/25 20:35:19

[global]

	workgroup = MSHOME
	server string = Samba %v Network Drive
	interfaces = ixp0, lo
	bind interfaces only = Yes
	map to guest = Bad User
	null passwords = Yes
	guest account = guest
	log file = /opt/var/samba/log.%m
	max log size = 10
	name resolve order = wins bcast
	socket options = SO_SNDBUF=8192 SO_RCVBUF=8192
	load printers = No
	printcap name = /opt/etc/printcap
	dns proxy = No
	ldap ssl = no
	config file = /opt/etc/samba/smb.conf
	lock directory = /var/samba3
	pid directory = /var/samba3
	create mask = 0771
	force create mode = 0660
	force directory mode = 0771
	hosts allow = 192.168., 172., 10., localhost

[ADMIN 1]

	comment = Full Data Partition
	path = /share/hdd/data/
	valid users = @administrators
	write list = @administrators

[DISK 1]

	comment = Public Folder Tree For Everyone
	path = /share/hdd/data/public/
	valid users = @administrators, @everyone
	write list = @administrators, @everyone
	read only = No
	guest ok = Yes

=] (:tableend:)

Finally, edit /opt/etc/init.d/S08samba, remove comments:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=

I use UTF-8 showing file's name in Chinese and it works fine until today. After I did the "ipkg upgrade" my samba become version 3.0.25b-1. All the shares are works but it can not show Chinese char! I checked smb.conf and it was the same as before(i.e. unix charset = UTF-8

<added on Aug 17 2007>

I use UTF-8 showing file's name in Chinese and it works fine until today. After I did the "ipke upgrade" my samba become version 3.0.25b-1. All the shares are works but it can not show Chinese char! I checked smb.conf and it was the same as before(i.e. unix charset = UTF-8 display charset = UTF-8 dos charset = UTF-8)

Alternate update method 3

I created the smb.conf file in /opt/etc/samba and started the slug. There was no need for a diversion script. Running Unslung 6.8 and samba 3.0.25a

return 1

unix charset = UTF-8 display charset = UTF-8

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

unix charset = UTF-8 display charset = UTF-8

unix charset = UTF-8 dos charset = CP850 display charset = ISO-8859-1

Finally, edit /opt/etc/init.d/S08samba, remove comments:

echo "Starting nmbd:"

 /opt/sbin/nmbd -D --configfile=/opt/etc/samba/smb.conf;

./S08samba

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0.

If you're new to Linux editors, the vi editor which comes standard with UnSlung? is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

I use these settings for support of Norwegian and Portugeese characters in filenames under Unslung 6.8 (samba 3):

I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

I use these settings for support of Norwegian and Portugeese characters in filenames: unix charset = UTF-8 dos charset = CP850? display charset = ISO-8859-1

I wanted support for the Norwegian ø/Ø and Portugese characters under Unslung 6.8 (samba 3). So I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

Installing Samba >=3.0.14a-4 on Unslung 4.2x beta or later

File size >= 2G and remote smbfs mount

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

--- When mounting smbfs the default does not include large file support, which limits files to less than 2 gigs. Using the lfs option will include large file support. Google "smbfs lfs option", since it seems to be missing from most documentation.

A better option is to use cifs, if it's supported by your kernel/distribution/version. When mounting cifs, large files are supported by default.

So either : mount -t smbfs //server/share /mountpoint -o lfs other-options or mount -t cifs //server/share /mountpoint -o options

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. If you're new to Linux editors the vi editor comes standard with UnSlung?; google "vi" to learn the basics.

Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2 - being a non-*nix user I found vi to be extremely unfriendly and a steep learning curve for a "one off job".

 An example smb.conf file that works is:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S80samba. Then restart. That's all.

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. If you're new to Linux editors the vi editor comes standard with UnSlung?; google "vi" to learn the basics. An example smb.conf file that works is:

If all goes well, the stock samba will stop and your new samba will start. Don't be suprised if running a "ps" shows two smbd & nmbd tasks, compared to one each previously. This is normal.

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S80samba. That's all.

Diversion script

You will find that the smb.conf file does stick and revert to orginal during a turn off/turn on...

username map =

 /opt/sbin/smbd -D --configfile=/opt/etc/samba/smb.conf;

 /opt/sbin/nmbd -D --configfile=/opt/etc/samba/smb.conf;

No script is required (that's why I think it's easier than writing a diversion script). Just type the following commands :

Diversion sript

You will find that the smb.conf file does stick and revert to orginal during a turn off/turn on...

Alternate update method 2

Alternate and simplier method

After each reboot, the smb.conf and smbpasswd files in /opt/etc/samba directory are overwritten. Having a look closer, you can see that :

• /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/
• links in /opt/etc/samba/ are never overwritten
• only files in /share/hdd/conf/share/ are overwritten at each boot

That's why I used the following commands that brought me satisfaction :

  
cd /opt/etc/samba
rm smb.conf
rm smbpasswd
cp /share/hdd/conf/share/smb.conf .
cp /share/hdd/conf/share/smbpasswd .
 

and then only I update the /opt/etc/samba/smb.cong file as shown below.

Be aware of ipkg upgrade of samba package to 3.0.14a-5. It may break your existing samba configuration and make files unsharable.

Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1.

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script

Please note that on OpenSlug, the log file is on /var/log/log.smbd.

(rc.samba): (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd
ln -sf /unslung/smbpasswd /etc/samba/smbpasswd

(:tableend:)

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

That's why I used the following commands that brought me satisfaction :

and then only I update the /opt/etc/samba/smb.cong file as shown below.

Alternate and simplier method

After each reboot, the smb.conf and smbpasswd files in /opt/etc/samba directory are overwritten. Having a look closer, you can see that :

• /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/
• links in /opt/etc/samba/ are never overwritten
• only files in /share/hdd/conf/share/ are overwritten at each boot

That's why I used the following commands thqt brought satisfaction : (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
cd /opt/etc/samba
rm smb.conf
rm smbpasswd
cp /share/hdd/conf/share/smb.conf .
cp /share/hdd/conf/share/smbpasswd .

and then only I update the /opt/etc/samba/smb.cong file as shown below. (:tableend:)

• You have installed unslung 4.20 or later
• You have unslung to the first disk drive (sda1)
• You have your user permissions set up for drive access working in the Linksys web interface
• Your ipkg is current (ipkg update)

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
ipkg install samba

(:tableend:)

cp -pR /etc/samba /opt/etc =] (:tableend:)

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. An example smb.conf file that works is:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
cd /opt/etc/init.d
./S80samba

(:tableend:)

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=

=] (:tableend:)

If you want to enable SWAT, the Samba web config tool included in the package, you should edit your rc.xinetd diversion script. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

Once that is done just point your browser to <slug IP Address>:901, and enjoy. More info on SAMBA 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! A normal user only get the buutons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

(On OpenSlug, you need to use /etc/init.d/samba restart)

Please note that on OpenSlug, the log file is on /var/log/log.smbd.

hosts deny = 0.0.0.0/0

Installing Samba 3.0.14a-4 on Unslung 4.2x beta or later

• you have installed unslung 4.20 or later

(:tableend:)

SAMBA web config tool

If you want to enable SWAT, the SAMBA web config tool included in the package, you should edit your rc.xinetd diversion script. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in dissabled services, which for example could dissable your telnet access.

If you add the following content, SWAT should work out off the box:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

  
#!/bin/sh
# Diversion script: /unslung/rc.xinetd
# Customize for your own use, do not delete your original content!
#

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then
  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf
fi

return 1
 

(:tableend:)

Once that is done just point your browser to <slug IP Address>:901, and enjoy. More info on SAMBA 3 (inclusing SWAT) can be found on the web at: us3.samba.org/samba/docs/man/

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script

Please note that on OpenSlug, the log file is on /var/log.smbd.

(rc.samba):

(Please note that on OpenSlug, the config file must be on /usr/lib/smb.conf)

Update: Thanks to Inge Bjørnvall Arnesen
Reference links: AddPrinter EnableWinsServer
If you find that the smb.conf file does stick and revert to orginal during a turn off/turn on... You have to set a diversion script in /unslung Create a file rc.samba to include the below

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=

This should allow you to fully use the web interface, keep both file locations intact and not have to start the v2 server before starting the v3.

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script (rc.samba): (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd
ln -sf /unslung/smbpasswd /etc/samba/smbpasswd

(:tableend:)

samba configuration and make files unsharable.

Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1.

Alternate Update Method

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 

When rebooting the system the file smb.conf will be overwritten with the original samba 2 version. 
To keep the version 3 file, you need a copy of it in a location where it will not be touched. The best spot for this is /unslung
Once you have created your smb.conf, you will need to remove the link to the old file and and point to the new file with a diversion script.

rc.samba

#!/bin/sh
ln -sf /unslung/smb.conf /opt/etc/samba/smb.conf
ln -sf /unslung/smb.conf /etc/samba/smb.conf
return 0

This should allow you to fully use the web interface, keep both file locations intact and not have to start the v2 server before starting the v3.

(:tableend:)

(:tableend:)

Be aware of ipkg upgrade of samba package to 3.0.14a-5. It may break your existing samba configuration and make files unsharable.

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#update. Thanks to Inge Bjørnvall Arnesen
Reference links 
http://www.nslu2-linux.org/wiki/HowTo/AddPrinter
http://www.nslu2-linux.org/wiki/HowTo/EnableWinsServer
If you find that the smb.conf file does stick and revert to orginal during a turn off/turn on...
You have to set a diversion script in /unslung  Create a file rc.samba to include the below

#! /bin/sh
# Diversion script: customize before starting crond
#
#

# Make sure we have a backup copy of /etc/samba/smb.conf
if [ ! -e /etc/samba/smb.conf.orig ]; then 
  cp -p /etc/samba/smb.conf  /etc/samba/smb.conf.orig 
fi

return 1

(:tableend:)

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
# sample samba 3.0 conf file
[global]
log level = 1

# CHANGE these settings to match your network/workgroup setup
# ------------------
workgroup = WORKGROUP
server string = NSLU Network Drive
netbios name = usbdrive
# your wins server ip address
wins server = 10.0.0.1
# the networks you want to allow connections from
hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2.
# ------------------

config file=/opt/etc/samba/smb.conf
os level = 8
load printers = no
max log size = 10
security = user
encrypt passwords = yes
smb passwd file = /opt/etc/samba/smbpasswd
socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 SO_RCVBUF=16384
preferred master = no
local master = yes
dns proxy = no 
preserve case = yes
short preserve case = yes
default case = upper
case sensitive = no
mangled names = yes 
null passwords = yes
username map = no
dos filetimes = yes
force directory mode=771
force create mode=660
create mask=771
map system=yes
map to guest=Bad User
guest account=guest
guest ok = yes
bind interfaces only = yes
interfaces = ixp0 lo
winbind use default domain = no

[ADMIN 1]
valid users=@"administrators"
comment=
path=/share/hdd/data/
read only=yes
write list=@"administrators"
[DISK 1]
valid users=@"administrators",@"everyone",@"linux"
comment=For everyone
path=/share/hdd/data/public/
browseable = yes
read only=yes
write list=@"administrators",@"everyone",@"linux"

(:tableend:)

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#!/bin/sh

# please remove '#' to activate the start script.

if [ -n "`pidof smbd`" ] ; then
   echo "Stopping smbd:"
   killall smbd
fi

if [ -n "`pidof nmbd`" ] ; then
   echo "Stopping nmbd:"
   killall nmbd
fi

sleep 2

echo "Starting smbd:"
 /opt/sbin/smbd -D;
echo "Starting nmbd:"
 /opt/sbin/nmbd -D;

(:tableend:)

 cp -pR /etc/samba /opt/etc

Installing Samba 3.0.14a-4 on Unslung 4.2x beta

Assumptions for these instructions

• you have installed unslung 4.20
• you are unslung to the first disk drive (sda1)
• you have your user permissions set up for drive access working in the linksys web interface
• your ipkg is current (ipkg update)

I've not tested any of this on pre 4.2 releases.

Install

 ipkg install samba

Post-install setup

First, copy the default samba config files over to the new samba directory:

 cp -pR /etc/samba /opt/etc/samba

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. An example smb.conf file that works is:

 # sample samba 3.0 conf file
 [global]
 log level = 1

 # CHANGE these settings to match your network/workgroup setup
 # ------------------
 workgroup = WORKGROUP
 server string = NSLU Network Drive
 netbios name = usbdrive
 # your wins server ip address
 wins server = 10.0.0.1
 # the networks you want to allow connections from
 hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2.
 # ------------------

 config file=/opt/etc/samba/smb.conf
 os level = 8
 load printers = no
 max log size = 10
 security = user
 encrypt passwords = yes
 smb passwd file = /opt/etc/samba/smbpasswd
 socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 SO_RCVBUF=16384
 preferred master = no
 local master = yes
 dns proxy = no 
 preserve case = yes
 short preserve case = yes
 default case = upper
 case sensitive = no
 mangled names = yes 
 null passwords = yes
 username map = no
 dos filetimes = yes
 force directory mode=771
 force create mode=660
 create mask=771
 map system=yes
 map to guest=Bad User
 guest account=guest
 guest ok = yes
 bind interfaces only = yes
 interfaces = ixp0 lo
 winbind use default domain = no

 [ADMIN 1]
 valid users=@"administrators"
 comment=
 path=/share/hdd/data/
 read only=yes
 write list=@"administrators"
 [DISK 1]
 valid users=@"administrators",@"everyone",@"linux"
 comment=For everyone
 path=/share/hdd/data/public/
 browseable = yes
 read only=yes
 write list=@"administrators",@"everyone",@"linux"

Finally, edit /opt/etc/init.d/S80samba, remove comments:

 #!/bin/sh

 # please remove '#' to activate the start script.

 if [ -n "`pidof smbd`" ] ; then
    echo "Stopping smbd:"
    killall smbd
 fi

 if [ -n "`pidof nmbd`" ] ; then
    echo "Stopping nmbd:"
    killall nmbd
 fi

 sleep 2

 echo "Starting smbd:"
  /opt/sbin/smbd -D;
 echo "Starting nmbd:"
  /opt/sbin/nmbd -D;

Now you are ready to restart

 cd /opt/etc/init.d
 ./S80samba

If all goes well, the stock samba will stop and your new samba will start.

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.