[Pkg-samba-maint] Bug#574283: samba: Doesn't bind to IPv4
webmaster
rm.imposit at gmail.com
Thu Mar 3 05:42:09 UTC 2011
Hello,
I can produce something in addition.
Bevore upgrade to squeeze i could bind samba to an openvpn tun device
(interfaces 172.16.10.1/24)
after upgrade nmdb cant even start
[2011/03/03 06:37:29.641278, 2] lib/interface.c:340(add_interface)
added interface 172.16.10.1 /255.2 ip= 172.16.10.1 bcast= 172.16.10 .255 netmask=255.255.255.0
[2011/03/03 06:37:29.641336, 0] lib/util_sock.c:880(open_socket_in)
bind failed on port 137 socket_addr = 172.16.10.255
ERROR: Failed when creating subnet lists. Exiting.
(why it trys to bind to the broadcast adress hmm)
however wen i set the netmask wrong 255.255.255.255 it starts but cant find the interface anymore but it starts at least
so i tried without specifiing an interface and bind it to all
result is that it binds only to non dynamical interface which are in /etc/network/interfaces
all otherinterfaces (bridges and openvpn tuns) are simply not found at all
funny thing is smb can bind to all (it also binds fine to my 172.16.10 /249)
and apear in the netstat while nmdb does in no case ever bind to those interfaces
this is a bit of an real problem - i need the wins support cause most users dont even know what an ip is :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20110303/e61110a9/attachment.htm>
More information about the Pkg-samba-maint
mailing list