On Wed, Jan 23, 2019 at 09:43:10PM +0000, Stuart Henderson wrote: > On 2019/01/17 09:39, Tracey Emery wrote: > > Hello, > > > > This is a new port request and a replacement for a formerly requested port, > > which should be disregarded (net/busybeed). > > > > thingsd has been completely refactored and cleaned up from the original > > busybeed, and now uses libevent from base. > > > > Description: > > The thingsd OpenBSD proxy daemon provides a mechanism for clients and client > > processes to communicate with an array of serial and IoT things. At its > > core, > > thingsd is primarily a packet repeater in that it waits for packets to swap > > between subscriber clients and things. However, thingsd also provides > > password > > control over those connections, including client limits. > > It probably makes sense to talk in DESCR about what protocols/devices are > supported ..
Howdy, is this what you're looking for? Does it make sense? Suggestions? Thanks, Tracey --- DESCR.orig Thu Jan 24 09:17:15 2019 +++ DESCR Thu Jan 24 09:33:52 2019 @@ -1,5 +1,16 @@ The thingsd OpenBSD proxy daemon provides a mechanism for clients and client processes to communicate with an array of serial and IoT things. At its core, -thingsd is primarily a packet repeater in that it waits for packets to swap -between subscriber clients and things. However, thingsd also provides password -control over those connections, including client limits. +thingsd is primarily a data aggregator and repeater, in that it waits for +packets to swap between subscriber clients and things. However, thingsd also +provides password control over those connections, including client limits. + +On the client side, thingsd sets up TCP/IP sockets to transmit packets from +things, and vice versa. On the server side, thingsd can connect to any serial +device which has a viable file descriptor, create a persistent connection to +the IP address of a device transmitting packets on the same network, or setup a +UDP listener on the network to receive broadcasted packets. Devices tested +include: ESP8266/ESP32 modules, on both the serial and network sides, XBee +Series 2 coordinators connected in a mesh network, and NF24 devices. To +transmit to an IP address, which does not allow persistence, thingsd will +create an ad hoc connection, transmit a packet, and detach. The thingsd proxy +daemon is agnostic about packet data.
