You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using command line options for sunshine is currently a bit tricky without proper documentation, and has some unwanted behavior (or I haven't found it, yet). Hence, it was a bit of trial and error for me to find a correct ordering for those options, specifically where to put the instanceID (-I).
This does not give an error but despite specifying -I 2 the actual instance of RPL is 0, because the DODAG is initialized when it hits the interface definition -i lowpan0, see here.
IMHO it would be better to actually init any RPL network after all options have been parsed successfully. Which would also have the benefit that options don't have to be in a certain order. I guess the original purpose/idea behind this was to allow for multiple RPL networks to be defined using cmd options? In this case, I would rather opt for some kind of config file, e.g. using YAML or JSON.
The text was updated successfully, but these errors were encountered:
Using command line options for
sunshine
is currently a bit tricky without proper documentation, and has some unwanted behavior (or I haven't found it, yet). Hence, it was a bit of trial and error for me to find a correct ordering for those options, specifically where to put the instanceID (-I
).Anyhow, a working command is something like:
This does not give an error but despite specifying
-I 2
the actual instance of RPL is0
, because the DODAG is initialized when it hits the interface definition-i lowpan0
, see here.IMHO it would be better to actually init any RPL network after all options have been parsed successfully. Which would also have the benefit that options don't have to be in a certain order. I guess the original purpose/idea behind this was to allow for multiple RPL networks to be defined using cmd options? In this case, I would rather opt for some kind of config file, e.g. using YAML or JSON.
The text was updated successfully, but these errors were encountered: