Alexander Aring <aar@xxxxxxxxxxxxxx> wrote:
> I had some dicussion at IETF that the destination pan id could be
> different than the source pan. So we need to change it "again" to remove
> it. :-)
> On rx side:
> - dst pan id can be everything (also 0xfff?)
> - src pan cannot be 0xffff, which should be filtered before reaching
> packet layer.
> On tx side:
> - We some mechanism to tell the destination pan, we need anyway a
> 6lowpan netlink api, so we could add 802.15.4 6lowpan option on it,
> to change the destination panid per interface.
> Or we do what vlan does:
> # ip link add link eth0 name eth0.100 type vlan id 100
> e.g.
> # ip link add link wpan0 name lowpan0 type lowpan pan id 0xbeef
> which can be handled by ip plugin command stuff.
I suggest that panid be handled in the same way as vlan tags: by creating new
virtual lowpanX interfaces. That requires some work below...
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
