I thought it has to be transmitted by Lightburn using the udp protocol… or else my t-link wifi bridge would not have worked, which was purchased from Amazon for $12… Nor would it work when I directly plug it into my pc via Ethernet.
UDP is the messaging mechanism that is a low level subset of TCP/IP and has no error reporting, re-ordering or most of what we expect from TCP/IP.
I can connect three running versions of Lightburn to my Ruida…via Ethernet, they all talk to it, but I can confuse it rather easily… since it doesn’t know or care who’s talking to it…
Conversely …
When I select Lightburn Bridge in the devices, maybe the UDP translation occurs at the PI… I have never gotten a good explanation of exactly what the Lightburn software layer in the PI does… All references that I’ve read from Adam have just mentioned that it corrects some of the UDP problems… and he seems to imply there isn’t any more development going into it… at least at the moment…
I’m sure Adam is busy and I don’t want to ping him over something like this…
I would never argue a usb port can’t be done…
I was always hoping that a .deb package would show up… that way I can get rid of one of the pair of PI’s that I use on the machine and use it elsewhere … One monitors the systems, the other does nothing but be the bridge 
… I’m sure the PI 4 could easily handle all of it. Or even a PI zero running linux…
I guess I’m still clueless… 
In this thread, the usb and wifi options are discussed … with Oz comments… from Jan, '22
