Ltning
@ltning@weirdr.net
11 following 15 followers
See also my main fediverse presence: @ltning@anduin.net
About this instance, at the time of writing:
- OS: #NetBSD 10
- Reverse proxy: nginx
- CPU: Dual Pentium Pro Overdrive, 333MHz
- RAM: 512MB EDO
- NIC: 3Com 100Mbit PCI NIC
- Storage: SATA 1.0 (CF and SSD)
ssl_ecdh_curve
from secp521r1:secp384r1;
to X25519:prime256v1;
now; let's see if that helps.CC: @rubenerd@bsd.network
Cc @grunfink@comam.es @gumnos@bsd.cafe @rubenerd@bsd.network
CC: @gumnos@bsd.cafe @rubenerd@bsd.network @grunfink@comam.es
(Read the alt text for more info)
#retrocomputing #moreram
@ltning I installed NetBSD on a 486.. 10 years ago, it worked great! But looks like newer versions need extra work for old PCs, see: https://www.idatum.net/running-netbsd-101-on-a-1998-toshiba-laptop.html
So..TLS aside, what is the most lightweight reverse proxy I can use instead of nginx
in front of this thing? You know, in case I would like to move the instance from this beefy PPro to, say, a #486 or a #Nintendo Wii running #NetBSD? :)
@ltning worth looking into: OpenBSDs httpd, and h2o
@ltning httpd and relayd can come with base system in case of BSDs
@ltning I used Apache HTTPd, with many modules ripped out as a reverse proxy for Snac on a machine with 32MB of RAM if that helps.
Something I was able to do with Apache that turned out to be helpful was limiting the connections to Snac itself to 1 - meant that the storm of hits from other servers allowed some requests to work, rather than mostly failing.
If curious: https://people.cobaltqu.be/~theothertom/Physical/Qube3Fedi.html
@ltning oh, and as an aside - I found Snac just about usable on a 450MHz K6-II with 32MB of RAM. Extrapolating backwards makes me think you would need quite a lot of patience to use it on a 486 :D
A bigger challenge will be the Nintendo WII - it has, I believe, 24MB or something like that? But at least the CPU should be vastly superior to any 486..
@ltning 24MB is tight, though you might be able to do it if you use something else as a proxy in front on Snac.
Something else that might not be immediately obvious too - lots of 32-bit builds target i686 these days, at least for Linux. The only Linux distro I could find that targets i586 with recent releases was Slackware - dunno what the situation is for NetBSD though.
Do you do TLS in Apache too? On a K6-II?
@ltning I've managed to add more memory since I first installed the system, so it's not quite as tight as it was (and now there's meaningful disk cache, which seems to help loads).
Looking at the stats on it, snac is using 13.5MB (resident), Apache is using 10.5MB.
I think the perception of Apache as a resource hog may have come from the "prefork" MPM there's other, lighter MPMs you can use instead.
Yeah - it's doing TLS in apache. https://social.cobaltqu.be/theothertom/p/1717810603.209255 if you want a sense of how quick it is.
@ltning Sure. I've got this, which I'm pretty sure is just the defaults from the distro package (at least, I don't remember tuning it):
SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
SSLHonorCipherOrder on
SSLProtocol all -SSLv3
SSLProxyProtocol all -SSLv3
SSLPassPhraseDialog builtin
SSLSessionCache "shmcb:/var/run/ssl_scache(512000)"
SSLSessionCacheTimeout 300
See also my main fediverse presence: @ltning@anduin.net
About this instance, at the time of writing:
- OS: #NetBSD 10
- Reverse proxy: nginx
- CPU: Dual Pentium Pro Overdrive, 333MHz
- RAM: 512MB EDO
- NIC: 3Com 100Mbit PCI NIC
- Storage: SATA 1.0 (CF and SSD)
ssl_ecdh_curve
from secp521r1:secp384r1;
to X25519:prime256v1;
now; let's see if that helps.CC: @rubenerd@bsd.network
Cc @grunfink@comam.es @gumnos@bsd.cafe @rubenerd@bsd.network
CC: @gumnos@bsd.cafe @rubenerd@bsd.network @grunfink@comam.es
I'll post each picture as a reply to this post, as snac doesn't like multiple attachments..
Enjoy. And wish the poor box luck serving this.
@ltning I need to use that toaster for lunch tomorrow…
secp*
curves are orders of magnitude slower than X25519
and prime256v1
. At least on a Pentium Pro/Pentium II-class CPU.History