Re: [riot-devel] GNRC_NETWORKING
Hi again, The problem is probably on the Br, after sending two udp messages, 4 bytes each with two minutes difference, I am not able to see the node in the br's ncache. I am using the br of miri64, I can't find the email where she mentioned that the br doesn't remove records. Anyone using the br without problems? Thank you in advance! On Sep 21, 2016 15:56, "Ilias Seitanidis" wrote: > @ Sebastian the first one is the udp.c where I execute an interval so > every 2 minutes I send a message. The second one is empty right now. > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] GNRC_NETWORKING
@ Sebastian the first one is the udp.c where I execute an interval so every 2 minutes I send a message. The second one is empty right now. ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] GNRC_NETWORKING
Thank you all for your replies, @Sebastian, I have the loop in the udp.c and when I use the make term I see that one of my threads is running. That's the strange thing!!! ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] GNRC_NETWORKING
Hi Oleg, you're probably right; I also missed that and also ignored Ilias statement: > After that I execute some threads. @Ilias: what are those threads doing, are they working as expected? Best, Sebastian > Am 21.09.2016 um 15:13 schrieb Oleg Hahm : > > Hi Sebastian! > > On Wed, Sep 21, 2016 at 02:50:31PM +0200, smlng wrote: >> you removed the shell, and doing so you also removed the main loop. So >> basically your program hits return 0 and terminates - which likely happens >> very fast after reboot. With this the RIOT-Kernel, network stack and >> everything stops working, so no logic remains to answer any pings or so. > > This shouldn't happen - and a quick test revealed that it is indeed not > happening. From the RIOT perspective main is basically a normal thread. If it > terminates, the kernel will just removes it from the list of scheduled threads > and continues as usual. Hence, all other threads should keep running. > > Cheers, > Oleg > -- > /* Identify the flock of penguins. */ >linux-2.2.16/arch/alpha/kernel/setup.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
Re: [riot-devel] GNRC_NETWORKING
Hi Sebastian! On Wed, Sep 21, 2016 at 02:50:31PM +0200, smlng wrote: > you removed the shell, and doing so you also removed the main loop. So > basically your program hits return 0 and terminates - which likely happens > very fast after reboot. With this the RIOT-Kernel, network stack and > everything stops working, so no logic remains to answer any pings or so. This shouldn't happen - and a quick test revealed that it is indeed not happening. From the RIOT perspective main is basically a normal thread. If it terminates, the kernel will just removes it from the list of scheduled threads and continues as usual. Hence, all other threads should keep running. Cheers, Oleg -- /* Identify the flock of penguins. */ linux-2.2.16/arch/alpha/kernel/setup.c signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] GNRC_NETWORKING
Hi Ilias, you removed the shell, and doing so you also removed the main loop. So basically your program hits return 0 and terminates - which likely happens very fast after reboot. With this the RIOT-Kernel, network stack and everything stops working, so no logic remains to answer any pings or so. I don't know what your goal is, but if you look at the microcoap example here [0] (line 44-47), you'll see it does the same: no shell and it has this _netif_config line, too. But instead of hitting return 0 it enters `microcoap_server_loop()` which keeps running forever. Best, Sebastian [0]: https://github.com/RIOT-OS/RIOT/blob/master/examples/microcoap_server/main.c > Am 21.09.2016 um 14:42 schrieb Ilias Seitanidis : > > Hi all, > > I am using the gnrc BR and I have another node running the gnrc_networking > example. I did some modifications on the main.c of the gnrc_networking, I > replaced the lines 44-46 [1] with the line: _netif_config(0, NULL); . After > that I execute some threads. My question is why I cannot ping the node > running the gnrc_networking example with this modifications I did. Moreover, > I can't see the node on the ncache of the BR. I was able to ping and see the > node in BR's ncache when I used the gnrc_networking example as it is. Any > suggestions??? > Thank you in advance! > > [1] > https://github.com/RIOT-OS/RIOT/blob/master/examples/gnrc_networking/main.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
[riot-devel] GNRC_NETWORKING
Hi all, I am using the gnrc BR and I have another node running the gnrc_networking example. I did some modifications on the main.c of the gnrc_networking, I replaced the lines 44-46 [1] with the line: _netif_config(0, NULL); . After that I execute some threads. My question is why I cannot ping the node running the gnrc_networking example with this modifications I did. Moreover, I can't see the node on the ncache of the BR. I was able to ping and see the node in BR's ncache when I used the gnrc_networking example as it is. Any suggestions??? Thank you in advance! [1] https://github.com/RIOT-OS/RIOT/blob/master/examples/gnrc_networking/main.c ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] gnrc_networking packets incoming
Hi Alessandro, gnrc_networking registers the "pkt_dump" module as UDP server. https://github.com/RIOT-OS/RIOT/blob/master/examples/gnrc_networking/udp.c#L108 You can find the implementation here: https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/pktdump/gnrc_pktdump.c . Just write your own minimal server and register its pid instead of the pkt_dump module. You should additionally remove USEMODULE += gnrc_pktdump from the Makefile. Best Peter Am 27.08.2016 um 16:02 schrieb ALESSANDRO NICOLI: Hi all, In case that i could not use CoAP for request messages, i tried to build on a communication using the "gnrc_networking" code. Obviously the communication works, but where and how can i retrive the payload of the incoming packets? My collector node (SAMR21) has to process the content of the incoming packets from DHT sensor node (this is SAMR21 too). thanks all, *best regards, * *Alessandro* ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel -- Peter Kietzmann Hamburg University of Applied Sciences Dept. Informatik, Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49-40-42875-8426 Web: http://www.haw-hamburg.de/inet ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] gnrc_networking packets incoming
Hi all, In case that i could not use CoAP for request messages, i tried to build on a communication using the "gnrc_networking" code. Obviously the communication works, but where and how can i retrive the payload of the incoming packets? My collector node (SAMR21) has to process the content of the incoming packets from DHT sensor node (this is SAMR21 too). thanks all, *best regards, * *Alessandro* ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
