Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Please Try Out the MQTT-SN Gateway
Hi Paul,

It makes sense.

It's better to write these issues into the github Issue for future references and easy to link commits.
I made Issue #31  and copied issue from your mails.
Thank you for your cooperation.

Tomy Technology
Tomoaki  YAMAGUCHI

2016-10-04 22:56 GMT+09:00 Paul Kierstead <paulkierstead@xxxxxxxxx>:
On Sun, 2 Oct 2016 at 22:17 Tomoaki Yamaguchi <tomoaki@xxxxxxxxxxxxx> wrote:
1) Gateway send DISCONNECT message to a client and broker when the client doesn't send any message within  the keep alive time.
2) Gateway send DISCONNECT message to a client when the gateway can not send message to the broker. (Gateway requires the client to send CONNECT to establish a connection between the broker.)

try my latest version (0.8.0) in my rep.

 When the gateway gets unknown client publish, it still doesn't send a DISCONNECT:

 ***************************************************************************

 * MQTT-SN Transparent Gateway

 * Part of Project Paho in Eclipse

 * (http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt-sn.embedded-c.git/)

 *

 * Author : Tomoaki YAMAGUCHI

 * Version: 0.8.0

 ***************************************************************************


20161004 135202.607 PahoGateway-01 has been started.


 ConfigFile:  ./gateway.conf

 SensorN/W:   API mode 1, Baudrate 9600, SerialDevice /dev/ttyUSB1

 Broker:      localhost : 1883, 8883

 RootCApath:  (null)

 RootCAfile:  (null)

 ClientCerts: (null)


20161004 135203.304   PUBLISH     0000  <---  Non Active Client !                 0C 00 00 02 00 00 38


20161004 135218.302   PUBLISH     0000  <---  Non Active Client !                 0C 00 00 02 00 00 39


20161004 135233.298   PUBLISH     0000  <---  Non Active Client !                 0C 00 00 02 00 00 30


20161004 135248.293   PUBLISH     0000  <---  Non Active Client !                 0C 00 00 02 00 00 31


 This happens when you cycle the gateway with a client connected. Unless the client tries a PING or a >QoS0 publish, it will never figure out it is disconnected. I think the gateway should send back a DISCONNECT in this circumstance, as it is essentially the only way to recover.

PK

_______________________________________________
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