0

[HELP]AJTCL - linux - alljoyn-14.02.00-thin_client-sdk-linux

asked 2014-08-05 19:59:11 -0700

juige gravatar image

updated 2014-08-05 19:59:41 -0700

Hi all,

I use this AJTCL SDK to build basic_service and basic_client but both of them can not correctly connect to my alljoyn-daemon which is built from alljoyn-14.02.00-src(AJSCL) on the board. The daemon works well with the basic_service, basic_client, and chat from AJSCL SDK. So I do not suppose the daemon is not work.

BTW, I have change the AJTCL service name from "org.alljoyn.busNode" to "org.alljoyn.Bus.sample" in order to be the same service name as alljoyn-daemon.

And I use wireshark to sniffer the packets. The daemon only respond the corresponding discovery packet to port 9956? So, It means my AJTCL does not listen on port 9956 right? Anyone knows how to use the AJTCL with AJSCL?

Thanks for sparing your time reading my question.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-08-06 19:17:08 -0700

0502lian gravatar image

I think it's the authentication problem. There is the code in SampleDaemon.cc for authentication.

namespace SampleDaemon {
const char* DefaultDaemonBusName = "org.alljoyn.BusNode.TestingPurposesOnly";

const char* ThinClientAuthMechanism = "ALLJOYN_PIN_KEYX";
const char* ThinClientDefaultBusPwd = "1234";
}

but there is nothing in the basic_service or basic_client. I suppose that the basic_service (in AJTCL) can correctly connect to basic_client(in AJSCL) not using the alljoyn daemon.

edit flag offensive delete publish link more

Comments

Hi lian, I have solve it. Now my AJTCL basic_service and basic_client can connect to my AJSCL daemon. In consequence, I only modify the aj_connect.c to let the port fix to 9956. And I remain the service_name "org.alljoyn.Busnode". Finally, change the number of max_untrusted_clients in alljoyn-daemon config from 0 to 20 and turn the restrict_untrusted_clients from TRUE to FALSE.

juige ( 2014-08-07 03:21:01 -0700 )edit

But another problem is that the discovery stage of both basic_service and basic_client are unstable. Sometimes both of two stuck in AJ_Discovery and cannot find the corresponding service.

juige ( 2014-08-07 03:23:42 -0700 )edit
0

answered 2014-08-06 01:19:43 -0700

juige gravatar image

There is a little progress now. Now the basic_client can get where the daemon is. But it stuck in AJ_authenticate, the error log is as follows:

000.000 aj_msg.c:752 The connection was rejected by the routing node

000.000 aj_msg.c:1082 Discarding bad message AJ_ERR_REJECTED

Does anyone knows what happened? Thanks

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2014-08-05 19:59:11 -0700

Seen: 507 times

Last updated: Aug 06 '14