I hadn't realized until I was trying to communicate LL (fe80::) addresses to a plugfest peer that the LL addresses and layer-2 addresses are not stable. (no eeprom in at86af23x, most of the OpenMote/Redwire devices that Contiki runs on have same issue) Yes, we can set them from /etc/network/interfaces using iwpan, but I'm a bit not keen about this as a general solution. Now, I have some ideas about deploying (802.1AR) certificates that permit a node to prove it owns a particular L2 address. Given that certificate, I might as well configure the l2 and short address, etc. directly from the info in the certificate. This solution will suit my needs well, but probably not others. We do not have a kernel command line option to set the LL address, we should, but in the specific case of the RPI, that won't help that much, because the RPI doesn't use GRUB (nor uboot by default), so the cmdline is hard to update. Does this matter that much; I'm not sure. Still, I think we should have a non-programmatic way to do this, maybe some kind file in /etc, or maybe a sensible recommendation for having udev do it. I also noted that if I tried to change some things, such as panid and l2 address that it wouldn't work until I rebooted. Probably there was another sequence I could have used, but I didn't figure it out at the time. Also, as far as I know, we can't operate on more than one panid at the same time. I could imagine that maybe one could create multiple lowpan on top of the same wpanX interface, but the panid is actually at the lower level. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
Attachment:
signature.asc
Description: PGP signature
