From: Max Krasnyansky <maxk@qualcomm.com>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: Alexandros Karypidis <karypid@inf.uth.gr>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: [Bluez-users] How do I obtain a free PSM automatically?
Date: Wed, 19 Feb 2003 12:04:06 -0800 [thread overview]
Message-ID: <5.1.0.14.2.20030219115417.0cefad08@mail1.qualcomm.com> (raw)
In-Reply-To: <1045609378.30001.88.camel@pegasus.local>
At 03:00 PM 2/18/2003, Marcel Holtmann wrote:
>Hi Max,
>
>> >I think about something like a special way to bind psm 0 and all
>> >incoming connections which are not associated with a bounded psm go to
>> >this application. So you can listen on all PSM with only one call.
>> >
>> >I want use this for one of my projects, but I can also work around this
>> >problem. So my question is if this makes sense to you and how much
>> >modifications in the L2CAP core may be needed ?
>> Modifications would be simple. But that feature doesn't make sense to me.
>
>I will try to explain for what it will be good. I want to do something
>which can be described like "L2CAP Forwarding Proxy over Ethernet". So
>the only special PSM is the one for SDP, all others (mainly over 0x1000)
>would be used dynamicly and forwarded to other devices over another
>medium like ethernet. For this I only want to have two listen calls, one
>for all not bound PSM's and one for SDP.
For that you should probably hack hcidump and forward L2CAP packets.
The problem with your approach is that connection to _any_ PSM will always
succeed even if that PSM is not active.
i.e.
1. accept()
2. try to forward
3. forward fails
4. close connection
That will confuse device that tries to connect to you because it will
assume that this PSM is in fact open but server closed connection
because of an error or something.
>How much we have to change for something like this?
l2cap_get_sock_by_psm() will have to be modified slightly.
But we're not going to do that ;-).
Max
next prev parent reply other threads:[~2003-02-19 20:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302071951.35073.karypid@inf.uth.gr>
[not found] ` <1044653120.32671.4.camel@pegasus.local>
2003-02-08 11:42 ` [Bluez-users] How do I obtain a free PSM automatically? Stephen Crane
[not found] ` <200302072329.21333.karypid@inf.uth.gr>
[not found] ` <1044653775.32672.14.camel@pegasus.local>
2003-02-08 15:40 ` Alexandros Karypidis
2003-02-08 16:14 ` [Bluez-devel] " Alexandros Karypidis
2003-02-10 21:13 ` Max Krasnyansky
2003-02-11 12:01 ` Marcel Holtmann
2003-02-11 17:26 ` Alexandros Karypidis
2003-02-11 17:52 ` Maksim Yevmenkin
2003-02-11 18:58 ` Max Krasnyansky
2003-02-11 18:06 ` Max Krasnyansky
2003-02-17 14:12 ` Marcel Holtmann
2003-02-18 21:06 ` Max Krasnyansky
2003-02-18 23:00 ` Marcel Holtmann
2003-02-19 20:04 ` Max Krasnyansky [this message]
2003-02-11 16:30 ` Alexandros Karypidis
2003-02-10 20:49 ` Max Krasnyansky
2003-02-11 16:22 ` Alexandros Karypidis
2003-02-11 18:04 ` [Bluez-devel] " Maksim Yevmenkin
2003-02-11 18:52 ` Max Krasnyansky
2003-02-11 20:01 ` Maksim Yevmenkin
2003-02-11 21:09 ` Max Krasnyansky
2003-02-11 18:23 ` [Bluez-devel] Re: [Bluez-users] " Max Krasnyansky
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=5.1.0.14.2.20030219115417.0cefad08@mail1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=karypid@inf.uth.gr \
--cc=marcel@rvs.uni-bielefeld.de \
/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