nmbd using the wrong source address upon sending Node Status requests

Richard Sharpe rsharpe at richardsharpe.com
Fri Apr 25 07:32:59 GMT 2003

On Fri, 25 Apr 2003, Volker Lendecke wrote:

> On Thu, Apr 24, 2003 at 12:09:32PM -0700, Richard Sharpe wrote:
> > > Using the first "interfaces" entry means that "socket address" can remain 
> > > depricated, and it also means that the sysadmin doesn't have to think 
> > > about configuring the "socket address" parameter.
> > 
> > I think this is the right solution.
> No, I don't think so, sorry. At least not as a default. I've seen 
> interfaces = lo eth0

Right, but Samba is already enumerating interfaces. It simply has to pick 
the first interface in the list that is broadcast capable.

lo on my Linux machine shows up as:

lo        Link encap:Local Loopback  
          inet addr:  Mask:
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:28440 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28440 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10265240 (9.7 Mb)  TX bytes:10265240 (9.7 Mb)

while lo0 on my FreeBSD 4.3 system shows up as:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 
	inet6 ::1 prefixlen 128 
	inet netmask 0xff000000 

So, looking for broadcast interfaces will work.

Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com

More information about the samba-technical mailing list