Hello Marko,
OC_TRANSPORT_IP and OC_TRANSPORT_IPV4 are both set.
The ip-adress should be the one from the board, right? I always get a
timeout. Is there a way to activate some kind of verbose output?
I start the service by calling
oc_main_init((oc_handler_t *)&omgr_oc_handler);
as in the slinky_oic app, which also does not connect.
any ideas?
Regards,
jan
Am 21.06.2018 um 22:14 schrieb marko kiiskila:
On Jun 21, 2018, at 10:59 AM, marko kiiskila <[email protected]> wrote:
On Jun 21, 2018, at 2:19 AM, Jan Clement <[email protected]> wrote:
Hello you All,
at the moment I am stuck at connecting to the oic server via newtmgr over udp.
the connection works fine with serial but ip is not.
I added a connection with
newtmgr conn add myudp5683 type=oic_udp connstring=[127.0.0.1]:5683
the port number is from the documentation, is it the correct one? And where
could i change it?
Make sure that you have syscfg knobs OC_TRANSPORT_IP and OC_TRANSPORT_IPV4
turned on.
5683 is the right port. There’s a define in
net/oic/src/port/mynewt/ip4_adaptor.c, if you need to change it.
Making it adjustable with syscfg is ok, if you want to create a PR.
BTW, here are profiles I’m using for communicating with the server over
loopback interface.
[marko@IsMyLaptop:~]$ newtmgr conn show v4_lo
Connection profiles:
v4_lo: type=oic_udp, connstring='[127.0.0.1]:5683'
[marko@IsMyLaptop:~]$ newtmgr conn show v6_lo
Connection profiles:
v6_lo: type=oic_udp, connstring='[::1]:5683'
