On Sat, Jan 21, 2006 at 07:59:58AM +0100, Christian Perrier wrote:
> > I have mixed feelings about putting these as examples, because there are so
> > many ways to get this wrong... c.f. the just opened bug #348766. :)

> Hmm, 348766 does not seem to happen because the user uses these options.

Indeed; my mistake.

> > If this is added, please list 'interfaces' *first* before 'bind interfaces
> > only', and make sure the comment on 'bind interfaces only' says that
> > 'interfaces' must also be set.  The comment on interfaces should also
> > probably mention the "dynamic interfaces" caveat from the manpage.

> Hmmm, man smb.conf does not give any clue about this...Where do you
> find documentation about it? First time I here about this parameter
> (which means nothing as there are so many).

Sorry, I was actually reading again the section on "bind interfaces only".

  For file service it causes smbd(8) to bind only to the interface list
  given in the interfaces parameter. This restricts the networks that smbd
  will serve to packets coming in those interfaces. Note that you should not
  use this parameter for machines that are serving PPP or other intermittent
  or non-broadcast network interfaces as it will not cope with non-permanent
  interfaces.

> So, proposing this:

> # The specific set of interfaces / networks to bind to
> # This can be either the interface name or an IP address/netmask
> ;   interfaces = 127.0.0.0/8 eth0

I would say

 # This can be either the interface name or an IP address/netmask;
 # interface names are normally preferred

> # Only bind to the named interfaces and/or networks (see the
> # 'interfaces" option which MUS be set if you use this). 
> # It is recommended that you enable this feature if your Samba 
> # machine is not protected by a firewall or is a firewall itself
> ;   bind interfaces only = true

Maybe

 # Only bind to the named interfaces and/or networks; you must use the
 # 'interfaces' option above to use this.
 # It is recommended that you enable this feature if your Samba machine is
 # not protected by a firewall or is a firewall itself.  However, this
 # option cannot handle dynamic or non-broadcast interfaces correctly.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to