samba - Jan 2015 - Samba4 and 0.0.0.0:137 and 0.0.0.0:138 opened, why ? How do close it ?

Rowland, as I you mentioned firstly, I have 3 faces: lo, lan, wan.
And you are right, 0.0.0.0 are all IPs.
I need only either listen to lo and lan or lan only, but not wan also.
But in my case and because of 0.0.0.0 are all faces, listening 0.0.0.0
doesn' t equal lo and lan (127.0.0.1 and 192.168.0.254) .
Yes, there is no 95.95.95.14 in netstat list, but 0.0.0.0 should cover and
95.95.95.14 also, or I don' t understand it right.

By the way I examined Samba4 4.1.14 again and 'socket address' parameter
is
deprecated by now.
And I can not turn it off to listen to 0.0.0.0 correctly.
I made some tests. In fact there are not 0.0.0.0:137 and 0.0.0.0:138 but
either double 192.168.0.254 or 192.168.0.255 is appeared that make Samba4
working quite not good.
The one and only attempt is don' t include lo to interfaces parameter but
specify 127.0.0.1 to "socket address" . But it needs more checking for
me.
> I personally think that you think wrong, it is *LISTENING* on 0.0.0.0
> with ports 137 & 138 on the ipaddresses 127.0.0.1 and 192.168.0.254, it
> doesn't matter whether you turn 0.0.0.0 off in smb.conf, samba will
> still listen on the two ipaddresses.
I suppose that listening on 0.0.0.0 means that listening on ALL interfaces
including wan one.
But I don' t extremely need it. You understand it, I think.
I can be wrong.
But how can I check it to be completely sure that for 0.0.0.0 is listening
on 127.0.0.1 and on 192.168.0.254 and not on 95.95.95.14 ?
> I am willing to bet that you have other programs listening on 0.0.0.0,
> what are you going to do, stop them listening on 0.0.0.0 and if you do,
> are you going to complain that nothing then works ??
> You sound like one of the people in my country that writes heath &
> safety risk assessments just to cover their behinds.
You lose the bet.
Exactly Samba4 listens on 0.0.0.0:137 and 0.0.0.0:138.
If I stop Samba4, these are both sockets are not opened.
You can check it in your own to start netstat while Samba4 runs and when
stops.
Or you don' t have pointed out sockets above opened by Samba4, then, please
send config example and Sama4 version you use.

Unfortunatelly there are quite many people, and not in my country only, who
don't go deeper to question essence or don' t want to understand
question
completely before put useless words at their posts which are not
corresponded to a topic/posts.
Please read my posts more carefully and put words which are exactly within
topic only, without off-topic discussion, if you want, of course. Ok ?

Shortly, one more: my final purpose is to close 0.0.0.0 from Samba4 without
restriction its functionality on lan or/and lan interfaces or be completely
sure that it doesn' t cover wan IP (interface) , of course, when I don'
t
want it.
Topic is about Samba4 only, not other soft.

P. S.: Sorry for last post wasn' t sticked to continuing topic.

Am 12.01.2015 um 12:05 schrieb CpServiceSPb .:
> By the way I examined Samba4 4.1.14 again and 'socket address'
parameter is
> deprecated by now and I can not turn it off to listen to 0.0.0.0 correctly.
you can

https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#BINDINTERFACESONLY
bind interfaces only (G)
  This global parameter allows the Samba admin to limit
  what interfaces on a machine will serve SMB requests.
  It affects file service smbd(8) and name service nmbd(8)
  in a slightly different ways

https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#INTERFACES
interfaces (G)
  This option allows you to override the default network
  interfaces list that Samba will use for browsing, name
  registration and other NetBIOS over TCP/IP (NBT) traffic.
  By default Samba will query the kernel for the list of
  all active interfaces and use any interfaces except
  127.0.0.1 that are broadcast capable

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20150112/3c83e3f4/attachment.pgp>