[ET10x00] box invisible on network

[ccs]

Here we go (9 months self isolating does strange things to you) ....

/etc/samba after a clean install of 5.4.003, 68 packages installed with samba or smb in the name (samba not yet installed) ....

root@et10000:~# ls -lR /etc/samba
/etc/samba:
drwxr-xr-x    2 root     root           528 Nov 11 12:24 distro
-rw-r--r--    1 root     root            20 Oct  8 05:12 lmhosts
drwxr-xr-x    2 root     root           376 Dec 29 15:12 private
-rw-r--r--    1 root     root           744 Oct  8 05:12 smb-user.conf
-rw-r--r--    1 root     root            95 Oct  8 05:12 smb.conf

/etc/samba/distro:
-rw-r--r--    1 root     root            61 Oct  8 05:12 smb-branding.conf
-rw-r--r--    1 root     root          1457 Oct  8 05:12 smb-global.conf
-rw-r--r--    1 root     root           586 Oct  8 05:12 smb-shares.conf
lrwxrwxrwx    1 root     root            13 Nov 11 12:24 smb-vmc.conf -> smb-vmc.samba
-rw-r--r--    1 root     root            29 Oct  8 05:12 smb-vmc.samba

/etc/samba/private:
-rw-------    1 root     root        430080 Dec 29 15:12 secrets.tdb
-rw-------    1 root     root           204 Dec 29 15:13 smbpasswd
-rw-r--r--    1 root     root            80 Oct  8 05:12 users.maps

After installing samba, 81 packages now installed (the same as a "working" samba), but /etc/samba has not changed and in particular, nmbd isn't running.

This is what "works" (quite different to the above) and is the same on an et10k and ultimo4k....

root@et10000:/tmp/etc# ls -lR samba
samba:
drwxr-xr-x    2 root     root           180 Dec 29 14:38 distro
-rw-r--r--    1 root     root            20 Jan 27  2018 lmhosts
drwxr-xr-x    2 root     root           120 Dec 29 14:38 private
-rw-r--r--    1 root     root           744 Jan 27  2018 smb-user.conf
-rw-r--r--    1 root     root            95 Jan 27  2018 smb.conf

samba/distro:
[COLOR="#FF0000"]-rw-r--r--    1 root     root           168 Jan 27  2018 smb-branding.conf
-rw-r--r--    1 root     root          1189 Jan 27  2018 smb-global.conf
-rw-r--r--    1 root     root           253 Jan 27  2018 smb-insecure.conf    (additional file)
-rw-r--r--    1 root     root           615 Jan 27  2018 smb-secure.conf      (additional file)[/COLOR]
-rw-r--r--    1 root     root           586 Jan 27  2018 smb-shares.conf
lrwxrwxrwx    1 root     root            13 Dec 29 14:38 smb-vmc.conf -> smb-vmc.samba
-rw-r--r--    1 root     root            29 Jan 27  2018 smb-vmc.samba

samba/private:
-rw-------    1 root     root        430080 Mar 20  2018 secrets.tdb
-rw-------    1 root     root           204 Oct 13 09:40 smbpasswd
-rw-r--r--    1 root     root            28 Oct 26  2019 users-insecure.map
-rw-r--r--    1 root     root            80 Jan 27  2018 users.map

Something updated the above many years(2018?) ago but what is anybody's guess.

 

[BrokenUnusableAccount]

@ccs
Hang on, the first listing is /etc/samba while the second seems to be /tmp/etc/samba which doesn't even seem to exist on my Zgemma H7.

 

[ccs]

@ccs
Hang on, the first listing is /etc/samba while the second seems to be /tmp/etc/samba which doesn't even seem to exist on my Zgemma H7.

I unpacked a settings backup of the et10k into /tmp to get hold of the "working" /etc/samba, just saved a bit of time. Just testing.

 

[ccs]

Another day, another idea. I wondered how I could possibly have got my ultimo4k working for the first time back in March.

