Stuart Longland (VK4MSL)<p>This afternoon, I got close to what I wanted to achieve in terms of load-balancing between the two <a href="https://mastodon.longlandclan.id.au/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> <a href="https://mastodon.longlandclan.id.au/tags/sabots" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sabots</span></a> I have running.</p><p>I had originally planned to use <a href="https://mastodon.longlandclan.id.au/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenBSD</span></a>'s <a href="https://mastodon.longlandclan.id.au/tags/OpenHTTPD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenHTTPD</span></a> or <a href="https://mastodon.longlandclan.id.au/tags/RelayD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RelayD</span></a> to do the job, but <a href="https://mastodon.longlandclan.id.au/tags/HAProxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HAProxy</span></a> <a href="https://mastodon.longlandclan.id.au/tags/PROXY" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PROXY</span></a> protocol was the limiting factor… so I went <a href="https://mastodon.longlandclan.id.au/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nginx</span></a> instead.</p><p>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.</p><p>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 <a href="https://mastodon.longlandclan.id.au/tags/sniproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sniproxy</span></a>.</p><p>But… it works, you can hit <a href="https://sabot.vk4msl.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">sabot.vk4msl.com/</span><span class="invisible"></span></a> 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.</p><p>This did get me thinking though, if enough of us did it, we could have a <a href="https://mastodon.longlandclan.id.au/tags/AISabotAsAService" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AISabotAsAService</span></a> for websites to redirect/link to when they think they're being scraped by an AI bot.</p><p>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.</p>