This should be working without any config changes as of the next
snapshot kernels.
On 2011-04-22, John Danks wrote:
> I'm seeing the nmbd daemon throw some errors in the log at startup and
> then exit. I'm using the April 21 i386 snapshot, and samba-3.5.8p2
> package without any flavors, from ft
On Sun, Apr 24, 2011 at 12:49:46PM +0100, Stuart Henderson wrote:
> On 2011/04/24 10:42, Claudio Jeker wrote:
> > On Sat, Apr 23, 2011 at 08:58:12PM +, Stuart Henderson wrote:
> > > On 2011-04-23, Henning Brauer wrote:
> > > > * Stuart Henderson [2011-04-23 14:41]:
> > > >> Should we do this
On 2011/04/24 10:42, Claudio Jeker wrote:
> On Sat, Apr 23, 2011 at 08:58:12PM +, Stuart Henderson wrote:
> > On 2011-04-23, Henning Brauer wrote:
> > > * Stuart Henderson [2011-04-23 14:41]:
> > >> Should we do this or should we rethink allowing sockets to be
> > >> bound to broadcast IP add
On Sat, Apr 23, 2011 at 08:58:12PM +, Stuart Henderson wrote:
> On 2011-04-23, Henning Brauer wrote:
> > * Stuart Henderson [2011-04-23 14:41]:
> >> Should we do this or should we rethink allowing sockets to be
> >> bound to broadcast IP addresses?
> >
> > i have no idea. and that seems to be
On 24/04/2011 6:58 AM, Stuart Henderson wrote:
On 2011-04-23, Henning Brauer wrote:
* Stuart Henderson [2011-04-23 14:41]:
Should we do this or should we rethink allowing sockets to be
bound to broadcast IP addresses?
Why the change in behaviour the first place? Is OpenBSD becoming less
p
On 2011-04-23, Henning Brauer wrote:
> * Stuart Henderson [2011-04-23 14:41]:
>> Should we do this or should we rethink allowing sockets to be
>> bound to broadcast IP addresses?
>
> i have no idea. and that seems to be common for all of us. i really
> dunno. anybody?
>
Unless there are objectio
* Stuart Henderson [2011-04-23 14:41]:
> Should we do this or should we rethink allowing sockets to be
> bound to broadcast IP addresses?
i have no idea. and that seems to be common for all of us. i really
dunno. anybody?
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, htt
Diff below:-
- sets "nmbd bind explicit broadcast" appropriately for -current OpenBSD,
causing nmbd to bind to 0.0.0.0 (or whatever is set in "socket address")
rather than separately binding a socket to each broadcast address.
Should we do this or should we rethink allowing sockets to be
bound to
On 2011-04-22, Stuart Henderson wrote:
> This is due to recent changes in OpenBSD's network stack.
>
> Setting "nmbd bind explicit broadcast = no" in smb.conf is likely
> to fix things for a single-homed host but it looks like samba
> has a problem with this on a multi-homed host.
Followup to thi
This is due to recent changes in OpenBSD's network stack.
Setting "nmbd bind explicit broadcast = no" in smb.conf is likely
to fix things for a single-homed host but it looks like samba
has a problem with this on a multi-homed host.
Please try it and group-reply back to me and ports@ with details
I'm seeing the nmbd daemon throw some errors in the log at startup and
then exit. I'm using the April 21 i386 snapshot, and samba-3.5.8p2
package without any flavors, from ftp5.usa.openbsd.org. The config is
the default that comes with the package. I started samba with
/etc/rc.d/samba start.
Here'
11 matches
Mail list logo
