I've been trying to carve out time to work on #LoRA again and have revisited https://git.oit.cloud/morgan/esp_netif_lora, my ESP-IDF IP over LoRa driver.

Today I got broadcast and multicast working, my test app, they just need to be put in the driver, with config options.

I've outlined a fix to allow for multiple interfaces if a device has more than one radio.

With multicast working, I think I can finally do #CoAP discovery!

kinda last major improvement for this to be useful is some sort of MTU enforcement.

esp_netif_lora

esp_netif_lora

Oit Cloud Consulting Services

@nils I did have some reservations about using @ratatui_rs for embedded devices (mainly that they're natively pixel based, so why go through a typewriter interface when there's no legacy) -- but seeing how reasonable that looks in code already at this quick prototype makes me reconsider.

Don't hold your breath for a text based #CoAP web browser, but I'd love to build one.

One specific number is gonna haunt me for a while now, and it's 65805.

Yes, I'm implementing #CoAP for #BIRD #Internet #Routing Daemon.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

RIOT Summit 2018 @ Amsterdam - Keynote by Jaime Jiménez (Ericsson)

https://makertube.net/w/3owgfnGMGoiVBVQKAwcZ6q

RIOT Summit 2018 @ Amsterdam - Keynote by Jaime Jiménez (Ericsson)

PeerTube

@reiver I think #CoAP is a good fit. It's easy enough to explain on a napkin, extensible, has the familiar REST semantics, and can be implemented on the smallest of devices.

Plus it has a well-vetted security mechanism that is lightweight enough to be implemented by a single person.

We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet. This includes security: I guess I just sent the first encrypted request over slipmux ever, and its security setup was unmodified from #ArielOS's CoAP example.
Implementation is available in #RiotOS (#C), and WIP for Ariel (#RustLang) and #aiocoap (#Python).

… and it was a success: We implemented runtime updates over #CoAP, and with our stack's access control, restricting changes to the VM code to authorized users is just a matter of four lines of config.

#IETFHackathon

Development of aiocoap, my Python CoAP library, is approaching its next breaking release.

If there's anything about its usability as a library that has been bugging you, especially if it would require breaking changes: Let me know soon, either here or on the issue tracker at https://github.com/chrysn/aiocoap/issues

#aiocoap #Python #CoAP

chrysn/aiocoap

The Python CoAP library. Contribute to chrysn/aiocoap development by creating an account on GitHub.

GitHub

@khalid Now that toot makes me kind'a feel bad about wanting to introduce coap:// to that list of #smolweb protocols.

Then again, #CoAP excels at proxying (and was carefully designed to facilitate it even across protocols), so a client could go through a CoAP proxy to access any of the others (unless it happens to implement any of the others as well).