Hi Adam, 2014-11-07 11:38 GMT+01:00 Adam Hunt <voxa...@gmail.com>:
> Will this refactoring effort allow for multiple interfaces on a single > RIOT device? Yes this (and easier more modularity through less coherence => easier testing) is the main reason for the refactoring. > What about bringing the border router support back into a state where a > real, well designed RIOT based border router? Or, is the role of a border > router better filled by Linux and the associated 15.4 driver work that's > being done. > The broken border router is mainly the fault of the broken 6LoWPAN Neighbor Discovery and the restricted possibility of multiple interfaces (it used to be just a thread, that scooped all packets not addressed to a node in the PAN over the UART of a node with no other option available). Since the refactoring effort also aims to squash this bugs once and for all (again through easier testing) and the multiple interface support is build-in into the model (you can even have SLIP over UART, if you do not have an Ethernet or WiFi module; have a look at PR #1454 [1]), there is nothing that is in the way of a functioning border router. Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/pull/1454
_______________________________________________ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