The first image was 5.3.019, so I flashed it onto the et10k, no restores.

Gasp, /etc/samba is the "working" version (date stamps are a bit different from before because of my settings restores over the years) ....

root@vuultimo4k:~# ls -lR /etc/samba
/etc/samba:
drwxr-xr-x    2 root     root          4096 Dec 30 10:40 distro
-rw-r--r--    1 root     root            20 Oct 26  2019 lmhosts
drwxr-xr-x    2 root     root          4096 Dec 30 10:40 private
-rw-r--r--    1 root     root           744 Oct 26  2019 smb-user.conf
-rw-r--r--    1 root     root            95 Oct 26  2019 smb.conf

/etc/samba/distro:
-rw-r--r--    1 root     root           168 Oct 26  2019 smb-branding.conf
-rw-r--r--    1 root     root          1177 Oct 26  2019 smb-global.conf
-rw-r--r--    1 root     root           386 Oct 26  2019 smb-insecure.conf
-rw-r--r--    1 root     root           787 Oct 26  2019 smb-secure.conf
-rw-r--r--    1 root     root           586 Oct 26  2019 smb-shares.conf
lrwxrwxrwx    1 root     root            13 Dec 30 10:40 smb-vmc.conf -> smb-vmc.samba
-rw-r--r--    1 root     root            29 Oct 26  2019 smb-vmc.samba

/etc/samba/private:
-rw-------    1 root     root           204 Dec 30 10:43 smbpasswd
-rw-r--r--    1 root     root            28 Oct 26  2019 users-insecure.map
-rw-r--r--    1 root     root            80 Oct 26  2019 users.map
root@vuultimo4k:~#

What is really odd, everything I'd expect to be running after installing samba is already running, so all boxes see each other (and themselves).....

root@et10000:~# ps -AFH | grep -e "[sn]mbd\|wsd\d"
root       701     1  0  9519  8684   1 11:18 ?        00:00:00   /usr/sbin/smbd
root       705   701  0  8817  4144   1 11:18 ?        00:00:00     /usr/sbin/smbd
root       706   701  0  8815  3888   1 11:18 ?        00:00:00     /usr/sbin/smbd
[COLOR="#FF0000"]root       709     1  0  6237  3884   1 11:18 ?        00:00:00   /usr/sbin/nmbd[/COLOR]
root       718     1  0   498  1028   1 11:18 ?        00:00:00   /usr/sbin/wsdd
root@et10000:~#

Installing Utilities/Samba comes up with the green "running" box for an instant, followed by the invite to install packagegroup-base-smbfs-server.

That installs ok, but still needs an opkg update first.

So, Samba has changed since March, and affects both the et10k and ultimo4k (and probably everything else).

 

[ccs]

If I stop /etc/samba/distro/smb-insecure.conf from running by using the "non-working" version of smb-branding.conf thus...

root@et10000:/etc/samba/distro# [COLOR="#0000CD"]cat smb-branding.conf[/COLOR]
[global]
        server string = OpenViX %h network services

root@et10000:/etc/samba/distro# [COLOR="#0000CD"]cat smb-branding.conf.orig[/COLOR]
[global]
        server string = OpenViX %h network services

#       include = /etc/samba/distro/smb-secure.conf
        include = /etc/samba/distro/smb-insecure.conf

root@et10000:/etc/samba/distro#

I end up with these still running....

root@et10000:~# ps -AFH | grep -e "[sn]mbd\|wsd\d"
root       613     1  0  6235  3640   0 12:38 ?        00:00:00   /usr/sbin/nmbd
root       620     1  0   498  1016   0 12:38 ?        00:00:00   /usr/sbin/wsdd
root@et10000:~#

Not quite what I expected, as nmbd not running is part of the original problem.

 

[ccs]

Back to 5.4.003, before installing Samba,

root@et10000:~# ps -AFH | grep -e "[sn]mbd\|wsd\d"

