I had one of the DXP4800 Plus NASes for about a month before RMAing it.
The CPU would immediately hit 100C with even the slightest whiff of load.
The entire thing was also unstable and would regularly just lock up without any kernel panic or other error message available, could even get kdump to gather anything (I'd binned their dodgy NAS OS and installed Debian).
It also seemed to amplify the noise of the hard drives within. Every thunk of a drive head moving around would be audible from a different room. Not sure how they managed to do that, but it's an acoustic nightmare.
The problem is the continual stream of bullshit emitted from Trump's mouth gets clicks, and as such even little things that don't have any bearing on an international audience are reported heavily.
When Biden was president I barely heard anything about US politics, but with Trump in power it's hard to avoid.
I have been having this exact same issue across multiple websites recently, most of the time it's monospace fonts that have the issue - Github is a nightmare. It only started after I upgraded to Fedora 42.
Haven't got to the bottom of it yet. I set Victor Mono as my Monospace font in Chrome and that has fixed it for things like the HN comment box, for instance, but Github and such still all look weird.
Are you familiar with port knocking? My servers will only open port 22, or some other port, after two specific ports have been knocked on in order. It completely eliminates the log files getting clogged.
The bots have been port scanning me for decades. They just don't know which two ports to hit to open 22 for their IP address. Simply iterating won't get then there, and fail2ban doesn't afford them much opportunity to probe.
Did you really notice a significant drop off in connection attempts? I tried this some years ago and after a few hours on a random very high port number I was already seeing connections.
I use a non standard port and have not had an unknown IP hit it in over 25 years. It's not a security feature for me, I use that to avoid noise.
My public SFTP servers are still on port 22 and but block a lot of SSH bots by giving them a long "versionaddendum" /etc/ssh/sshd_config as most of them choke on it. Mine is 720 characters long. Older SSH clients also choke on this so test it first if going this route. Some botters will go out of their way to block me instead so their bots don't hang. One will still see the bots in their logs, but there will be far less messages and far fewer attempts to log in as they will be broken, sticky and confused. Be sure to add offensive words in versionaddendum for the sites that log SSH banners and display them on their web pages like shodan.io.
In my experience can cut out the vast majority of ssh connection attempts by just blocking a couple IPs. ... particularly if you've already disabled password auth because some of the smarter bots notice that and stop trying.
Connectivity and IP blockage (I assumed) issues last time I tried it.
But the main reason is — it’s the default recommendation on HN. So I would prefer to know what else good there that people are using. Because it would be really sad if it’s the only one. I kind of refuse to believe that.
It's the only one. It's technically difficult, and there are lots of things to do to sell out the user in the name of not leaving money on the table or bowing to authority, or other excuses for bad behavior. Principle in anything is rare, we're lucky to have mullvad.
Next best option is self hosting. Beyond that, it's a thoroughly enshittified marketplace.
To add to the sibling comment, being stuck in a small, incredibly loud tube usually pinned under some receiver isn't great for claustrophobic patients either.
Assume there is similar for other countries, though I can't see this being of any use whatsoever.
reply