mqtt-users team mailing list archive

["Brian O'Donovan" <bodonovan@xxxxxxxxx>]

Roger,

Thanks for your help and you are right, I was running Dropbox and the
working directory I was using when running the MQTT publish process was
being synced with Dropbox (I didn't realize that Dropbox did peer to peer
communication on the LAN as well as synchronization via their server - but
as they say you learn something new every day).

The bottom line was that my issue was not a Mosquitto bug at all and merely
a iptables configuration error. Sorry to have bothered you.

Regards,
             Brian
http://www.brianodonovan.ie




On 28 October 2010 15:31, Roger Light <roger@xxxxxxxxxx> wrote:

> Hi Brian,
>
> > I came to this conclusion by placing a wireshark trace on traffic between
> > the two nodes while exchanging MQTT messages. I confirmed this conclusion
> by
> > seeing that when I used the default (for inside IBM) policy of dropping
> > traffic from this udp port the MQTT messages did not get through, while
> if I
> > changed the rules to accept udp packets from this port the PQTT messages
> got
> > through.
>
> I can't explain why allowing UDP port 17500 would allow messages
> through. Does the output of lsof show that mosquitto has port 17500
> associated with it? Do you run dropbox? It seems that port 17500 is
> used by dropbox for its lan sync feature.
>
> Cheers,
>
> Roger
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mqtt-users
> Post to     : mqtt-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mqtt-users
> More help   : https://help.launchpad.net/ListHelp
>