Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6LOWPAN ON SAMR21 Device #4855

Closed
girisugu2 opened this issue Feb 20, 2016 · 94 comments
Closed

6LOWPAN ON SAMR21 Device #4855

girisugu2 opened this issue Feb 20, 2016 · 94 comments
Assignees
Labels
Type: question The issue poses a question regarding usage of RIOT

Comments

@girisugu2
Copy link

Hi I am new to this,
I am using two SAMR21-xpro boards.
I want to connect two boards automatically.For that i tried gnrc_networking.i tried rpl configurations to set parent and child nodes.But i don't know how to communicate over 6lowpan.please guide me.
Thanks in Advance.

With Regards,
R.Giritharan

@cgundogan
Copy link
Member

But i don't know how to communicate over 6lowpan.please guide me.

What exactly do you mean by communicate over 6lowpan?
You can start a udp server on both nodes with udp server start 8888 and then send udp packets to another node via udp send <ip_addr> 8888 test. You can obtain the ip addresses via ifconfig.
The udp transmission will use 6lowpan, as this is the default for the transceiver you are using.
You can also test your connection by using the ping command. ping <ip_addr>. This will also use 6lowpan.

Could you make your question more specific with regard to what you want to transmit over 6lowpan?

@cgundogan cgundogan added the Type: question The issue poses a question regarding usage of RIOT label Feb 28, 2016
@girisugu2
Copy link
Author

Hi I am new to RIOT.

              I have two SAMR21-XPRO Devices.I am using RIOT OS to

communicate between two board.I tried RPL Routing for mesh network.I set up
one device is parent and another is child by RPL networking.I tried this
link
to set up RPL (https://github.com/RIOT-OS/RIOT/wiki/Tutorial%3A-RIOT-and-
Multi-Hop-Routing-with-RPL).As per the above link all are working fine for
me.
My question is i want to communicate my parent node to wifi or ethernet
based
devices.For that which device i can use.I think boarder router is used to
convert ipv6 to ipv4 or vice versa.So for boarder router which device
shall i
use to communicate with samr21.
I am confusing over this.Please help me to find out the right solution.
Thanks in advance.

With Regards,
R.Giritharan

@miri64
Copy link
Member

miri64 commented Feb 28, 2016

Sorry for sounding a little pissed, but it's neither helpful for any of us nor will it speed up "our process" if you just repeat the question over and over again. So please answer my question (and the questions posted to your other posts on both devel ML and here): What setup do you use? What pins did you connect your second UART to (which is needed for the process described in )? What prefix did you use? How did you configure the border router (you need to connect over /dev/ttyACMx for configuration)? And did you look into #4725, which simplifies a lot of bootstrapping and doesn't require you to open a second UART?

I think boarder router is used to convert ipv6 to ipv4 or vice versa.

There is currently no dual stacking in RIOT, we only have IPv6 support for now. The border router is just there to translate IPv6 over IEEE 802.15.4 (6LoWPAN) to IPv6 over X (Ethernet, SLIP, WiFi, you name it). If you don't have an IPv6 connection: There are tunnel brokers that provide 6in4 tunneling or can find a number of other solutions using your own tunneling solution on Linux.

@girisugu2
Copy link
Author

ok ,i will explain my steps below,
1.>I tried boarder router as per the readme file in RIOT/examples/gnrc_boarder_router.
As per the read me file everything works fine for me.(sudo ./tunslip6 affe::1/64 -t tun0 -s /dev/ttyUSB0)which opens the tunslip terminal.I can able to send messages from RIOT terminal to tunslip using txtsnd command.Even i can ping the affe::1 address which is configured in tunslip.

2.>And next is gnrc_networking.
In this a.> i set the global IP adress in one board(root node).
b.>Then initializes the rpl init in root node.
c.>set the rpl init 2008::dead in root node i.e parent node
d.>After that in another node i.e child node i start the rpl init.
e.>So finally i create parent node and child node as per the rpl routing.

So finally,
My Question is,
I want to ping the child IP from linux PC i.e Outside world(for that only i use boarder router).So after that i want to communicate from outside world to child node via parent node.

So how can i do that one?
how to push my data's to internet?
please help me...
Thanks in advance!

With Regards,
R.Giritharan

@cgundogan
Copy link
Member

I am just wondering: did you also do ifconfig 6 add affe::2 and ncache add 6 affe::1 like described in the README for the border router example? Is the 2001:dead:: prefix propagated correctly, i.e. does the child node get a global ip address on its interface after configuring the 2001:dead::X address on interface 5 of the border router?

BTW: we noticed that the current setup is not quite straight forward and we are working on an enhancement of the border router setup in #4725

@girisugu2
Copy link
Author

Thankyou for your reply,

I have only two samr21-xpro devices.
So i used that two devices for gnrc_networking for RPL setup(Parent node and child node).

So with this two devices how can i push the data's to internet (server).
I don't know how to do exactly.Here below i explain what i did exactly.

I want to control(send and receive) messages over internet via ethernet based devices or wifi.
So for now , what i did is,
i set up RPL (parent and child nodes)gnrc_networking.And after that i opened the tunslip in linux pc using SAMR21 UART.So i configure the global ip 2008::dead or something else in tunslip and RIOT terminal(parent node).
So my doubt is how to ping child node ip from linux pc using ping6 command.
what is the exact solution for my question?
Thanks in Advance!
With Regards,
R.Giritharan

@cgundogan
Copy link
Member

@girisugu2 you need to flash the gnrc_border_router example on one of the samr21-xpro boards. Currently, without modifying any Makefiles, you need to connect a second UART to your border router on PA23 (RX) and PA22 (TX). When you call sudo ./tunslip6 affe::1/64 -t tun0 -s /dev/ttyUSB0, then /dev/ttyUSB0 needs to refer to this second UART that you connected additionally. After this setup, it's just following the README.

Once #4725 is merged (hopefully today), this process will be simplified a lot and you won't need the second UART. So stay tuned!

@cgundogan cgundogan self-assigned this Mar 1, 2016
@girisugu2
Copy link
Author

Thanks for your reply.
I tried this already.gnrc_boarder_router.
My Question is how to ping my child ip from linux pc...I am working on gnrc_networking for set up parent child nodes.

@cgundogan
Copy link
Member

are you able to ping from the parent to the child?

@cgundogan
Copy link
Member

Honestly, I do not understand your current setup:
Let's break it down:

You have two samr21-xpros.
One of them uses the gnrc_border_router example.
The other one uses the gnrc_networking example.

RPL is not included in the gnrc_border_router example by default. Did you add rpl to the Makefile?
BTW, your current setup with two nodes works completely without RPL. The prefix will be announced from the border router to the 6lowpan router via Prefix Information Options within the Router Advertisements (so, basically, automagically)

@cgundogan
Copy link
Member

Could you please show us the output of ifconfig on both of your nodes after setting up everything?

@cgundogan
Copy link
Member

And while we are at it, the output of ncache could also be interesting from both samr21-xpro boards.

@girisugu2
Copy link
Author

I here attach both board's log(BOARD A and BOARD B)
Both are configured gnrc_networking

BOARD A
RIOT/examples/gnrc_networking$ sudo make BOARD=samr21-xpro term
RIOT/dist/tools/pyterm/pyterm -p "/dev/ttyACM0" -b "115200"
2016-03-01 14:19:41,978 - INFO # Connect to serial port /dev/ttyACM0
Welcome to pyterm!
Type '/exit' to exit.
ifconfig
2016-03-01 14:20:38,888 - INFO # > ifconfig
2016-03-01 14:20:38,893 - INFO # Iface 7 HWaddr: 47:52 Channel: 26 Page: 0 NID: 0x23
2016-03-01 14:20:38,897 - INFO # Long HWaddr: 5a:5a:41:6d:64:67:c7:52
2016-03-01 14:20:38,904 - INFO # TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4
2016-03-01 14:20:38,910 - INFO # AUTOACK CSMA MTU:1280 HL:64 6LO RTR IPHC
2016-03-01 14:20:38,913 - INFO # Source address length: 8
2016-03-01 14:20:38,915 - INFO # Link type: wireless
2016-03-01 14:20:38,921 - INFO # inet6 addr: ff02::1/128 scope: local [multicast]
2016-03-01 14:20:38,926 - INFO # inet6 addr: fe80::585a:416d:6467:c752/64 scope: local
2016-03-01 14:20:38,933 - INFO # inet6 addr: ff02::1:ff67:c752/128 scope: local [multicast]
2016-03-01 14:20:38,934 - INFO #

