pan profile support in freebsd
maksim.yevmenkin at gmail.com
Wed Feb 4 12:02:35 PST 2009
On Wed, Feb 4, 2009 at 11:27 AM, Alexander Motin <mav at mavhome.dp.ua> wrote:
> Maksim Yevmenkin wrote:
>>> Does actually this binding really necessary? rfcomm somehow works without
>> please see Iain's response :) i knew he would chime in :) thanks Iain!
>> and, yes, i suspected that it would be something related to mac
>> addresses on virtual ethernet interface. i do not have a copy of spec
>> handy, but i recall something about setting mac address to be the same
>> as radio's bd_addr. dont remember if it was a requirement or more of a
>> in any case, i like Iain's suggestion to rewrite mac addresses on the
>> fly. i would have done it this way. also, i think, nap server should
>> just act as ethernet hub, i.e. forward everything everywhere. after
>> all, nap is supposed to be like local ethernet network :)
> Hmm. Working like an Ethernet hub also means that every single hub port (in
> our case every single point-to-point BT link) may transmit packets from
> different source MAC addresses, that can't be equal to BT adapter address.
> So or I don't understand your example, or something is wrong here.
why do you think it is wrong? logically all the radios are on the same
virtual ethernet network. i think the only issue here is that
apparently some clients are picky about src mac address and that
complicates the case when nap server has multiple radios.
>>> Indeed. But general number of BT tools, daemons and their options just
>>> making me sad.
>> i'm not sure how to read that :) there is, like, less than 10
>> bluetooth related daemons in total. each has, like, may be 10 options.
>> compare this to the number of options ls(1) has :) not sure what could
>> possibly make you sad here. if you feel that the documentation is not
>> adequate, please feel free to fix it :)
> 10 daemons is understood, as BT is not that simple and IP stack also have
> many different tools. But anyway having about 70 defined and undocumented
> arguments of hccontrol alone, one of which should be used for such basic
> thing as getting local btaddr, are not looking so funny for anybody who are
> not BT guru. May be writing of some man page with some BT basics to cross
> reference that basic tools could help. Or just better cross reference
> existing pages.
oh, please :) man hccontrol(8) gives you all the commands. it also
tells you to use 'help <command>' to get more information. also help
for each command is taken directly from the bluetooth specification.
i'm not sure how much more documentation can we put here. there are
also man pages for ng_hci(4) and ng_l2cap(4). that is already so much
more information than you can ever get on vast majority of bluetooth
enabled gadgets. oh, and btw, users are not even supposed to
know/touch any of this stuff. so if your bluetooth gadget does not
work - you sh*t out of luck for the most of the time :)
in ideal world, everything should just work. in real world, like
everything that has to do with rf, sometimes it doesn't :)
i agree, documentation could always be better, and i repeatedly asked
for help here. i do not know why, but for whatever reason people
prefer to put stuff on their private webpages/blogs/forums/etc.
instead of just saying "hey, i had this problem and here is how i
fixed it. wouldn't it be nice if you could document this in man
page/handbook. btw, here is the patch."
More information about the freebsd-bluetooth