History log of /netbsd/usr.sbin/btpand/server.c (Results 1 – 8 of 8)
Revision Date Author Comments
# f5ca43cb 14-Oct-2012 plunky <plunky@NetBSD.org>

add code to ensure that SO_SNDBUF is large enough on client connections,
as was previously done for server mode


# 585aadf0 08-Feb-2011 plunky <plunky@NetBSD.org>

the default socket rcvbuf for L2CAP is only 4Kbytes which is only
2 and a bit ethernet packets. Check and increase SO_RCVBUF on startup
so that we have buffers for 10 complete packets, should solve a

the default socket rcvbuf for L2CAP is only 4Kbytes which is only
2 and a bit ethernet packets. Check and increase SO_RCVBUF on startup
so that we have buffers for 10 complete packets, should solve a
reported problem with overruns at higher connection speeds (our L2CAP
does not have any flow control).

(the default can still be adjusted upwards using sysctl)

show more ...


# b04b174c 25-Oct-2009 plunky <plunky@NetBSD.org>

after setting the L2CAP link mode in server mode, retrieve the kernels
interpretation of it and check specifically for auth when creating the
service record.


# f379f083 24-Oct-2009 plunky <plunky@NetBSD.org>

use correct value for 10 Mbps


# ab1f45ac 12-May-2009 plunky <plunky@NetBSD.org>

update to use the new Service Discovery API


# 493f204d 12-May-2009 plunky <plunky@NetBSD.org>

rework the channel shutdown code path, each channel now has its own
action to process which separates the server and client code.


# 8d16a253 24-Jan-2009 plunky <plunky@NetBSD.org>

The "Service Availability" value in the SDP record should be a number
from 0-255 indicating how much availability the service has, rather
than the "Load Factor (0-7)" as used in the "Class of Device"

The "Service Availability" value in the SDP record should be a number
from 0-255 indicating how much availability the service has, rather
than the "Load Factor (0-7)" as used in the "Class of Device" setting.

show more ...


# 1fc74d21 17-Aug-2008 plunky <plunky@NetBSD.org>

add btpand(8), a Bluetooth PAN daemon