set global ip

ifconfig 7 add 2001:db8::1
2016-03-01 14:21:20,012 - INFO # > ifconfig 7 add 2001:db8::1
2016-03-01 14:21:20,013 - INFO # success: added 2001:db8::1/64 to interface 7

Initializing RPL

rpl init 7
2016-03-01 14:21:32,672 - INFO # > rpl init 7
2016-03-01 14:21:32,676 - INFO # successfully initialized RPL on interface 7

Configure RPL

rpl root 1 2001:db8::1
2016-03-01 14:21:46,506 - INFO # > rpl root 1 2001:db8::1
2016-03-01 14:21:46,509 - INFO # successfully added a new RPL DODAG

RPL Result

rpl
2016-03-01 14:26:15,453 - INFO # rpl
2016-03-01 14:26:15,454 - INFO # instance table: [X]
2016-03-01 14:26:15,457 - INFO # parent table: [ ] [ ] [ ]
2016-03-01 14:26:15,457 - INFO #
2016-03-01 14:26:15,461 - INFO # instance [1 | mop: 2 | ocp: 0 | mhri: 256 | mri 0]
2016-03-01 14:26:15,470 - INFO # dodag [2001:db8::1 | R: 256 | OP: Router | PIO: on | CL: his | TR(I=[0,8], k=20, c=10, TC=1s, TI=8s)]
ping6 fe80::5855:5064:9977:23ca(child IP i.e BOARD B)
2016-03-01 14:28:13,793 - INFO # ping6 fe80::5855:5064:9977:23ca
2016-03-01 14:28:13,808 - INFO # 12 bytes from fe80::5855:5064:9977:23ca: id=83 seq=1 hop limit=64 time = 8.223 ms
2016-03-01 14:28:14,827 - INFO # 12 bytes from fe80::5855:5064:9977:23ca: id=83 seq=2 hop limit=64 time = 8.855 ms
2016-03-01 14:28:15,843 - INFO # 12 bytes from fe80::5855:5064:9977:23ca: id=83 seq=3 hop limit=64 time = 6.944 ms
2016-03-01 14:28:15,847 - INFO # --- fe80::5855:5064:9977:23ca ping statistics ---
2016-03-01 14:28:15,853 - INFO # 3 packets transmitted, 3 received, 0% packet loss, time 2.0646154 s
2016-03-01 14:28:15,857 - INFO # rtt min/avg/max = 6.944/8.007/8.855 ms

BOARD B

