1
0
Fork 0
mirror of https://github.com/warmcat/libwebsockets.git synced 2025-03-30 00:00:16 +01:00
libwebsockets/lib/system
Andy Green d0fa39af7f lws_system: dhcpclient
Generic lws_system IPv4 DHCP client

 - netif and route control via lib/plat apis
 - linux plat pieces implemented
 - Uses raw ip socket for UDP broadcast and rx
 - security-aware
 - usual stuff plus up to 4 x dns server

If it's enabled for build, it holds the system
state at DHCP until at least one registered interface
has acquired a set of IP / mask / router / DNS server

It uses PF_PACKET which is Linux-only atm.  But those
areas are isolated into plat code.

TODOs

 - lease timing and reacquire
 - plat pieces for other than Linux
2019-10-12 12:41:14 +01:00
..
async-dns lws_system: dhcpclient 2019-10-12 12:41:14 +01:00
dhcpclient lws_system: dhcpclient 2019-10-12 12:41:14 +01:00
ntpclient lws_system: ntpclient 2019-10-10 16:34:37 +01:00
README.md lws_state and system state 2019-09-22 09:35:07 -07:00
system.c client h2: auth bearer option flag 2019-10-12 12:41:14 +01:00

LWS System Helpers

Lws now has a little collection of helper utilities for common network-based functions necessary for normal device operation, eg, async DNS, ntpclient (necessary for tls validation), and DHCP client.

Conventions

If any system helper is enabled for build, lws creates an additional vhost "system" at Context Creation time. Wsi that are created for the system features are bound to this. In the context object, this is available as .vhost_system.