Hey,
That sounds like the problem described in this issue [1].
The current master / release candidate version
should include a "workaround" fix for that.
Cheers,
Cenk
[1] https://github.com/RIOT-OS/RIOT/issues/5122
On 04/22/2016 12:19 PM, smlng wrote:
Hi everyone,
I'm testing COAP between
Hello Mateusz,
This may be unrelated to your problem, but just FYI:
You need a global unique IPv6 address for RPL to work.
With a link-local address (fe80::) you won't be able
to create the RPL-DODAG.
Cheers!
Cenk
On 04/14/2016 09:44 AM, Mateusz Kubaszek wrote:
Hi Kaspar,
than you for your
Hello Carsten,
Thank you for the hint.
CircleCI looks nice, but its free plan includes only one (concurrent)
build at a time.
I think this won't help much in our case (:
Currently, we have about 11 jobs that need to be processed before one
pull request can be marked as "checked". And each job
Dear hard-working Developers,
I just wanted to share with you the chart in [1]
with the caption "Active Linux Builds for Open Source Projects (GCE)"
All our current jobs are build on that infrastructure and looking at the
chart:
travis is pretty flat-lining. It seems that there are more jobs
Dear Developers,
This is a friendly reminder that we should take more care
of our travis backlog.
Everytime a pull request gets rebased/squashed/new commits
travis will enqueue a new task. This enqueing takes up space
in the travis backlog and hinders us from getting quick feedback
about
Hello Francisco,
we have some problems with the hardware (:
Should be back online in a jiffy
On 26.01.2016 18:01, Francisco Javier Acosta Padilla wrote:
Hi there!
I'm trying to join the PlaceCam session but it says that Riot is not
online... Is the participation closed?
Thanks!
Francisco.
The PlaceCam session is online again. The link is the same.
On 26.01.2016 18:03, Cenk Gündogan wrote:
Hello Francisco,
we have some problems with the hardware (:
Should be back online in a jiffy
On 26.01.2016 18:01, Francisco Javier Acosta Padilla wrote:
Hi there!
I'm trying to join
Correction, in Berlin the Hack'n'Ack will not be at the c-base, but at
the FU Berlin (room 137 in Takustr. 9)
Best,
Cenk
On 25.01.2016 17:00, Google Calendar wrote:
more details »
Hello Francisco,
You do not need RPL for your setup:
* Start your border router application and tunslip6 (e.g. beef::1/64)
* configure beef::2/64 on interface 6 at the border router and
add beef::1 to the neighbor cache on interface 6
(these steps are outlined in the border router README)
*
Hello Martine,
I also want to add and stress that we should make proper use of
the "Hack'n'ACK Candidate" label in GitHub to find those "5-10"
PRs during the Hack'n'ACK.
In general, I also think that there is room for optimization regarding
the way we deal with Hack'n'ACKs currently and I like
Dear RIOT developers and users,
I am glad to announce the sixth official release of the RIOT operating
system:
--- * RIOT 2015.12 *
---
This release is packed with nearly 150 enhancements to the codebase and
bugfixes
for several
Hello Sugang,
Can you try the pins PA23(RX pin) and PA22(TX pin)?
PA04 and PA05 share the same UART with the shell.
I hope this helps.
Best,
Cenk
On 08.12.2015 17:29, Sugang Li wrote:
Hi Oleg,
Sorry that I come back to this question so late. After a few trials,
I still have the following
Hey everyone,
I just noticed that travis ignores a pull request if the latest commit
includes "[ci skip]" anywhere
in the commit message.
This is great for commits that are intended to be squashed anyways.
Otherwise, travis keeps queueing a pull request after every commit only
to quit
the
Hello Haoyang,
MODULE_* macros will be generated from the `USEMODULE` and `USEPKG`
variables. [1]
Best,
Cenk
[1] https://github.com/RIOT-OS/RIOT/blob/master/Makefile.modules#L7
On 23.11.2015 04:01, Haoyang Yu wrote:
Hi Martine,
I understood the idea behind the concept. Thank you very
Hello Haoyang,
`gnrc_netif_default` is a pseudo module and defined in
`Makefile.pseudomodules`.
In `Makefile.dep` you can see that it pulls in `gnrc_netif` as a dependency.
Best,
Cenk
On 18.11.2015 04:19, Haoyang Yu wrote:
Hi Oleg,
I do cannot find any Makefile claim this module as the
Hello Haoyang,
Please have a look at [1] for a quick tutorial on using RPL in RIOT.
Out of curiosity: what kind of hardware do you use to build your sensor
network?
Cheers,
Cenk
[1]
https://github.com/RIOT-OS/RIOT/wiki/Tutorial:-RIOT-and-Multi-Hop-Routing-with-RPL
On 29.10.2015 06:41,
+1
minor remark:
I would prefer writing `pull request` with lowercase letters. I couldn't
find any significant occurences on google, where `pull request` is
written with capital letters. It's fine for the subject, though. But
then again, I would insist on also capitalizing `Creating` and
Hi Oleg,
Out of curiosity (and maybe to state the obvious):
The rules you proposed would forbid WIP pull requests, right?
On 20.08.2015 19:10, Cenk Gündogan wrote:
Hey Oleg,
I like your proposed guideline.
What's your opinion on adding some words about logically splitting a
PR across
Hey,
As far as I'm concerned the mqtt-sn implementation
that Ludwig and me started a while back can be labled as Work In
No-Progress.
We never went beyond some header definitions, because the gnrc network
stack was still transitioning. So feel free to port mqtt-sn or adopt
Ludwig's branch.
Hello Lennart,
On 25.06.2015 16:14, Lennart Dührsen wrote:
the method you suggested now works halfway for me, but I still can't
that's half the battle (:
linux~ nc -u fe80::b400:b1ff:fe63:f33d%tap0 54545
Using nc without the -l flag will start a udp client and connect to the
riot server. You
Hello Alexandru,
I am not certain that this method is bullet-proof, but you can try the
following:
* Create a tun/tap interface:
sudo openvpn --mktun --dev tap0
[FYI: I did not test this method with the tapsetup script]
* Enable the interface:
sudo ip link set dev tap0 up
* start
Hello Lennart,
I might be wrong and Sebastian might be able to shed some light on this, BUT
isn't marz restricted to the old network stack? As far as I know it
strips/adds the old nativenet header from outgress/ingress packets.
BTW, are you also using the old network stack? My described
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
Hi,
unrelated to RIOT, but for the sake of completeness, there is also the
native git command `git request-pull` [1], which let's you generate a
pull request message that you can send per email to e.g. a mailing list.
[1] http://git-scm.com/docs/git-request-pull
Best,
Cenk
On 04.02.2015
Hi Steve!
The default routing table size is at 128 entries, that's too much for
the samr21-xrpo :)
Can you try the following:
BOARD=samr21-xpro make clean all RPL_MAX_ROUTING_ENTRIES=6
and see how this works out for you?
You can even play a little bit around with the entry size, maybe you
25 matches
Mail list logo
