Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] MQTTSNGateway and AWS IoT

Hi,

Did you register your ClientID and SensorNet Address address to clients.conf ?

In order to authenticate the client, the gateway confirms that the ID and SensorNet Address are registered in clients.conf in case of TLS connection.


Tomy Technology
Tomoaki  YAMAGUCHI

2017-07-19 18:21 GMT+09:00 Sergey Semernin <sergey.semernin@xxxxxxxxx>:
Hello All!

I'm new to transparent MQTT-SN gateway that published in Paho project.
I'm trying to test this gateway with Amazon MQTT message broker. I set
up SSL/TLS certificates, test connection to the MQTT, and it works.

Then, I setup gateway:

BrokerName=....iot.eu-central-1.amazonaws.com
BrokerPortNo=1883
BrokerSecurePortNo=8883
ClientAuthentication=YES
ClientsList=clients.conf

RootCAfile=root-CA.crt
CertKey=my-certificate.pem.crt
PrivateKey=my-private.pem.key

GatewayID=1
GatewayName=PahoGateway-01
KeepAlive=900

GatewayPortNo=10000
MulticastIP=225.1.1.1
MulticastPortNo=1883

And I'm trying to publish or subscribe with mqtt-sn-tools.
Each time I got this error:

20170719 120527.230   CONNECT           <---  mqtt-sn-tools-7142
         04 04 01 00 0A 6D 71 74 74 2D 73 6E 2D 74 6F 6F 6C 73 2D 37 31
34 32
20170719 120527.910   CONNECT           --->  mqtt-sn-tools-7142
         10 1E 00 04 4D 51 54 54 04 02 00 0A 00 12 6D 71 74 74 2D 73 6E
2D 74 6F 6F 6C 73 2D 37 31 34 32
Error: BrokerRecvTask can't receive a packet from the broker errno=0
mqtt-sn-tools-7142

I checked traffic with tcpdump and saw that SSL/TLS connection with AWS
cloud is present. But nothing more.

What I missed? Or this gateway just not working/not tested with AWS MQTT
broker?


With best regards, Sergey.
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev


Back to the top