Issue with MQTT-SN Gateway connection

[rogerarchibald]

Hello,

I'm working on a project using a Thread network to send MQTT packets and I'm having an issue with the example project out of the box.  I'm running the version 3.2.0SDK for Thread and Zigbee.  My setup is:

-2x NRF52840DK, one running the thread_mqtt_sn_client_publisher and the other running the thread_mqtt_sn_client_subscriber

-1x NRF52840 Dongle flashed with the NCP firmware on a Raspberry Pi3B running the Nordic Border Router image.

I can see the 3 devices on the thread network and ping between them.  I can ping google and dns resolve an ipv4 address, but not an ipv6 (I think this is due to my ISP not providing a <64 prefix).

When I try to connect either of the DK's to the gateway per the example, I see the following on the Debugger:

<info> app: MQTT-SN event: Client has found an active gateway.

<info> app: MQTT-SN event: Gateway discovery procedure has finished.

<info> app: MQTT-SN event: Gateway discovery result: 0x0.

I don't know if I'm missing something obvious here or if the lack of IPV6 connectivity to the outside world is my main issue-my understanding is that paho speaks to mqtt.eclipse.org via ipv4 so I'm not sure that this would be an issue.  If anybody has any suggestions on how to get past this wall I'd appreciate it.  I'm trying to start out very basic with this and work up, but I've hit a wall early on!

[rogerarchibald]

I've tried restarting paho on the Pi and I see the following when watching the terminal as I try to connect the DK:

20191115 010110.088 PahoGateway-01 has been started.

 ConfigFile: /etc/paho-mqtt-sn-gateway.conf
 SensorN/W:   Gateway Port: 47193 Broadcast Address: ff03::1 Interface: wpan0
 Broker:     198.41.30.241 : 1883, 8883
 RootCApath: (null)
 RootCAfile: (null)
 CertKey:    (null)
 PrivateKey: (null)

20191115 010131.225   SEARCHGW          <---  Client                              01 01
20191115 010131.225   GWINFO            --->  Clients                             02 01

20191115 010143.058   CONNECT           <---  nRF52840_publisher                  04 04 01 00 3C 6E 52 46 35 32 38 34 30 5F 70 75 62 6C 69 73 68 65 72
Error: BrokerSendTask: nRF52840_publisher can't connect to the broker. errno=113 No route to host 

I'm unable to ping 198.41.30.241 from the Pi, although I can ping it from my desktop.

I'm sure my ignorance towards networking is on full display, but if anybody has any tips I'd really appreciate it.

[Edvin]

Hello,

Can you reach the IP from your computer? Try to ping the address. If there is no route to it, then you will not be able to reach it from the DK/RPi. Maybe the IP of the destination you are trying to reach has changed?

BR,

Edvin

[rogerarchibald]

I'm working with the examples right out of the box with the SDK and the Raspberry Pi image.  The included 'paho-mqtt-sn-gateway.conf' has the BrokerName as 192.41.30.241.  I've tried changing that to 'iot.eclipse.org' without any change in the results.  

[Edvin]

I get a different IP address when I lookup the iot.eclipse.org. Can you please let me know what guide you try to follow? I am not sure exactly what you are trying to do, or where you got your IP address or the iot.eclipse.org domain from..

[rogerarchibald]

Edvin,

I was trying to follow the example on InfoCenter and with the 192.41.30.241 address that was the default on the Pi image I wasn't able to connect.  I mistakenly tried to use iot.ecliplse.org rather than MQTT.eclipse.org for the BrokerName.  Now I'm using the domain MQTT.eclipse.org and everything is looking good.  

I appreciate your assistance here and apologize for taking your time on something so silly.