Paul SomeoneElse<a href="https://snac.d34d.net?t=openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a><br><br><a href="https://snac.d34d.net?t=techpost" class="mention hashtag" rel="nofollow noopener" target="_blank">#techpost</a><br><br>One of my problems with using relayd for tls is that I lose the origin IP in my httpd logs.<br><br>(background:)<br>I am adding IPs to my PF blocklist because I don't like my server getting spidered/crawled.<br>Specifically repeatedly hitting dynamic links that are not valid.<br><br>So I find the bad hit in my httpd log, and then use the time stamp to find<br>the origin IP in the relayd log.<br><br>I can probably add more info to either the httpd log or the relayd log<br>to mitigate this. Or I can script some tools to help me.<br><br>I was meaning to script some log stuff anyways just to get an idea<br>of how often it happens. Also writing helper code to look for<br>stuff in log files is fun for me. I was thinking for ease I would wait<br>until they "roll" and access the .gz versions. Then I don't have to<br>do "last line accessed" kind of record keeping. But I am more thinking<br>I WILL access the live logs, because doing that "last line accessed"<br>record keeping is also a fun exercise.<br>