thr3ads.net - samba - [Samba] FreeBSD 12.3-RELEASE and Samba 4.13 [Apr 2022]

If this information is useful, please help other people find it:
Share via:

Rowland Penny

2022-Apr-16 21:18 UTC

[Samba] FreeBSD 12.3-RELEASE and Samba 4.13

On Sat, 2022-04-16 at 13:53 -0700, David Christensen via samba
wrote:> On 4/16/22 13:36, Rowland Penny via samba wrote:
> 
> > You are running a version of Samba that has SMBv1 turned off by
> > default
> > and you need SMBv1 for Network Browsing. Also wsdd is supposed to
> > replace Network Browsing, you use one or the other, not both.
> 
> Thanks for the reply.  :-)
> 
> 
> Is there a way that I can query nmbd and/or smbd to determine what 
> protocols, etc., are supported and/or enabled?
> 
> 
> AIUI SMBv1 is deprecated and in the process of becoming unsupported 
> everywhere.  But the last time I looked, SMBv2 seemed to involve
> domain 
> networking and/or Kerberos.  I know nothing about SMBv3.
> 
> 
> I would prefer Workgroup networking, or whatever is the current 
> equivalent.  I do not want to implement domain, etc., networking at
> this 
> time.
> 
> 
> I only discovered wsdd(1) yesterday, and have little experience with
> it.
> 
> 
> What is the current way to implement Workgroup networking (or 
> equivalent) on Samba 4.13?
Do you need SMBv1 ?

Or to put it another way, do you have any old computers that can only
use it ?

If you don't, then you have no need to run nmbd, just run smbd and use
wsdd to get Windows to show your Samba computers in Explorer and Avahi
to show your computers on Linux. Add 'disable netbios = yes' to
smb.conf and remove all references to wins.

Rowland

David Christensen

2022-Apr-17 06:16 UTC

head link

[Samba] FreeBSD 12.3-RELEASE and Samba 4.13

On 4/16/22 14:18, Rowland Penny via samba wrote:
> Do you need SMBv1 ?
> 
> Or to put it another way, do you have any old computers that can only
> use it ?

I am unsure if I need SMBv1.  I can disable it and see if any clients break.

> If you don't, then you have no need to run nmbd, just run smbd and use
> wsdd to get Windows to show your Samba computers in Explorer and Avahi
> to show your computers on Linux. Add 'disable netbios = yes' to
> smb.conf and remove all references to wins.

2022-04-16 22:54:31 toor at samba ~
# samba-tool testparm
INFO 2022-04-16 22:55:56,866 pid:14793 
/usr/local/lib/python3.8/site-packages/samba/netcmd/testparm.py #96: 
Loaded smb config files from /usr/local/etc/smb4.conf
INFO 2022-04-16 22:55:56,866 pid:14793 
/usr/local/lib/python3.8/site-packages/samba/netcmd/testparm.py #97: 
Loaded services file OK.
Press enter to see a dump of your service definitions

# Global parameters
[global]
	disable netbios = Yes
	local master = Yes
	passdb backend = tdbsam
	preferred master = Yes
	security = USER
	server string = Samba Server Version %v
	workgroup = WORKGROUP

[dpchrist]
	path = /var/local/samba/dpchrist
	read only = No
	valid users = dpchrist

2022-04-16 22:55:58 toor at samba ~
# service samba_server restart
Performing sanity check on Samba configuration: OK
Stopping smbd.
Waiting for PIDS: 10332, 10332.
Stopping nmbd.
Waiting for PIDS: 10325.
Performing sanity check on Samba configuration: OK
Starting nmbd.
Starting smbd.

2022-04-16 22:56:27 toor at samba ~
# service wsdd start
Starting wsdd.
2022-04-16 22:56:34 toor at samba ~
# service wsdd status
wsdd is not running.

2022-04-16 23:02:02 toor at samba ~
# tail -n 12 /var/log/samba4/log.nmbd
   Got SIGTERM: going down...
[2022/04/16 22:56:16.963883,  0] ../../source3/nmbd/nmbd.c:960(main)
   nmbd version 4.13.14 started.
   Copyright Andrew Tridgell and the Samba Team 1992-2020
[2022/04/16 22:56:16.965950,  0] 
../../lib/util/become_daemon.c:136(daemon_ready)
   daemon_ready: daemon 'nmbd' finished starting up and ready to serve 
connections
[2022/04/16 22:56:39.721814,  0] 
../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
   *****

   Samba name server SAMBA is now a local master browser for workgroup 
WORKGROUP on subnet 192.168.5.24

   *****


So, nmbd has not been disabled.  How do I disable nmbd on FreeBSD 12.3-R?


2022-04-16 23:02:56 toor at samba ~
# tail -n 13 /var/log/samba4/log.smbd
[2022/04/16 22:56:17.013720,  0] ../../source3/smbd/server.c:1784(main)
   smbd version 4.13.14 started.
   Copyright Andrew Tridgell and the Samba Team 1992-2020
[2022/04/16 22:56:17.167275,  0] 
../../lib/util/become_daemon.c:136(daemon_ready)
   daemon_ready: daemon 'smbd' finished starting up and ready to serve 
connections
[2022/04/16 22:56:17.176516,  0] 
../../source3/lib/util_sock.c:334(open_socket_in)
   open_socket_in(): socket() call failed: Protocol not supported
[2022/04/16 22:56:17.176646,  0] 
../../source3/smbd/server.c:1077(smbd_open_one_socket)
   smbd_open_one_socket: open_socket_in: Protocol not supported
[2022/04/16 22:56:17.176671,  0] 
../../source3/lib/util_sock.c:334(open_socket_in)
   open_socket_in(): socket() call failed: Protocol not supported
[2022/04/16 22:56:17.176691,  0] 
../../source3/smbd/server.c:1077(smbd_open_one_socket)
   smbd_open_one_socket: open_socket_in: Protocol not supported


So, smbd is still complaining about protocols.


2022-04-16 23:04:08 toor at samba ~
# tail -n 29 /var/log/messages | head -n 23
Apr 16 22:56:35 samba daemon[14846]: 2022-04-16 22:56:35,125:wsdd 
WARNING(pid 14847): no interface given, using all interfaces
Apr 16 22:56:35 samba daemon[14846]: Traceback (most recent call last):
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1799, in <module>
Apr 16 22:56:35 samba daemon[14846]:     sys.exit(main())
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1754, in main
Apr 16 22:56:35 samba daemon[14846]:     nm = 
RouteSocketAddressMonitor(aio_loop)
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1058, in __call__
Apr 16 22:56:35 samba daemon[14846]:     obj.enumerate()
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1097, in enumerate
Apr 16 22:56:35 samba daemon[14846]:     self.do_enumerate()
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1471, in do_enumerate
Apr 16 22:56:35 samba daemon[14846]: 
self.parse_route_socket_response(rt_buf.raw, True)
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1505, in parse_route_socket_response
Apr 16 22:56:35 samba daemon[14846]:     new_intf = 
self.parse_addrs(buf, sa_offset, offset + rtm_len, intf, addr_mask, 
rtm_type, intf_flags)
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1551, in parse_addrs
Apr 16 22:56:35 samba daemon[14846]:     self.handle_new_address(addr, 
addr_family, intf)
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
1161, in handle_new_address
Apr 16 22:56:35 samba daemon[14846]:     mch = 
MulticastHandler(addr_family, addr, interface, self.aio_loop)
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
83, in __init__
Apr 16 22:56:35 samba daemon[14846]:     self.init_v4()
Apr 16 22:56:35 samba daemon[14846]:   File "/usr/local/bin/wsdd",
line
163, in init_v4
Apr 16 22:56:35 samba daemon[14846]: 
self.uc_send_socket.bind((self.address, WSD_UDP_PORT))
Apr 16 22:56:35 samba daemon[14846]: OSError: [Errno 48] Address already 
in use


So, wsdd is still broken.


I can still mount shares from Debian GNU/Linux 9.


Samba host is still not visible in Windows 7 Windows Explorer -> Network.


Entering a UNC path in Windows Explorer is now broken -- I get a Windows 
Security -> Enter network password dialog and it refuses to accept the 
password.


David

samba - Apr 2022 - FreeBSD 12.3-RELEASE and Samba 4.13

[Samba] FreeBSD 12.3-RELEASE and Samba 4.13

[Samba] FreeBSD 12.3-RELEASE and Samba 4.13