RIOT/dist/tools/pyterm/pyterm -p "/dev/ttyACM1" -b "115200"
2016-03-01 14:20:28,564 - INFO # Connect to serial port /dev/ttyACM1
Welcome to pyterm!
Type '/exit' to exit.
ifconfig
2016-03-01 14:20:33,384 - INFO # ifconfig
2016-03-01 14:20:33,393 - INFO # Iface 7 HWaddr: 23:ca Channel: 26 NID: 0x23 TX-Power: 0dBm State: IDLE CSMA Retries: hu
2016-03-01 14:20:33,397 - INFO # Long HWaddr: 5a:55:50:64:99:77:23:ca
2016-03-01 14:20:33,402 - INFO # AUTOACK CSMA MTU:1280 HL:hu 6LO RTR IPHC
2016-03-01 14:20:33,405 - INFO # Source address length: 8
2016-03-01 14:20:33,408 - INFO # Link type: wireless
2016-03-01 14:20:33,413 - INFO # inet6 addr: ff02::1/hu scope: local [multicast]
2016-03-01 14:20:33,419 - INFO # inet6 addr: fe80::5855:5064:9977:23ca/hu scope: local
2016-03-01 14:20:33,425 - INFO # inet6 addr: ff02::1:ff77:23ca/hu scope: local [multicast]
2016-03-01 14:20:33,426 - INFO #
rpl init 7
2016-03-01 14:22:01,224 - INFO # > rpl init 7
2016-03-01 14:22:01,228 - INFO # successfully initialized RPL on interface 7
rpl
2016-03-01 14:22:04,742 - INFO # > rpl
2016-03-01 14:22:04,744 - INFO # instance table: [X]
2016-03-01 14:22:04,746 - INFO # parent table: [X] [ ] [ ]
2016-03-01 14:22:04,747 - INFO #
2016-03-01 14:22:04,751 - INFO # instance [1 | mop: 2 | ocp: 0 | mhri: 256 | mri 0]
2016-03-01 14:22:04,759 - INFO # dodag [2001:db8::1 | R: 512 | OP: Router | CL: his | TR(I=[0,8], k=20, c=10, TC=lus, TI=lus)]
2016-03-01 14:22:04,766 - INFO # parent [addr: fe80::585a:416d:6467:c752 | rank: 256 | lifetime: 119s]
ping6 fe80::585a:416d:6467:c752(parent IP i.e BOARD A)
2016-03-01 14:27:23,801 - INFO # > ping6 fe80::585a:416d:6467:c752
2016-03-01 14:27:23,817 - INFO # 12 bytes from fe80::585a:416d:6467:c752: id=83 seq=1 hop limit=hu time = 64.008 ms
2016-03-01 14:27:24,834 - INFO # 12 bytes from fe80::585a:416d:6467:c752: id=83 seq=2 hop limit=hu time = 64.008 ms
2016-03-01 14:27:25,851 - INFO # 12 bytes from fe80::585a:416d:6467:c752: id=83 seq=3 hop limit=hu time = 64.008 ms
2016-03-01 14:27:25,855 - INFO # --- fe80::585a:416d:6467:c752 ping statistics ---
2016-03-01 14:27:25,861 - INFO # 3 packets transmitted, 3 received, 0% packet loss, time 2.0648265 s
2016-03-01 14:27:25,864 - INFO # rtt min/avg/max = 8.227/8.650/8.866 ms

@cgundogan
Copy link
Member

Both are configured gnrc_networking

This does not work. One of the samr21-xpro boards needs to be flashed with the gnrc_border_router example in order to achieve what you desire.

@girisugu2
Copy link
Author

ok Fine.But if i use one as gnrc_boarder_router how can i set up as parent and child nodes.

@girisugu2
Copy link
Author

So no need RPL?

@cgundogan
Copy link
Member

You can omit RPL for your use case with two samr21-xpros. If you really need multi-hop on the lowpan side, then you can include the rpl module in the Makefile of the gnrc_border_router example, but AFAIK, this was never tested. The boder router might get confused with the additional fib entries of RPL.

@cgundogan
Copy link
Member

The boder router might get confused with the additional fib entries of RPL.

