From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Connectionless l2ping.
Date: Tue, 17 Jul 2007 21:57:59 +0200 [thread overview]
Message-ID: <1184702279.28210.40.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <C2BFEB57.558%tjoconno@unity.ncsu.edu>
Hi TJ,
> Is it possible to use connectionless sockets with L2CAP? I tried rewriting
> l2ping to use SOCK_DGRAM and sendto / recvfrom instead of SOCK_RAW,
> send,recv but with no luck.
of course not. This is not how L2CAP works. The SOCK_RAW is special and
only present for that exactly purpose.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-17 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 19:18 [Bluez-devel] Connectionless l2ping TJ OConnor
2007-07-17 19:57 ` Marcel Holtmann [this message]
2007-07-17 20:10 ` TJ OConnor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1184702279.28210.40.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox