Bug with 2.02 MQTT connect

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug with 2.02 MQTT connect

Richard Man
The MQTT connect function is missing code to check for optional username/passwd and add the info to the header. The fix is trivial, and I will see if I can send it to the official people when I have the chance.


--
// richard http://imagecraft.com
Beyond Arduino - When you're ready to get serious...
JumpStart C Tools for Atmel AVR and Cortex-M, The Better Alternative

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug with 2.02 MQTT connect

goldsimon@gmx.de
On 02.08.2018 22:16, Richard Man wrote:
> The MQTT connect function is missing code to check for optional
> username/passwd and add the info to the header. The fix is trivial,
> and I will see if I can send it to the official people when I have the
> chance.

Version 2.0.2 is rather old. I think what you want is already
implemented in git master and in the current release candidate 1 for the
upcoming version 2.1.0:

https://savannah.nongnu.org/forum/forum.php?forum_id=9196

Simon

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug with 2.02 MQTT connect

Richard Man
I meant lwIP 2.0.3, but yes you are correct, 2.1.0 RC1 does have a fix, as well as using "altcp_" instead of "tcp_" function names. Must be something new....

Thanks


On Thu, Aug 2, 2018 at 11:23 PM, [hidden email] <[hidden email]> wrote:
On 02.08.2018 22:16, Richard Man wrote:
The MQTT connect function is missing code to check for optional username/passwd and add the info to the header. The fix is trivial, and I will see if I can send it to the official people when I have the chance.

Version 2.0.2 is rather old. I think what you want is already implemented in git master and in the current release candidate 1 for the upcoming version 2.1.0:

https://savannah.nongnu.org/forum/forum.php?forum_id=9196

Simon

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users



--
// richard http://imagecraft.com
Beyond Arduino - When you're ready to get serious...
JumpStart C Tools for Atmel AVR and Cortex-M, The Better Alternative

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug with 2.02 MQTT connect

goldsimon@gmx.de
On 03.08.2018 08:55, Richard Man wrote:
> I meant lwIP 2.0.3, but yes you are correct, 2.1.0 RC1 does have a
> fix, as well as using "altcp_" instead of "tcp_" function names. Must
> be something new....

Those "altcp_" functions allow layering SSL between MQTT and TCP. There
sghould be an example of this somewhere... If not I'll have to create
one. Anyway, in default configuration, the functions just map through to
the "tcp_" functions.

Simon

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug with 2.02 MQTT connect

Richard Man
Wow! Amazingly enough, sandwiching mbedTLS between MQTT and TCP is EXACTLY what I need to do next! I have mbedTLS ported working with lwIP and my RTOS (REXIS).

This should save time a bit of time. Thanks!

On Thu, Aug 2, 2018 at 11:59 PM, [hidden email] <[hidden email]> wrote:
On 03.08.2018 08:55, Richard Man wrote:
I meant lwIP 2.0.3, but yes you are correct, 2.1.0 RC1 does have a fix, as well as using "altcp_" instead of "tcp_" function names. Must be something new....

Those "altcp_" functions allow layering SSL between MQTT and TCP. There sghould be an example of this somewhere... If not I'll have to create one. Anyway, in default configuration, the functions just map through to the "tcp_" functions.


Simon

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users



--
// richard http://imagecraft.com
Beyond Arduino - When you're ready to get serious...
JumpStart C Tools for Atmel AVR and Cortex-M, The Better Alternative

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug with 2.02 MQTT connect

goldsimon@gmx.de
On 03.08.2018 09:08, Richard Man wrote:
> Wow! Amazingly enough, sandwiching mbedTLS between MQTT and TCP is
> EXACTLY what I need to do next! I have mbedTLS ported working with
> lwIP and my RTOS (REXIS).
>
> This should save time a bit of time. Thanks!

I just noticed I cannot find an example :-(  I'll have to dig in my
local sources...

Simon

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug with 2.02 MQTT connect

vespaman
fredag 3 augusti 2018 kl. 09:11:29 CEST skrev  [hidden email]:
>
> I just noticed I cannot find an example :-(  I'll have to dig in my
> local sources...
>
> Simon

If you would find a simple example, it would be very useful for me as well,
mqtt+mbedtls is in my next project. Keeping my fingers crossed.. :)
(it not, I fully understand, and continue to appreciate all the effort you put
into making lwip great)

Cheers,
  Micael



_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users