• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 73 subscribers
  • Views 3064 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 108762
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

can't connect the device running coap server example

horiebin

Hello, I set up the environment by This. Now I can ping the device on the raspberry pi. How ever, When I run the python client example on My ubuntu-14.04 and try to connect the bluetooth. the result is "aiocoap.error.RequestTimedOut".

I connect the rpi to my pc by a cable and each of them can ping each other. My connection is like this:

PC<-cable->RPI <-bluetooth->PCA10028
Parents
  • 0

    The FE80 is the link local prefix, so these are link local IPv6 addresses. This will only work on one link, for example the bt0 link, or the et0 link. To communicate between links you need to use a global prefix, to make a global IPv6 address. RADVD distributes these global prefixes.

    Please have a look at this question for how to set it up.

Reply
  • 0

    The FE80 is the link local prefix, so these are link local IPv6 addresses. This will only work on one link, for example the bt0 link, or the et0 link. To communicate between links you need to use a global prefix, to make a global IPv6 address. RADVD distributes these global prefixes.

    Please have a look at this question for how to set it up.

Children
Related
Terms of service