Skip to content
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

Facing issue to connect Broker over SSL. #9

Open
sanket-kulkarni-vmware opened this issue Dec 9, 2016 · 2 comments
Open

Facing issue to connect Broker over SSL. #9

sanket-kulkarni-vmware opened this issue Dec 9, 2016 · 2 comments

Comments

@sanket-kulkarni-vmware
Copy link

I am facing an issue for checking benchmark of broker over SSL.

Command I am using:

~/mqtt-bench -broker=tcp://127.0.0.1:8883 -action=pub -tls=client:ca.crt,client.crt,client.key -x=true

I am getting following error log:

Connected error: Network Error : %!s(<nil>)

@gdhgdhgdh
Copy link

gdhgdhgdh commented Feb 27, 2017

👍 - looking with strace shows that the bytes sent to the remote server are NOT encrypted..

strace -f mqtt-bench -action=pub -broker="tcp://XXXXXXXX-1714791189.eu-west-2.elb.amazonaws.com:8883" -tls=client:root.crt.pem,0000000000000000.crt.pem,0000000000000000.key.pem -x=true


[...]

[pid 17976] getpeername(3, {sa_family=AF_INET, sin_port=htons(8883), sin_addr=inet_addr("52.56.X.X")}, [16]) = 0
[pid 17976] write(3, "\20\33\0\4MQTT\4\2\0\36\0\17mqttbench4638-0", 29 <unfinished ...>

@hareeqi
Copy link

hareeqi commented Jul 15, 2017

Because you are putting the broker address wrong, It should be

-broker=ssl://127.0.0.1:8883 not -broker=tcp://127.0.0.1:8883

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants