linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: M <lists@gazelasport.sk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Ultimate PAN howto. Where?
Date: Tue, 22 Nov 2005 16:18:07 +0100	[thread overview]
Message-ID: <438336AF.8050204@gazelasport.sk> (raw)
In-Reply-To: <1132671135.28644.69.camel@blade>

Marcel Holtmann wrote:
> Hi,
> 
> 
>>>>I'm trying to get PAN running, NAP on linux, 2 PANUs on windows. 
>>>>There is no problem with the windows boxes, it gives me headaches to set 
>>>>up the linux box however. I got everything running quite fine with just 
>>>>one client using non-briged routing, now I would like to bridge bnepX 
>>>>and eth0 interfaces so that:
>>>>
>>>>- IP addresses are asigned by DHCP
>>>>- it's possible to connect to internet from NAP box (after following one 
>>>>howto it wasn't possible)
>>>>- everything is automatic - after the setup anyone should be able to 
>>>>turn on the NAP box and connect, even without an account.
>>>>
>>>>Please, direct me to the right howto, tell me which parts to skip and 
>>>>what to do another way.
>>>
>>>
>>>actually the automatic part is distribution specific, because you need
>>>to create the bridge at startup and run the dedicated DHCP server. You
>>>also need to make sure the bnepX devices are added/removed to the bridge
>>>when pand accepts a new connection.
>>
>>After experimenting I got bridge + DHCP working, it's not automatic but 
>>that does not matter now anyway, cause I had to change it back.
>>
>>If remote device disconnects, the bnepX interface is not fully unregistered:
>>
>>[/var/log/messages]:
>>
>>kernel: pan0: port 1(bnep0) entering disabled state
>>net.agent[12626]: remove event not handled
>>kernel: unregister_netdevice: waiting for bnep0 to become free. Usage 
>>count = 1
>>
>>The last message is repeated at regular intervals.
>>
>>`brctl show` shows bnep0 in pan0 bridge interface
>>
>>`brctl delif pan0 bnep0` results in "interface bnep0 does not exist!"
>>
>>`ifconfig` or `ifdown bnep0` freeze up
>>
>>I can't even turn of the computer regulary, I have to hard reset it.
>>
>>Is this a bug?
> 
> 
> sounds like a bug in the bridge code. What kernel do you use?

kernel-i686-up-4GB-2.6.12.12mdk

vendor Mandriva


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-11-22 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  9:08 [Bluez-users] Ultimate PAN howto. Where? M
2005-11-22 11:12 ` Marcel Holtmann
2005-11-22 14:26   ` M
2005-11-22 14:52     ` Marcel Holtmann
2005-11-22 15:18       ` M [this message]

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=438336AF.8050204@gazelasport.sk \
    --to=lists@gazelasport.sk \
    --cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).