Hi Henrik, Not quite globally as we're using unique-local addresses (fdxx:: range), but yes. We're using DHCPv6 to hand out addresses, but this requires further hacking to support extended 802.15.4 addresses during the DHCP phase (which reminds me, I should post a diff to #30 to hopefully inspire someone to fix it "properly").
For each site we essentially have one node running PppRouter connected to an ARM Linux board where the DHCPv6 server runs (wide-dhcpv6 was the only one we could make work with relayed requests btw). The motes themselves have UID chips in them so each has a valid Eui64 to derive their extended 15.4 address from. Once they're assigned an IPv6 address, they then derive a short 15.4 address from that (-DBLIP_DERIVE_SHORTADDRS). This allows us to use a single firmware image across all the mesh nodes without having to futz around with tos-set-symbols to alter TOS_NODE_ID for each mote. Having had support for regular router solicitations would have been a bit easier than doing the DHCP dance, but now that we have it set up it works well. Cheers, /Johny 2011/9/15 Henrik Mäkitaavola <[email protected]> > Hi, > > As anyone made motes running BLIP 2.0 reachable globally? If you have how > did you solve it? > > If no one has succeeded in doing this does anyone know how it is expected > to work? > > We have made this possible with static IP addresses and don't intend to use > DHCP in the future but instead Router solicitation as it is done in BLIP > 1.0. This is how we understand it its meant to be done with IPv6 so I also > wonder why this solution has been abandoned in the new BLIP 2.0 stack? Maybe > its just not implemented yet? > > /Henrik > > -- Johny Mattsson Senior Software Engineer DiUS Computing Pty. Ltd. *where ideas are engineered *
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
