public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "R.M.M" <rmm79@op.pl>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] can't add bnep0 to bridge pan0: Invalid argument
Date: Tue, 14 Nov 2006 17:43:46 +0100	[thread overview]
Message-ID: <4559F242.5040106@op.pl> (raw)
In-Reply-To: <1163405941.26272.43.camel@localhost>

Marcel Holtmann wrote:
> Hi,
> 
<snip>

>> The problem turn up when I try (after establishing connection) to add
>> bnep0 interface to pan0 bridge interface. After
>>
>> ~# brctl addif pan0 bnep0
>>
>> I get:
>>
>> can't add bnep0 to bridge pan0: Invalid argument
>>
>> (bnep0 has IP 0.0.0.0 after ifconfig bnep0 0.0.0.0 and is up, though I
>> get no answer on ping which I could be a routing problem actually. Also
>> adding eth1 makes no problems).
>>
>> As I said, no messages in logs, no more information. What's wrong?
> 
> you have a dongle with an invalid BD_ADDR. Return that dongle and get
> one which has a valid address. Dongles using this address can't be added
> to a bridge.

Thanks a lot for this piece of advice. I wasn't aware there are
unlicensed dongles on the market. Unfortunately I can't give mine back:/
Are they somehow damaged or is it only a software problem?

-- 
Regards,
R.M.M

-------------------------------------------------------------------------
SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now.
Check out Slashdot's new job board. Browse through tons of technical jobs
posted by companies looking to hire people just like you.
http://jobs.slashdot.org/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-11-14 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 19:36 [Bluez-devel] can't add bnep0 to bridge pan0: Invalid argument R.M.M
2006-11-13  8:19 ` Marcel Holtmann
2006-11-14 16:43   ` R.M.M [this message]
2006-11-14 16:54     ` Marcel Hilzinger

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=4559F242.5040106@op.pl \
    --to=rmm79@op.pl \
    --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