@OlegHahm do you have something smart to say for this matter? (:

@OlegHahm
Copy link
Member

OlegHahm commented Mar 1, 2016

I'm not smart.

@OlegHahm
Copy link
Member

OlegHahm commented Mar 1, 2016

But in general, I see no problem with RPL on the 6LBR and I think @kYc0o have even tried.

@girisugu2
Copy link
Author

ok let me explain clearly,

      IOT(INTERNET OF THINGS) means connect devices with internet.For that my project is home automation..So i have different samr21 boards(now for testing i have two samr21).

I want to control that two boards via internet.
For that i tried RIOT .So i tried gnrc_networking and gnrc_border_router examples.As per the reame files from border_router and gnrc_networking works perfectly for me.

I think upto this everything is ok.
So after that i want to communicate the SAMR21 boards to internet.So only for one device i think gnrc_networking is ok (to connect multiple nodes).
And to connect Parent node to IOT server gnrc_border_router is the only choice i think.
The border_router converts radio device datas to normal internet .

This is my requirement.
So please tell me frankly about my ideas and your suggestions.

Thanks in advance
With Regards,
R.Giritharan

@girisugu2
Copy link
Author

I am wrong means please help how to do?

@cgundogan
Copy link
Member

@girisugu2 can you show me again your ìfconfig and ncache output of both nodes? But this time one of the nodes must the gnrc_border_router example (with all steps included that are outlined in the README of the border router example). The other node can be flashed with the gnrc_networking example.

@girisugu2
Copy link
Author

this is the gnrc_networking example...
how to configure ncache.
what is the use of ncache in RIOT
2016-03-01 15:18:29,063 - INFO # > ifconfig
2016-03-01 15:18:29,069 - INFO # Iface 7 HWaddr: 47:52 Channel: 26 Page: 0 NID: 0x23
2016-03-01 15:18:29,073 - INFO # Long HWaddr: 5a:5a:41:6d:64:67:c7:52
2016-03-01 15:18:29,080 - INFO # TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4
2016-03-01 15:18:29,085 - INFO # AUTOACK CSMA MTU:1280 HL:64 6LO RTR IPHC
2016-03-01 15:18:29,088 - INFO # Source address length: 8
2016-03-01 15:18:29,091 - INFO # Link type: wireless
2016-03-01 15:18:29,096 - INFO # inet6 addr: ff02::1/128 scope: local [multicast]
2016-03-01 15:18:29,102 - INFO # inet6 addr: fe80::585a:416d:6467:c752/64 scope: local
2016-03-01 15:18:29,108 - INFO # inet6 addr: ff02::1:ff67:c752/128 scope: local [multicast]
2016-03-01 15:18:29,109 - INFO #
ncache
2016-03-01 15:19:47,607 - INFO # ncache
2016-03-01 15:19:47,613 - INFO # IPv6 address if L2 address state type
2016-03-01 15:19:47,620 - INFO # ------------------------------------------------------------------------------

@girisugu2
Copy link
Author

One more doubt,
I i run gnrc_networking in one board,
gnrc_boarder_router in another means how to communicate between these two boards(gnrc_border_router to gnrc_networking).
Think in border router there is no UDP

@cgundogan
Copy link
Member

the more interesting part is the ifconfig and ncache output of the other node (; Did you connect your border router?

@cgundogan
Copy link
Member

Think in border router there is no UDP

we can talk about this once we connect your border router correctly to the linux machine

@girisugu2
Copy link
Author

no i didn't connect.
Ok what shall i do?
please give me the step by step procedures.
I will follow your guidence.
Now i will flash one board as gnrc_networking and another as gnrc_border_router ok

@cgundogan
Copy link
Member

can you show me the output of git rev-parse --verify HEAD and git rev-parse --abbrev-ref HEAD?

@girisugu2
Copy link
Author

where i need to give this command?

@cgundogan
Copy link
Member

from within the RIOT folder

@girisugu2
Copy link
Author

RIOT$ rev-parse --abbrev-ref HEAD
rev-parse: command not found

It shows command not found

@cgundogan
Copy link
Member

I edited my previous message, you need to include git in front of these commands

@girisugu2
Copy link
Author

oviya@oviya-Tech:/giritharan/IOT/RPL/RIOT$ git rev-parse --verify HEAD
562218d
oviya@oviya-Tech:
/giritharan/IOT/RPL/RIOT$ git rev-parse --abbrev-ref HEAD
master
oviya@oviya-Tech:~/giritharan/IOT/RPL/RIOT$

@girisugu2
Copy link
Author

oviya@oviya-Tech:~/giritharan/IOT/RPL/RIOT$ git rev-parse --verify HEAD
562218d

@cgundogan
Copy link
Member

can you do a git pull?

@girisugu2
Copy link
Author

oviya@oviya-Tech:~/giritharan/IOT/RPL/RIOT$ git pull
remote: Counting objects: 6733, done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 6733 (delta 2273), reused 2272 (delta 2270), pack-reused 4449
Receiving objects: 100% (6733/6733), 1.71 MiB | 1.10 MiB/s, done.
Resolving deltas: 100% (4601/4601), completed with 775 local objects.
From https://github.com/RIOT-OS/RIOT
562218d..754a028 master -> origin/master
7840174..0fbb0af 2015.09-branch -> origin/2015.09-branch

  • [new branch] 2015.12-branch -> origin/2015.12-branch
  • [new tag] 2015.12 -> 2015.12
  • [new tag] 2015.12-RC1 -> 2015.12-RC1
  • [new tag] 2015.12-RC2 -> 2015.12-RC2
  • [new tag] 2015.12-RC3 -> 2015.12-RC3
  • [new tag] 2015.12-RC4 -> 2015.12-RC4
  • [new tag] 2016.03-devel -> 2016.03-devel
    Updating 562218d..754a028
    error: Your local changes to the following files would be overwritten by merge:
    README.md
    sys/net/gnrc/pktdump/gnrc_pktdump.c
    Please, commit your changes or stash them before you can merge.
    Aborting
    oviya@oviya-Tech:~/giritharan/IOT/RPL/RIOT$

@cgundogan
Copy link
Member

if your changes to sys/net/gnrc/pktdump/gnrc_pktdump.c are not important then just do a git pull -f. Otherwise do a git stash before a git pull

@girisugu2
Copy link
Author

oviya@oviya-Tech:/giritharan/IOT/RPL/RIOT$ git pull -f
Updating 562218d..754a028
error: Your local changes to the following files would be overwritten by merge:
README.md
sys/net/gnrc/pktdump/gnrc_pktdump.c
Please, commit your changes or stash them before you can merge.
Aborting
oviya@oviya-Tech:
/giritharan/IOT/RPL/RIOT$

@girisugu2
Copy link
Author

oviya@oviya-Tech:/giritharan/IOT/RPL/RIOT$ git stash
Saved working directory and index state WIP on master: 562218d Merge pull request #4369 from haukepetersen/fix_saul_typos
HEAD is now at 562218d Merge pull request #4369 from haukepetersen/fix_saul_typos
oviya@oviya-Tech:
/giritharan/IOT/RPL/RIOT$

@cgundogan
Copy link
Member

great, now try again a git pull.

@girisugu2
Copy link
Author

It shows ver big files.But i copied only 1/4th for your reference

oviya@oviya-Tech:~/giritharan/IOT/RPL/RIOT$ git pull
Updating 562218d..754a028
Fast-forward
.gitattributes | 1 +
.gitignore | 9 +
.strider.yml | 6 +-
.travis.yml | 43 +-
Makefile.buildtests | 106 +-
Makefile.defaultmodules | 2 +-
Makefile.dep | 43 +-
Makefile.docker | 1 +
Makefile.include | 1 -
Makefile.modules | 2 +
Makefile.pseudomodules | 2 +
README.md | 13 +-
Vagrantfile | 58 +
boards/Makefile.include.cortexm_common | 56 -
boards/Makefile.include.msp430_common | 21 -
boards/airfy-beacon/Makefile | 3 +-
boards/airfy-beacon/Makefile.features | 4 +-
boards/airfy-beacon/Makefile.include | 3 -
boards/airfy-beacon/board.c | 2 +-
boards/airfy-beacon/include/board.h | 30 +-
boards/airfy-beacon/include/periph_conf.h | 7 -
boards/arduino-due/Makefile | 7 +-
boards/arduino-due/Makefile.features | 4 +-
boards/arduino-due/Makefile.include | 3 -
boards/arduino-due/include/arduino_board.h | 123 +
boards/arduino-due/include/arduino_pinmap.h | 160 +-
boards/arduino-due/include/board.h | 14 -
boards/arduino-due/include/periph_conf.h | 247 +-
boards/arduino-mega2560/Makefile | 2 +-
boards/arduino-mega2560/Makefile.include | 16 +-
boards/arduino-mega2560/board.c | 2 +
boards/arduino-mega2560/include/board.h | 12 +-
boards/arduino-mega2560/include/periph_conf.h | 7 +
boards/avsextrem/Makefile | 2 +-
boards/avsextrem/Makefile.include | 1 -
boards/avsextrem/drivers/Makefile | 2 +-
boards/avsextrem/drivers/avsextrem-smb380.c | 19 +-
boards/avsextrem/drivers/avsextrem-ssp0.c | 3 +-
boards/avsextrem/include/board.h | 9 -
boards/cc2538dk/Makefile | 3 +-
boards/cc2538dk/Makefile.features | 2 +-
boards/cc2538dk/Makefile.include | 3 -
boards/cc2538dk/board.c | 4 -
boards/cc2538dk/include/board.h | 14 -
boards/cc2538dk/include/periph_conf.h | 9 +-
boards/chronos/Makefile | 3 +-
boards/chronos/Makefile.include | 3 +-
boards/chronos/drivers/Makefile | 2 +-
boards/chronos/include/board.h | 12 -
boards/ek-lm4f120xl/Makefile | 3 +-
boards/ek-lm4f120xl/Makefile.features | 3 +-
boards/ek-lm4f120xl/Makefile.include | 5 +-
boards/ek-lm4f120xl/include/board.h | 9 -
boards/ek-lm4f120xl/include/periph_conf.h | 18 +-
boards/f4vi1/Makefile | 3 +-
boards/f4vi1/Makefile.features | 2 +-
boards/f4vi1/Makefile.include | 3 -
boards/f4vi1/include/board.h | 14 -
boards/f4vi1/include/periph_conf.h | 45 +-
boards/fox/Makefile | 2 +-
boards/fox/Makefile.include | 3 -
boards/fox/include/board.h | 14 -
boards/fox/include/periph_conf.h | 6 +-
boards/frdm-k64f/Makefile | 3 +-
boards/frdm-k64f/Makefile.features | 4 +-
boards/frdm-k64f/Makefile.include | 4 +-
boards/frdm-k64f/include/board.h | 20 +-
boards/frdm-k64f/include/periph_conf.h | 14 +-
boards/iotlab-m3/Makefile | 2 +-
boards/iotlab-m3/Makefile.include | 3 -
boards/iotlab-m3/include/board.h | 12 +-
boards/iotlab-m3/include/gpio_params.h | 3 +
boards/iotlab-m3/include/periph_conf.h | 6 +-
boards/limifrog-v1/Makefile | 2 +-
boards/limifrog-v1/Makefile.include | 3 -
boards/limifrog-v1/include/board.h | 15 -
boards/limifrog-v1/include/periph_conf.h | 57 +-
boards/mbed_lpc1768/Makefile | 3 +-
boards/mbed_lpc1768/Makefile.include

@cgundogan
Copy link
Member

ok looks fine.. could you rebuild the applications for the border router and the gnrc_networking node?

@girisugu2
Copy link
Author

yeah now its worked

@cgundogan
Copy link
Member

Great! Can we close this issue now?

@girisugu2
Copy link
Author

1.>currently i am able to ping parent node(gnrc_networking) from linux pc
parent node and child node is setup by rpl routing.So
Can i ping child node directly from the linux pc?
please advice me
2.>currently i can ping parent node in same linux pc(192.168.0.101).
But how do i can ping that parent node from outside world i.e another PC(another pc ip is 192.168.0.112)

@cgundogan
Copy link
Member

this goes beyond RIOT. You have to setup correct forwarding rules on your linux machines. I am not an expert at this topic ): However, RIOT does only support IPv6. So either your machines speak IPv6 along all hops, or you have an IPv4-IPv6 tunnel somewhere configured.

@PeterKietzmann
Copy link
Member

Question was answered. Closing this issue now.

@girisugu2
Copy link
Author

ok....thank you very much for your support..

@sarathsanthoss
Copy link

Hi,
I'm trying to do the microcoap server example(native board) , I just followed the steps what are all given in the README file... i got the global IP...if i'm trying to connect using copper plugin.... it showing host/network unreachable...
could you please explain if you know.....
thanks in advance...........

@miri64
Copy link
Member

miri64 commented Mar 15, 2016

microcoap only provides functionality for CoAP servers. For a client implementation you need to use libcoap.

@sarathsanthoss
Copy link

in that libcoap , there is not a proper guidence in README file . could you please guide me how to use that....

@miri64
Copy link
Member

miri64 commented Mar 16, 2016

I would have to look into the code myself (though I originally ported it I used it only for testing my port and that was years ago). @Lotterleben do you have any experience with libcoap (or know someone who does)?

@OlegHahm
Copy link
Member

@miri64
Copy link
Member

miri64 commented Mar 16, 2016

@OlegHahm that's using libcoap on Linux, right? We are talking about libcoap on RIOT.

@OlegHahm
Copy link
Member

Do we?

@sarathsanthoss
Copy link

Hi all,
can anyone guide me how to work the libcoap client and microcoap server for samr21-xpro board..... how to set the interface in radvd.conf file..that means for native tap0...for board what should i mention....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: question The issue poses a question regarding usage of RIOT
Projects
None yet
Development

No branches or pull requests

6 participants