repository·master·Indexed 42 days ago
https://github.com/sysgrok/edge-netA collection of async, no_std, and no-allocation network protocol implementations for embedded systems and microcontrollers. Version 0.16.0 includes implementations for HTTP (client and server), DHCP (client and server), mDNS responders, and Captive Portal DNS servers.
The edge-raw crate provides an asynchronous, no_std, and no-alloc implementation for creating and parsing IP and UDP packets. It is specifically designed for low-level networking tasks where standard IP stacks might not be available or sufficient.
Key use cases include protocols like DHCP, which require the ability to send and receive UDP packets to/from peers that do not yet have an assigned IP address.
edge-dhcp is an asynchronous, no_std, and no-alloc implementation of the DHCP protocol. It is designed for resource-constrained environments and provides both client and server capabilities.edge-ws is an asynchronous, no_std, and no-alloc implementation of the WebSocket protocol. It is designed for resource-constrained environments where heap allocation is not available. It works in conjunction with edge-http for the initial HTTP upgrade handshake.edge-mdns is an asynchronous, no_std, and no-allocation implementation of an mDNS (Multicast DNS) responder. It is built upon the domain library and is designed for resource-constrained environments. It allows devices to be discoverable on a local network using the .local hostname convention.The edge-net crate provides asynchronous, no_std, and no-allocation implementations of various network protocols designed for microcontrollers and embedded systems. It is organized into several specialized crates depending on the required functionality:
edge-http).edge-ws).edge-captive).edge-mdns).edge-dhcp).edge-raw), often used alongside DHCP.edge-nal).edge-http is an asynchronous, no_std, and no-alloc implementation of the HTTP protocol. It is built upon the httparse library and is designed for resource-constrained environments. It provides both HTTP client and HTTP server capabilities.edge-nal provides a set of networking traits for UDP, TCP, and raw ethernet (raw sockets) designed for edge and embedded environments. It extends the capabilities of embedded-nal-async to support more complex networking patterns required by crates like edge-mdns, edge-dhcp, edge-http, and edge-ws.no_std, and no-alloc implementation of a Captive Portal DNS server. It functions by resolving every requested domain name to a single, fixed IP address, which is a common technique used to redirect users to a login or landing page in captive portal environments. The implementation is built upon the domain library.The edge-nal-openthread crate provides an implementation of edge-nal UDP factory and socket traits for the OpenThread (Thread) network. It works by wrapping the openthread crate to allow any edge-nal-based UDP protocol to operate over a Thread network.
Key Constraints:
edge-nal-embassy crate provides a bare-metal implementation of the edge-nal traits, specifically designed for the Embassy ecosystem. It leverages the embassy-net networking stack to provide network abstraction layers (NAL) for embedded systems running on Embassy.edge-nal-std crate provides a concrete implementation of the edge-nal traits using the Rust Standard Library. It is designed to allow network-agnostic code to run on platforms that support the standard library by providing asynchronous networking primitives.The edge_raw::io module provides implementations of several core traits from the edge_nal crate. These allow you to perform raw packet operations:
edge_nal::RawBind: For binding to a network interface.edge_nal::RawReceive: For receiving raw packets.edge_nal::RawSend: For sending raw packets.These traits are essential when you need to bypass the standard IP stack to communicate with unconfigured devices.