Hello,
as far as I understand, LoWPAN interfaces in Linux act like proxies for IPv6
packet transport from/to the device (through adaptation layer).
Additionally linux uses „Linux cooked” encapsulation for IPv6 packets which go
through those virtual interfaces.
So the result of this is that SDN controller, such as OpenDaylight won’t see
any traffic on vSwitch’s bridge which comes from lowpan virtual interface. The
interface may be added to the bridge without any „errors”, but I’m guessing it
just ignores packets which come this way with no proper encapsulation.
Here’s an example:
Bridge br_bt
Controller "tcp:10.0.0.1:6633"
is_connected: true
Port "bt0"
Interface "bt0"
Port br_bt
Interface br_bt
type: internal
OpenDaylight does see only br_bt local bridge. There’s no sign of bt0 interface.
Linux cooked encapsulation ignores HW addressing, so packet frame conversion
would need some server & db application which would synthetically defragment
Linux cooked packet (assigning and mapping some mac addresses to src/dest
devices even if they don’t have their own - like bluetooth dongles) and rebuild
the packet so it become a proper Ethernet packet. App could work
bidirectionally and it would use some new virtual interface with ethernet
encapsulation as it’s output, and lowpan virtual interface as it’s input.
Is it possible? Would it work if I’ve added this „new virtual interface” to
vSwitch as it’s internal port? One thing I understand is you cannot omit the
proxy interface, so any way to get it to work is to create an application
bridge between proxy interface and vSwitch, or to add "Linux cooked”
encapsulation support within vSwitch. Or maybe there’s some easier way to
achieve it using vLan or some existing tool?
Michal
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
