msolters
commented
8 years ago You're not seeing any wireless_input lines in your /var/log/6lbr.log. In my experience, that means your SLIP radio is not actually receiving any traffic from your node.
Are your nodes definitely being compiled with radio channel 26 (that's what 6LBR is expecting according to your .dat file) and PAN_ID of abcd? Does that COAP example which does show up in the neighbors list have different values for those two parameters?
tiagodiogo
laurentderu
hello all, i'm currently having issues while trying to communicate between the border router and the network nodes. in order to facilitate the exposure of my situation, i will start by doing and overview of my setup and what i have already working, folllowing with an explanation of my problem and some attemps to understand what is going on.
the following image shows an overview of my setup. the border router, slip-radio and coap client (6lbr-demo) have been built from the 6lbr develop branch. the coap client is firefox browser with the copper plugin the border router is a raspberry pi the slip radio and coap server are zolertia remotes
so far i believe i have managed to setup the 6lbr. my linux client network interfaces are properly configured:
i can access the web interface both from the border router and the linux client as seen in the following picture:
and my nvm.dat file looks like this:
the 6lbr recognizes what i believe is the slip-radio, as reachable:
but then... my node running the 6lbr-demo is never added to the list of neighbours nor is a route established towards him.
"maybe it's a hardware issue?"
i don't believe so, because if i switch the firmware of the network node with the er-rest-example coap server, the device is added and a route is established as seen in this picture:
but although a route is added, i cannot access the coap server resources:
and the node itself does not seem fully configured:
so my questions at this point are:
should not this setup be working? the border-router, slip-radio and 6lbr-demo (coap server) are all built from the 6lbr-develop branch.
what can be the cause of this lack of connectivity? i don't know what else to do at this point
if it helps, here is the 6lbr.log file (the one using the 6lbr-demo as coap server, which was not added to the list of 6lbr neighbours) with a level 5 debug: