linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Disable pnat-server
Date: Sun, 03 Jul 2011 21:56:57 +0200	[thread overview]
Message-ID: <4E10C989.9060909@kernelconcepts.de> (raw)
In-Reply-To: <20110703190615.GA20814@dell.ger.corp.intel.com>

Am 03.07.2011 21:06, schrieb Johan Hedberg:
> On Sun, Jul 03, 2011, Nils Faerber wrote:
>>> There should be absolutely no reason for Ubuntu have this plugin enabled
>>> or even compiled. You might wanna file a bug to them to disable it. The
>>> only place where it makes sense to be compiled is in Nokia's Maemo
>>> Harmattan platform. For everything else it should be disabled (as it is
>>> by default).
>>
>> Yes, indeed - I have not tried, what is the default when compiling the
>> BlueZ package, en- or disabled?
> 
> It's disabled (grep for pnat_enable in acinclude.m4).

OK, then it would indeed be Ubuntu's fault.

>>> Btw, if you have your own RFCOMM based service you should take a look at
>>> doc/assigned-numbers.txt to be sure not to conflict with any of those
>>> services. The range of possible RFCOMM channels (1-31) is so small that
>>> it's easy to get conflicts.
>>
>> I was not the one to choose that ;)
>> It is for the Sony Ericsson LiveView and I have to use what they did.
> 
> Hmm? So they don't use SDP do discover the RFCOMM channel but directly
> connect to channel 1?

Um...well I just checked that code.
What the device does it look for the service name on the host and on the
host side it is bound to channel 1 - I think. I borrowed that part of my
code from some old BlueZ code, forgot which.

>>>> After some more searching and reading sources I found that plugins can
>>>> theoretically be disabled in bluetoothd's config file main.conf. So I added
>>>>
>>>> DisablePlugins = pnat-server
>>>
>>> The plugin is called pnat, so that line should read DisablePlugins=pnat
>>
>> Sure?

Yes, you are ;)
Tried that and now my device works again - yippie!


Thanks for your quick help!

> Johan
Cheers
  nils

-- 
kernel concepts GbR        Tel: +49-271-771091-12
Sieghuetter Hauptweg 48
D-57072 Siegen             Mob: +49-176-21024535
http://www.kernelconcepts.de

  reply	other threads:[~2011-07-03 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03 15:40 Disable pnat-server Nils Faerber
2011-07-03 18:04 ` Johan Hedberg
2011-07-03 18:48   ` Nils Faerber
2011-07-03 19:06     ` Johan Hedberg
2011-07-03 19:56       ` Nils Faerber [this message]
2011-07-03 20:13         ` Johan Hedberg
2011-07-03 20:28           ` Nils Faerber

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=4E10C989.9060909@kernelconcepts.de \
    --to=nils.faerber@kernelconcepts.de \
    --cc=linux-bluetooth@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).