finds nothing, which is what you'd expect, unlike 5.3.019 (post #64) which had everything running.

Commenting out the line "disable netbios = Yes" from /etc/samba/distro/smb-global.conf and installing Samba produces....

root@et10000:~# ps -AFH | grep -e "[sn]mbd\|wsd\d"
root       602     1  0  7933  7832   1 13:15 ?        00:00:00   /usr/sbin/smbd
root       606   602  0  7293  2872   0 13:15 ?        00:00:00     /usr/sbin/smbd
root       607   602  0  7291  2504   1 13:15 ?        00:00:00     /usr/sbin/smbd
root       609     1  0  4794  2888   1 13:15 ?        00:00:00   /usr/sbin/nmbd
root       617     1  0   499  1004   0 13:15 ?        00:00:00   /usr/sbin/wsdd
root@et10000:~#

which, I think, is what's wanted, with every box seeing what you'd expect.

 

[ccs]

I can find references to smb-global.conf on github, before netbios was disabled...

https://github.com/oe-alliance/oe-alliance-core/blob/e1a528415e6e243a2a6e9af17edc211b3b859b48/meta-oe/recipes-connectivity/samba/samba-3.6.25/smb-global.conf

and after

https://github.com/oe-alliance/oe-alliance-core/blob/4.4/meta-oe/recipes-connectivity/samba/samba/smb-global.conf

but no history, probably because of Samba version changes.

There are also references to the secure.conf and insecure.conf files here...

https://github.com/oe-alliance/oe-alliance-core/tree/e1a528415e6e243a2a6e9af17edc211b3b859b48/meta-oe/recipes-connectivity/samba/samba-3.6.25

 

[ccs]

Samba uses the directory /etc/samba to store its configuration files.
This directory comes as part of Vix, whether you use Samba or not.

My current version of Vix (5.4.003) is ok because I've had a working version for a number of years, and a settings restore overwrites
everything in /etc/samba. There is a fundamental problem here, because a new version of Samba was released a while ago, with
a new set of config files in /etc/samba. A system restore overwrites all these file, so I'm running the latest version of the samba packages
with an old set of config files.

Commenting out the line "disable netbios = Yes" from /etc/samba/distro/smb-global.conf works, but I guess is not the correct way to do it.
I'm assuming the file /etc/smb-user.conf should be edited instead, with the line "disable netbios = No", but I've not tried it yet.

 

[BrokenUnusableAccount]

Samba uses the directory /etc/samba to store its configuration files.
This directory comes as part of Vix, whether you use Samba or not.

My current version of Vix (5.4.003) is ok because I've had a working version for a number of years, and a settings restore overwrites
everything in /etc/samba. There is a fundamental problem here, because a new version of Samba was released a while ago, with
a new set of config files in /etc/samba. A system restore overwrites all these file, so I'm running the latest version of the samba packages
with an old set of config files.

I think that probably doesn't matter.
Samba just looks at /etc/samba/smb.conf and also at any files mentioned in include lines in that first file.

Commenting out the line "disable netbios = Yes" from /etc/samba/distro/smb-global.conf works, but I guess is not the correct way to do it.
I'm assuming the file /etc/smb-user.conf should be edited instead, with the line "disable netbios = No", but I've not tried it yet.

Just bear in mind that smb.conf seems to be divided into sections, and the disable netbios line needs to be in a [Global] section.

I'm wondering if two boxs that both have "disable netbios = Yes" would be able to see each other.

 

[ccs]

Just bear in mind that smb.conf seems to be divided into sections, and the disable netbios line needs to be in a [Global] section.

The file that needs changing is /etc/samba/smb-user.conf, not smb.conf

This one line change works (at last) using the /etc/samba directory which comes with 5.4.003, no settings restore in sight, and nmbd starts ...

## User changes to Samba config go here

## You can overrule the insecure defaults and enforce password
## protected access to shares by uncommenting the following
## line, including the secure settings:

[global]
#       include = /etc/samba/distro/smb-secure.conf
        [COLOR="#FF0000"]disable netbios = No[/COLOR]

## You can hide and veto access to certain directories, e.g. mount points of
## other boxes in order to prevent round trips through your LAN
## In Samba 4.x this needs to be configured per share:

[Root]
#       veto files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/
#       hide files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/

[Harddisk]
#       veto files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/
#       hide files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/

I'm wondering if two boxs that both have "disable netbios = Yes" would be able to see each other.

With netbos disabled, nmdb doesn't run, boxes can only see boxes that have it running.

 

[ccs]

I think that probably doesn't matter.
Samba just looks at /etc/samba/smb.conf and also at any files mentioned in include lines in that first file.

The contents of the include files it was looking at before were different, but, in practice, added up to being very similar to the latest samba directory.
Unfortunately, my uniq/sort/diff attempts struggled to produce a definitive list of exceptions, but there were some.

 

[ccs]

If you get the dreaded "/media/autofs/..... file does not exist" when selecting a remote location in movielist,
have a look in /etc/auto.network If you find 2 entries for the failing location, delete them both while enigma2 is stopped.
Restart and then use network manager to delete the location, and then network browser to re-create.

 

[ccs]

One last observation. If you remove the samba service via network/utilities/samba then smbd, nmbd and wsdd no longer run, which is what you'd expect.

However, '/etc/samba' is not removed from the entry "config.backupmanager.backupdirs=" in /etc/enigma2/settings.

So /etc/samba will be in settings backups for evermore.
.
This means that if you have an old version of /etc/samba (like I had), removing the samba service, taking a settings backup, reflashing a new image followed by a settings restore won't have the desired effect, the old one will come back.

( '/etc/samba' is not in the settings entry "config.backupmanager.backupdirs=" after a clean flash of a new release, it is put there after you install samba for the very first time.)

 

[ccs]

.... and for anyone who thinks they may have come up with a workaround (removing the /etc/samba reference in settings for example), think again, because backupmanager puts it back in again!

So it looks like /etc/samba is backed up even if you've never installed samba.

 

[cactikid]

But i have used an earlier image and setup from start and box is now seen,for the moment.

 

[ccs]

But i have used an earlier image and setup from start and box is now seen,for the moment.

Settings restores kind of fixed the problem by accident rather than design.

If you flashed an old image (you mentioned 2 years old a while ago) then it's very unlikely it needs "disable netbios = No" putting in smb-user.conf.

I reckon the new samba changes went in about 14 months ago.

 

[Joe_90]

The earlier images use an older version of samba which supports SMB1 and network browsing works fairly well and handles older windows shares (Win95/98/XP/NT/2000 etc). Win10 by default doesn't support SMB1, so the default now is SMB2 in most linux distros and network browsing doesn't work well. enigma builds now use SMB2 by default also. Most of my shares are on a linux mint (ubuntu derived) box which acts as a NAS. This too uses SMB2 by default. So I bit the bullet and set user and password on the various shares and access them by IP address/sharename and provide a userid and password in the mount manager in enigma and on my separate kodi box and it all works fine in the 5.4.nnn builds. It's all in the name of improved security, supposedly! There's no "one size fits all" option if you have a mixed MS Windows and linux network, particularly if you are running an older unsupported windows version (anything other than Win10). @SpaceRat is probably the best at describing the various scenarios and best settings, so if you search for posts by him you might get some good tips. I just gave up on browsing and access everything by IP address at this stage (but it can be done if you are prepared to keep configuring and maybe adopt the avahi method in an all linux environment). As @ccs has discovered, the samba config files are not being cleaned up properly when you remove samba from the system so that means you can end up with bits of old samba config and new samba executables. The older versions of samba had netbios enabled by default I think so that provided the network discovery, but that's a security issue also, so it's not the default now.