Hi, On 09/06/2016 01:50 PM, Amith Raghunath wrote: > Hi Alex, > >> 2016-09-04 20:13 GMT+02:00 Alexander Aring <alex.aring@xxxxxxxxx>: >>> >>> 2016-09-01 17:49 GMT+02:00 Amith Raghunath <Amith.Raghunath@xxxxxxxxx>: >>>> >>>> >>>> 1. The 6LBR has to forward the packets sent by one node to another node based on the link-local address. Is this scenario supported in the present code base ? >>> >>> >>> so far I know, no. >>> > > In RFC7668 it states that " 6LNs connected to the same 6LBR have to communicate with each other by > using the shared prefix used on the subnet." > It is not the link-local address that was referring to in the earlier query, kindly let me know whether this shared prefix feature and the 6LBR routing mechanism based on this shared prefix is yet to be implemented. I checked the net/bluetooth/6lowpan.c of linux kernel 4.7.1, could not find this feature. This would be required to support the "Isolated Bluetooth LE Network" topology. > Is this not simple run some Router Advertisment Daemon, e.g. radvd on the 6LBR Node and then putting a PIO into the RA messages. Maybe a ULA prefix for your $SUBNET? Then you have the routing mechanism based on your prefix. Additional you could also add a 6CO to compress the used prefix. See forked radvd branch [0] which used a non-stable UAPI to provide access to 6LoWPAN stateful compression. --- for the link-local case I through it must be possible to access 6LN's over it's their link-local address. Example 6LN(A) <---> 6LBR <---> 6LN(B) so it must be possible somehow to have a connection from A to B by using the link-local address. But RFC7668 says: "6LN-to-6LN communications using link-local addresses are not possible." So I think it's simple not possible and you must do the shared prefix and this is what you want (I think I finally understand), but this is not the job of 6LoWPAN subsystem - you need to do right IPv6 setup. - Alex [0] https://github.com/linux-wpan/radvd/tree/6lowpan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
