Maksim Yevmenkin wrote:
On Wed, Feb 4, 2009 at 11:27 AM, Alexander Motin <[email protected]> wrote:
Maksim Yevmenkin wrote:
Does actually this binding really necessary? rfcomm somehow works without
it.
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
guideline.
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.
You have told that NAP server works as hub. So, as I have understood, it
retransmits upstream traffic back down to all/some clients. So, it
transmits packets with MAC addresses of other clients via it's BT
adapter. So, source MAC address will not match his BDADDR. Or server is
an exception, which can violate the rule of equal addresses?
--
Alexander Motin
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "[email protected]"
