David Palma <david.palma@xxxxxxx> wrote:
> After shamefully trying it, I suppose it's not possible to add a lowpan
> interface to a bridge because it's not an ethernet segment.
> However, I was wondering if this could/will be a possibility in the
> future?
No, because 802.15.4 uses 8-byte EUI64 addresses, or 2-byte short addresses.
> If I understood correctly there was a discussion about the tun/tap
> driver that touched upon similar aspects, but I didn't get the
> conclusion.
> The motivation for this question is to enable offloading/traffic
> redirection between 15.4 and .11 depending on certain conditions
> (e.g. energy and distance). I have accomplished this with changing
> routes and iptables but I was looking for an "SDN/OpenFlow-like"
> approach.
Stupid Layer-2 tricks are a bad idea here.
Use smart layer-3 techniques instead: routing.
Assuming that both of your devices have 15.4 and .11 interfaces, then put
them into seperate subnets, and then distribute /128 addresses to your end
systems, and use a dynamic routing protocol to announce things.
Choices would include: RPL (see my unstrung.sandelman.ca, and others),
BABEL, OSPFv3.
Before you complain about overhead of that, you need to go read the source
code for the bridging code that includes {R,M,}STP.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
