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
Send message from host PC to networking boards via border_router #11534
Comments
On the first question: I think the consumption is the same, I am not entirelly sure, but I think by default the state of the AT86RF233 (in RIOT implementation) is RX_AACK_ON Second: The files here should give you a clue on how to get this information on your application: RIOT/sys/net/gnrc/pktdump/* |
@talalong consumption wise it doesn't make a big difference to open a UDP server or not. If you have strict energy requirements you might rethink some other components though.
Are you sure that
You register a UDP server. Have a look at the sock API or the implementation of the |
PS: Please indicate when your question was answered! |
First of all, thank you all for your answers:
@PeterKietzmann yes. after connecting using
Secondly:
adding A Simple UDP Echo Server into /gnrc_networking/udp.c, I am able to start my custom server via
|
@talalong your setups sounds good and you got many things right and working all ready. First, it is correct that you can only ping from host to samr21 node using addresses like TL;DR: try to use only global addresses or ULAs (IPv6 addresses for private and testing usage, starting with To receive UDP directly in your app you should use the |
@smlng Thank you for making the addressing clear. I have no more questions at this topic, now. So it's time to close it. Thanks again for making this great os. |
@PeterKietzmann, @smlng , @taherrera
using
Here
|
I don't think you'd have ever been able to ping the border router or end device from macos unless you added a route to macos to tell it to reach Adding a route on macos goes something like I've assumed that interface Also it's helpful in addition to Take note that the addresses I've quoted from you may have changed next time you restart things. |
@benemorius thanks for your answer. I did try to ping to |
I was not satisfied to encourage you to fundamentally change your setup just because I didn't understand your setup. I have duplicated your vagrant/macos setup to find out just what a working vagrant setup is actually supposed to look like in the first place.
Actually, yes. I found that Riot's vagrant configuration isn't compatible to support routing traffic past the vagrant guest linux to the vagrant host OS, thus it is not compatible to use with a border router. Probably this is just a little oversight that no one has taken notice of yet. For now, I'd recommend a setup that has nodejs and Riot's However in order to come to that conclusion it was necessary to understand what was actually keeping the setup from working, and indeed I was able to get the setup working with two important changes:
With these changes, it should put you in the situation which I believed you were in when I first replied, which is that you need only to configure a couple of routes:
I didn't double-check all of these commands and statements as well as I'd have liked. Please don't assume I made no errors or omissions. Also apparently the ubuntu version we're using for vagrant is so old that we must indeed use |
Hi @benemorius I am very appreciate your help. And also sorry for the late response, because I did try to understand what you pointed at. I did follow your steps and realized that I could only ping to |
Setup description:
I have two
samr21-xpro
boardsThe first
samr21(sam_router)
is runninggnrc_border_router
on it, connects to my host PC runningvagrant
on MacOSThe second
samr21(sam_node)
is runninggnrc_networking
on it, connects to power supplyI have pinged
sam_router
<->sam_node
back and forth successfully.And also ping from my host PC <->
sam_node
viasam_router
worked as well.using
ping6 2001:db8::blah::blah
My goal is to send a message from my host PC via
sam_router
to serveralsam_node(s)
.Here is my first though:
using
udp server start 8080
, I can start mysam_nodes
to listen to messages from client.(That meanssam_nodes
are going to burn more power from power supply, prove me wrong pls!)-> First questionUpdate!
Now, I can send message from host PC to
sam_node
viasam_router
usingnetcat
likenc -6uv 2001:db8::blah::blah 8808
(becauseping6 to fe80::ccf5:blah:blah%tap0 8080
did not work for me)And the output from
sam_node (server udp)
looks like this:-> My second question is: how do I get these messages in
main.c
?If my though is wrong, I would appreciate if you could tell me how I can do it. Thank you!
Ps: Im a beginner level at this. :(
The text was updated successfully, but these errors were encountered: