วีดีโอ

Usually, "frames" are used w.r.t. Ethernet, "segments" are used for TCP payload within frames, "packets" and "frames" are usually synonyms. Bytes are, well, bytes. If you have more specific question - we'd be happy to address, just ask!

You are welcome!

Glad it was helpful!

Please follow this guide: mongoose.ws/documentation/tutorials/device-dashboard/#1-skeleton-firmware

@@mongoose-networking-library I still got a problem. I followed your guide, but I get the DHCP request message. I the pins are correct. Do you know what could also be an issue?

How about just adding RP2040 + W5500 to the mongoose.ws/wizard/ ? The basic principles would stay absolutely the same as already outlined in the video, but the wizard would make a ready-to-go project ready?

​@@mongoose-networking-libraryThat would certainly help. I guess my broader request is for a tutorial that covers using Mongoose in FreeRTOS, what may or may not be the gotchas and pitfalls. It doesn't have to be a web server example. It just happens that my platform of choice is RP2040 + W5500. If there is already a tutorial that covers this, my apologies.

@@chrisgoddard9236 For sure! Actually, using Mongoose in FreeRTOS and in bare metal is absolutely identical. Just run event loop in a separate task, and that's it! The only gotcha is the task's stack size - give it 8k and you're good. Take a look at mongoose.ws/documentation/tutorials/rp2040/pico-w5500/. What environment do you use, RPI C SDK, Arduino or something else?

@@mongoose-networking-library Thanks. I'm using PICO-SDK (In VSCode if that makes a difference!) C++ projects with a few C libraries for good measure.

Yes, the outlined strategies would work on rp2040.

Yes: mongoose.ws/documentation/tutorials/core/embedded-filesystem/ The other option is to use Mongoose Wizard, mongoose.ws/wizard/ - which generates everything for you.

Thank you! And more is coming!

@@mongoose-networking-library oh wow... Would be waiting... Also would be glad if there is any way of getting involved

mg_mqtt_pub() (g, not q) ptr -> buf Hope that helps!

Thanks! The concept is simple, but the details of implementation are not so. You can take a look at the code walk-through video, which explains this concept on a real world example: th-cam.com/video/x5Uy-CIz33k/w-d-xo.html . That one is a complex video.

@@mongoose-networking-library I had an Cybersecurity exam today, and thankfully i'd be able to solve a question on Physical layer of OSI model just because i remembered this video. I'll check it out 😋 Thanks again!!

The oldest data was removed. Continue... 00000 668c1 1 mongoose.c:16587:mg_tcpip_driv b0000000 668c5 1 mongoose.c:16587:mg_tcpip_driv b0000000 668ca 1 mongoose.c:16587:mg_tcpip_driv b0000000 668ce 3 mongoose.c:5189:tx_dhcp_discov DHCP discover sent. Our MAC: 02:2d:cf:46:29:04 66c9d 1 mongoose.c:16585:mg_tcpip_driv No free descriptors: 0 b0000000 00000000 00000000 66ca5 1 mongoose.c:16587:mg_tcpip_driv b0000000 66ca9 1 mongoose.c:16587:mg_tcpip_driv b0000000 66cad 1 mongoose.c:16587:mg_tcpip_driv b0000000 66cb2 1 mongoose.c:16587:mg_tcpip_driv b0000000 66cb6 3 mongoose.c:5189:tx_dhcp_discov DHCP discover sent. Our MAC: 02:2d:cf:46:29:04 67085 1 mongoose.c:16585:mg_tcpip_driv No free descriptors: 0 b0000000 00000000 00000000

Thank you! Is there something particular you'd like to see?

You're welcome!

Thank you! And more videos are surely coming! If you have a specific topic you're interested in, let us know.

@@mongoose-networking-library Maybe https and websocket secure

Thank you! To make it simple - that's our goal!

Thank you. You partially answered your own question. Mongoose is well documented. Well supported. Very easy to integrate. Provides a well-designed high-level API like HTTP/MQTT. Implementing a simple Web/Websocket/MQTT code takes just a couple of minutes. Provides TLS. If you report an issue, it gets promptly fixed - see issue count on Github. So it beats not only lwIP. Mongoose is the best embedded network library you can find.

@mongoose-networking-library Thank you for elaborating, I have to look into Mongoose more. It's indeed really active, good to see. Big plus of LwIP is the license. Do you have a rough value for the Mongoose license cost if used in a commercial product?

@@rick_er2481Please contact us via the website. As for the the license - it all comes down as a total cost for the project. Including developing, maintaining the product, and cost of fixing possible mistakes in the product that is already shipped. By using lwIP, one does not pay for the license, but pays for extra development, and pays for risks associated with using ad-hoc, home-grown implementations built on (very far from ideal) lwIP examples. Plus, don't forget that Mongoose is much more than just a TCP/IP stack. When we're talking about the real product, the TCP/IP stack is not the biggest worry - it is the logic built on top of it. So, we would not compare the two, it is just not apples to apples. Here is a quick example. Imagine you want to create a Web UI for your product, which is a real-time graph reported by your device. You want to have user login, and HTTPS. Basic stuff. If you decide to use lwIP, you need to: a) add RTOS, and bear associated costs. If your firmware already uses RTOS, that's fine, but if it does not, it is an extra cost b) add and configure lwIP itself. Could be easy, could be very tricky and difficult. It depends on many factors c) add mbedTLS or another TLS library, for HTTPS. Then know how to optimise it (there are many pitfalls) d) add some 3rd party Websocket library for the real-time graph, cause lwIP does not provide one. Or make your own e) either patch lwIP httpd example (which is not trivial to adopt), or use 3rd party HTTP library to make a Web UI If you decide to use Mongoose, you need to: a) add Mongoose, and use one of the many reference projects to bring up the UI, done. Estimate the robustness, complexity, cost of maintenance, and potential risks of shipping a buggy product. Then estimate the total cost based on all factors. That cost estimation should make the decision more informed.

Thanks I will looking in to this. Again thank you for elaborating!

Yes that would be possible! Of course a web-based oscilloscope would have its limitations, but could be quite functional for many use cases. You're welcome to join our discord and share some details about your "oscilloscope" project idea, you can find a link on mongoose.ws/demo/ page.

Please take a look at this video - th-cam.com/video/lKYM4b8TZts/w-d-xo.html

Short answer: github.com/cesanta/mongoose/tree/master/examples/mqtt-client

link is broken :(

THank you, @@miloslovric2818 , a link has been corrected!