On May 21, 2015 8:37 AM, "Cenk Gündogan" <cenk.guendo...@fu-berlin.de> wrote: > > Hey Adam, > > I am currently adopting RPL to our new network stack and while doing so, > I also added sane functionalities which were plainly missing in the old implementation. > This also includes sending a DIS when initializing RPL for the first time. > However, I am just now realizing that such a DIS can get lost in our typical LLN case - it may make sense to send a DIS periodically until a DIO is received? > Does anyone has an opinion on this?
Good idea, as long as the periodic interval is large enough to not waste power or cause interruptions in normal traffic if there is no other rpl node on the network. > > Forcing a DIS from userspace sounds like a good feature. It may help in testing/debuging the dodag tree interactively. > I also thought about reseting the trickle timer from userspace to enforce DIOs. +1 for this. It would be nice to have some shell commands to call these functions too. Best regards, /Joakim > > Cheers, > Cenk > > > On 21.05.2015 04:36, Adam Hunt wrote: >> >> That's great. Is there any way to force a node to send a DIS message from userspace? >> >> >> On Wed, May 20, 2015, 5:34 PM Oleg Hahm <oliver.h...@inria.fr> wrote: >>> >>> Hi Adam! >>> >>> > Has anyone tested the amount of time it takes for a node (full or reduced >>> > function) to join an RPL routed 6lowpan network? I realize that it's very >>> > likely to vary quite a bit depending on the network, I'm just curious if >>> > anyone has an approximate range. >>> >>> As you said: it depends quite a bit on the network and the parameters. Since >>> nodes on the current RPL implementation won't send proactively DIS messages >>> and the interval of sending DIOs increases, it will usually take just a couple >>> of seconds if you try to join the network right after bootup, but can take >>> more than one minute in a later phase. >>> >>> Cheers, >>> Oleg >>> -- >>> printk (KERN_ERR "%s: Oops - your private data area is hosed!\n", ...) >>> linux-2.6.6/drivers/net/ewrk3.c >>> _______________________________________________ >>> devel mailing list >>> devel@riot-os.org >>> https://lists.riot-os.org/mailman/listinfo/devel >> >> >> >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel > > > > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
