Le mer. 24 juil. 2019 à 00:27, Dark Penguin <darkpeng...@yandex.com> a écrit :
>
> On 24/07/19 00:15, Mathieu Parent wrote:
> > Version: 2:4.9.5+dfsg-5
> >
> > I'm closing this bug with the version in buster.
> >
> > Le dim. 21 juil. 2019 à 21:45, Dark Penguin <darkpeng...@yandex.com> a
> > écrit :
> >>
> >> I tried this just now. The result is, basically, nothing: my kernel does
> >> not have IPv6 support anyway, so restricting IPv6 out on the systemd
> >> level does not change anything. There are still error messages about
> >> being unable to bind to IPv6 upon restarting smbd, however with this,
> >> restarting it also takes a few seconds instead of happening almost
> >> instantly.
> >>
> >> I guess the "proper" solution would be the same: if there are no IPv6
> >> interfaces in the system, smbd should not try to bind to them. If it was
> >> specifically instructed to bind to a certain interface and it is
> >> unavailable, then output an error message "This interface is requested
> >> but unavailable", instead of "open_socket_in(): socket() call failed:
> >> Address family not supported by protocol". This error message is not
> >> even decipherable without Google's help.
> >
> > The following binds to IPv4 only:
> >
> > interfaces = lo 0.0.0.0
> > bind to interfaces only = yes
> >
> > Regards
>
>
> Umm... I've actually tried that before.
Confirmed with:
interfaces = 127.0.0.0/8 0.0.0.0
bind interfaces only = yes
$ sudo ss -lntp | grep smbd
LISTEN 0 50 127.0.0.1:445
0.0.0.0:* users:(("smbd",pid=9146,fd=32))
LISTEN 0 50 127.0.0.1:139
0.0.0.0:* users:(("smbd",pid=9146,fd=33))
--
Mathieu Parent
