On martes, 13 de diciembre de 2016 21:23:46 ART Florian Schlichting wrote: > Hi Matthew, > > On Tue, Dec 13, 2016 at 05:34:28AM -0500, Matthew E. J. Draisey wrote: > > I just fixed a situation where I couldn't get mpd to work over my home > > network. I think it may be this same issue. > > > > On my system > > > > # sysctl net/ipv6/bindv6only > > net.ipv6.bindv6only = 1 > > > > netstat would show init listening on [::]:6600 but doesn't report the > > IPV6_V6ONLY socket state so I had missed there was no socket listening on > > ipv4. > > > > Adding > > > > [Socket] > > BindIPv6Only=both > > > > to the mpd.socket unit fixed my problem. > > that's an interesing observation. Lisandro could you check that?
Yes, and while the mentioned workaround doesn't solves my issue it clearly has something to do. Remember my original bug where I stated that I needed to stop the systemd service and then start it by the init.d script? Well, thanks to this I've discovered that if I stop mpd.socket and then restart mpd.service I get both the IPV4 and IPV6 6600 port opened, whereas with mpd.socket I can only open the IPV6 one. Yes, my system also has net.ipv6.bindv6only = 1 (I don't remember changing it myself). If I stop mpd.socket/service and then: sysctl -w net.ipv6.bindv6only=0 and then restart mpd.socket I still only get the IPV6 behavior. Now I'm going to update this machine (it has been off for ~3 months) and try again. > AFAIK net.ipv6.bindv6only defaults to "both", so as a package maintainer > I wouldn't override a local configuration where the admin has decided to > deviate from the default. Well, I don't remember having changed this, but it's clearly ipv6only here :-/ -- No subestimes el ancho de banda de un camión cargado de cintas. Andrew S. Tanenbaum Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
