bug, smb 2.2.1a, redhat 7.2

[Kohei Yoshida]

On Tue, 2001-12-18 at 10:06, 5468696A6D656E wrote:
> i am not sure whether this is by default or not, but i think i found a tiny bug. (maybe by design, i am not a samba guru)
> 
> Steps to reproduce:
> Create a loopback device without asigning an ip to it. 
> (not sure whether it is also reproducable without the loopback device at all)
> 
> set in smb.conf:
> bind interfaces only = yes
> interfaces = yourip
> 
> According to what i could find in the docs it should now only use the ip of interfaces.
> 
> But it will not let you connect. If you connect with windows it will write something in the log log.smbd like:
>  smbd/oplock.c:init_oplocks(1205)
>   open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested address
> 
> Looking at the code  it seems it is allways trying to open a socket on 127.0.0.1
> open_socket_in(SOCK_DGRAM, 0, 0, htonl(INADDR_LOOPBACK),False)
> 
> But surely, if you specify "bind interfaces only" to yes and interfaces does not have 127.0.0.1 it should not try that?
> 
> Off course, bug or not, it is not severe. Idiots like me who sometimes do not have a loopback device are rare.
> 
> Hope this helps,
> kind regards,
> 
> Thijmen
> 
> -- 
> __Thijmen Klok________
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
> 

It's been my understanding that if you use "bind interfaces only", you
must include 127.0.0.1 in your interfaces as Samba relies on this ip for
loopback calls.

Kohei