I have followed the CoAP example from IoT SDK, I have a Raspberry PI set up as the router, and two nRF52 boards, one is the client, the other is the server.
Following instructions I manage to change LEDs (on/off) of the server, by pressing the buttons on the client.
But now I'm trying to use the client from my PC (Windows) using Mozilla's CoAP client implementation, and although I navigate to correct path, I don't see the lights led3 and led4 there, as they're shown in the example image.
Also if I try to ping from my PC, the client or the server board I cannot do it, what seems to be the problem?
##update 1
Here is the info:
radvd.conf
interface bt0
{
AdvSendAdvert on;
prefix 2001:db8::/64
{
AdvOnLink off;
AdvAutonomous on;
AdvRouterAddr on;
};
};
ifconfig
bt0 Link encap:UNSPEC HWaddr 00-1A-7D-FF-FE-DA-71-08-00-00-00-00-00-00-00-00
inet6 addr: 2001:db8::1/64 Scope:Global
inet6 addr: 2001:db8::21a:7dff:feda:7108/64 Scope:Global
inet6 addr: fe80::21a:7dff:feda:7108/64 Scope:Link
UP POINTOPOINT RUNNING MULTICAST MTU:1280 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1661 (1.6 KiB) TX bytes:4523 (4.4 KiB)
eth0 Link encap:Ethernet HWaddr b8:27:eb:f4:dd:1e
inet addr:192.168.11.221 Bcast:192.168.11.255 Mask:255.255.255.0
inet6 addr: fe80::1d1d:8327:1679:29ec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1128702 errors:0 dropped:4238 overruns:0 frame:0
TX packets:41571 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:175303947 (167.1 MiB) TX bytes:7370884 (7.0 MiB)
route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
::1/128 :: U 256 0 0 lo
2001::/64 :: U 1 0 0 eth0
2001:db8::/64 :: U 256 1 18 bt0
fe80::/64 :: U 256 1 109 eth0
fe80::/64 :: U 256 1 8 bt0
::/0 :: !n -1 1 500 lo
::1/128 :: Un 0 2 12 lo
2001:db8::/128 :: Un 0 1 0 lo
2001:db8::1/128 :: Un 0 2 15 lo
2001:db8::21a:7dff:feda:7108/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::21a:7dff:feda:7108/128 :: Un 0 1 0 lo
fe80::1d1d:8327:1679:29ec/128 :: Un 0 2 164 lo
ff00::/8 :: U 256 1117832 eth0
ff00::/8 :: U 256 1 15 bt0
::/0 :: !n -1 1 500 lo
Server board:
fe80::250:46ff:fe72:2b55 - nrf52 SERVER
echo "connect 00:50:46:72:2b:55 1" > /sys/kernel/debug/bluetooth/6lowpan_control
00:50:46:72:2b:55 - BT address
2001:db8::250:46ff:fe72:2b55 - GLOBAL
Client board:
00:a9:c1:b9:f1:9f - nrf52 (other board) BT Address CLIENT
echo "connect 00:a9:c1:b9:f1:9f 1" > /sys/kernel/debug/bluetooth/6lowpan_control
ping6 -I bt0 fe80::2a9:c1ff:feb9:f19f
2001:db8::2a9:c1ff:feb9:f19f
If I do ping6 2001:db8::250:46ff:fe72:2b55
or ping6 -I bt0 fe80::250:46ff:fe72:2b55
from the RasPi, I can ping the server, also same goes for the client
If enter from my Windows PC: ping -6 fe80::1d1d:8327:1679:29ec
(eth0 RasPi address) it works, but if I try to ping the server from PC like this: ping -6 2001:db8::250:46ff:fe72:2b55
it fails