#openhttpd — Public Fediverse posts

This afternoon, I got close to what I wanted to achieve in terms of load-balancing between the two #AI #sabots I have running.

I had originally planned to use #OpenBSD's #OpenHTTPD or #RelayD to do the job, but #HAProxy #PROXY protocol was the limiting factor… so I went #nginx instead.

One thing I haven't worked out yet, is how to pass the client IP by PROXY protocol to a HTTP back-end. Seems I can do it for a generic TCP stream, but not HTTP.

The alternative is to set X-Forwarded-For, and have the back-ends trust it, like they trust PROXY for the gateway's IPv4 address for #sniproxy.

But… it works, you can hit https://sabot.vk4msl.com/ and you'll either get sabot01 (which uses nepenthes) or sabot02 (which uses iocaine). Since neither cares about the URI, I can bounce the client between them.

This did get me thinking though, if enough of us did it, we could have a #AISabotAsAService for websites to redirect/link to when they think they're being scraped by an AI bot.

We could provide a pool of servers that would provide the link maze. Front-end proxies would just bounce you between all the pool members, feeding your bot nonsense.

I've just thrown this little page together…

http://vk4msl.com/2023-backburn/

I'll probably get rid of it once the backburning is passed, but this is the raw data along with the current conditions. The current conditions update each minute (self-refreshing).

I might see if I can get a chart going on it, the data's there.

Data flow is from the data logger → #6LoWPAN mesh → #CoAP proxy → #WideSky back-end → #pyhaystack → JSON files to be served up by #OpenHTTPD

The pyhaystack script runs from `cron`.