All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: Isaiah Sarju <Isaiah.Sarju@Dartmouth.edu>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: RFCOMM channel 1 behavior differences
Date: Fri, 12 Aug 2011 21:06:15 -0300	[thread overview]
Message-ID: <20110813000615.GA32541@piper> (raw)
In-Reply-To: <4E45B5F1.4020807@Dartmouth.edu>

Hi Isaiah,

On 19:23 Fri 12 Aug, Isaiah Sarju wrote:
> Hello,
> 
> Does Ubuntu, linux kernel 2.6.38.10, running bluez 4.91-0ubuntu1
> have a special security policy for incoming rfcomm connections on
> channel 1, and not other channels?
> 

Most probably this is caused by a problem in how Ubuntu packages
BlueZ. 

Could you try this: edit /etc/bluetooth/main.conf and add "pnat-server"
to the DisabledPlugins field (perhaps you will need to uncomment that
line). Restart bluetoothd and see if it works.

> I ask this because I can create rfcomm connections between two
> computers on other channels (2, 3, 11, 13, etc.) but the listening
> computer refuses connections when connection requests come in for
> channel 1.
> 
> I use the following commands:
> 
> on listening computer:
> 	sudo rfcomm listen hci0 <channel>
> 
> on connecting computer:
> 	sudo rfcomm connect hci0 <BD_ADDR> <channel>
> 
> When <channel> does not equal 1 both computers connect no with no
> problem. When <channel> equals 1 I receive the error "Can't connect
> RFCOMM socket: Connection refused"
> 
> I tried this in to two different environments. 1) in a X-session and
> 2) in command line
> 
> 1) in GUI on the listing computer a dialogue box pops up requesting
> a pin for pairing. When I click cancel on the dialogue box of the
> listening machine the error "Can't connect RFCOMM socket: Connection
> refused" appears on the command line of the connecting machine.
> 
> 2) in command line mode on the listening computer nothing appears
> and I immediately receive the error "Can't connect RFCOMM socket:
> Connection refused" on in the command line of the connecting machine
> 
> These problems do not arise when attempting to connect on any other
> channels.
> 
> I have searched Google, looked at multiple forum posts on rfcomm
> connections, looked at forum posts on peoples' problems with rfcomm
> connections, reviewed this mailing list's archives, and I cannot
> find my specific problem.
> 
> Thank you for any advice you can provide or resources to which you
> can point me.
> 
> Regards,
> Isaiah
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


Cheers,
-- 
Vinicius

  reply	other threads:[~2011-08-13  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 23:23 RFCOMM channel 1 behavior differences Isaiah Sarju
2011-08-13  0:06 ` Vinicius Costa Gomes [this message]
2011-08-13  8:26   ` Johan Hedberg
2011-08-13 21:15     ` Isaiah Sarju

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=20110813000615.GA32541@piper \
    --to=vinicius.gomes@openbossa.org \
    --cc=Isaiah.Sarju@Dartmouth.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.