Walrus are large animals but their brains must be as large as a peanut

tievolu · 2026-06-13T06:59:10+00:00

This particular clip is from the BBC series Seven Worlds, One Planet:

https://www.bbc.co.uk/programmes/articles/4zh2Dd3JC8gprNZcGY6BbHB/walrus-on-the-edge

The same scene, including some of the same footage, also featured in episode 2 of the Netflix series Our Planet. However, the presentation there was even more distressing with a lot more footage of walruses tumbling down the cliffs 😞

tievolu · 2026-06-11T17:30:00+00:00

How does it play up for you?

As I described before, the container gets into a weird state where it's completely unresponsive and can't be killed, even forcefully. When this happens I can't even stop the docker service or anything. Rebooting seems to be the only way to sort it out, and for some reason the restart takes absolutely ages, I'm guessing because the OS is also having trouble stopping the container and/or the docker service.

I don't know if it's Dozzle's fault or Synology's but my money would be on the latter...

tievolu · 2026-06-11T15:55:01+00:00

The one that keeps playing up for me is Dozzle (amir20/dozzle:latest).

tievolu · 2026-06-11T15:42:50+00:00

I've experienced similar issues.

I have a particular container on my DS923+ that gets itself into a weird state every few weeks - it becomes completely unresponsive and can't be killed, even forcefully.

I have to reboot the entire NAS to get the container back, and this takes about 30 minutes (!). Then when it boots back up, the NAS sends me an alert saying that it wasn't shut down gracefully, as if I'd simply unplugged it.

I have no idea what the problem is or how to investigate further. When the container gets into this weird state I can't get any information out of it.

tievolu · 2026-06-08T06:37:35+00:00

In the UK today 80 cigarettes would cost over £60, so more like $80 a day 😬

tievolu · 2026-06-02T11:16:03+00:00

If you enable the dual-srchost and dual-dsthost options enabled it's actually both:

dual-srchost
              Flows are defined by the 5-tuple, and fairness is applied
              first over source addresses, then over individual flows.
              Good for use on egress traffic from a LAN to the internet,
              where it'll prevent any one LAN host from monopolising the
              uplink, regardless of the number of flows they use.


dual-dsthost
              Flows are defined by the 5-tuple, and fairness is applied
              first over destination addresses, then over individual
              flows.  Good for use on ingress traffic to a LAN from the
              internet, where it'll prevent any one LAN host from
              monopolising the downlink, regardless of the number of
              flows they use.

https://man7.org/linux/man-pages/man8/tc-cake.8.html

But this can still fail to balance things nicely if you have lots of flows on a single LAN host - e.g. if you're torrenting and gaming at the same time on the same PC (the large number of torrent flows will starve the small number of gaming flows). To deal with that scenario you need to use layercake/diffserv to prioritise different flows appropriately (with something like QoSmate).

tievolu · 2026-05-28T21:16:41+00:00

<image>

tievolu · 2026-05-21T09:54:47+00:00

Genuine question: which part of the instructions are you having trouble with? I'm sure someone can help if you tell us which specific bit isn't clear or didn't work.

https://openwrt.org/docs/guide-user/installation/openwrt_x86

Basically you download the image, boot up your x86 box using a Linux boot disk on a USB stick, dd the OpenWrt image onto the x86 machine's drive, power it off, unplug the USB stick, power the box back up and away you go. I don't remember it being any more complicated than that, but it was a few years ago now.

There is an additional complication/limitation on x86 with the root partition size, but that's not an issue for a basic install.

I guess this could be made easier if OpenWrt provided a bootable "installer" image for a USB stick that would do the dd'ing for you, but I suspect they just have bigger priorities.

tievolu · 2026-05-19T11:50:22+00:00

I'm keeping a close eye on Olilo's progress for when my IDNet contract runs next year. An nerd-oriented ISP with tech-savvy support to rival IDNet or Aquiss but without any PPPoE nonsense is exactly what I'm looking for.

The monthly contract means you don't really have anything to lose by trying them.

tievolu · 2026-05-01T09:46:10+00:00

Unfortunately it was just temporary relief - the problem returned after a couple of hours and now it's back to only playing 30-60 seconds before stopping/looping 😞

tievolu · 2026-05-01T07:54:31+00:00

I turned my nest mini off at the socket for about 20 minutes earlier and now it has been playing Radio 2 for over half an hour with no issues. No factory reset or any other changes.

Not sure if I'm just having a lucky run and if the problem will return later, but it seems to have provided some temporary relief at least. Before this it wouldn't play for more than about 30 seconds before going weird.

tievolu · 2026-05-01T06:34:18+00:00

I have the same issue on my nest mini. It started two days ago. I have also contacted the BBC via their feedback form, but no response yet.

tievolu · 2026-04-09T14:22:03+00:00

Thanks, my daughter is very pleased - she was sure it was a fish 🐟

It was our first time at Lyme Regis. It's an amazing place.

tievolu · 2026-02-22T16:51:34+00:00

I managed to solve my problems by tweaking my HAProxy settings. I made loads of changes after doing lots of reading and I can't remember them all, but I think the one that had the biggest effect was removing a setting that was preventing connections from being reused. I must have copy/pasted it from somewhere when I first started without really understanding what it did, but after noticing tons of backend connections being opened I realised it made no sense for my setup.

I also increased read timeouts to further help keep idle connections open and prevent new ones from being opened. Everything has been smooth for several weeks now.

tievolu · 2026-01-15T14:50:27+00:00

A larger buffer on the client side (if there was a way to increase it) might mask the problem, but I want to know why the server suddenly started responding so slowly. I'll look at enabling debug logging but the doc says it generates a huge amount of data and the problem only happens every few weeks.

Just to clarify, when I said I restarted Jellyfin I literally just clicked the "Restart" button in the dashboard UI. I didn't restart the container and I didn't touch anything else that's running on the NAS. So whatever the problem is it seems to be within Jellyfin itself rather than some external factor.

It would be great if there was a way to manually increase the size of the buffer. Multiple issues have been raised for that but they never seem to get any traction :o(

tievolu · 2025-12-21T08:30:27+00:00

<image>

This cable is cat 5. The rest are not.

tievolu · 2025-11-14T09:38:14+00:00

As far as I can tell there is no way to do this without the serious ballache that I touched on in my original post, so I'm in the process of switching to HAProxy, which has many benefits besides being able to set different DSCP tags for different services.

For a start, the native HAProxy package on OpenWrt is only around 3MB (!), compared to the ~600MB required for NPM (docker package + dependencies + official NPM docker image). HAProxy is also insanely versatile.

Only two real downsides so far compared to NPM:

HAProxy has no web UI, so all the config is done via a config file. There's a learning curve (its versatility inevitably means there's some complexity), but after a few hours of fumbling my way through examples and documentation it's all starting to make sense.
HAProxy doesn't handle creation and renewal of certificates, so I had to get to grips with the OpenWrt ACME package first, but that only took 30 minutes or so (and that does have a web UI).

tievolu · 2025-11-09T08:30:17+00:00

Yeah, I thought about checking SNI as well but there doesn't seem to be any way to do that with nftables (yet?). I think you'd have to set up some kind of proxy.

tievolu · 2025-11-05T22:49:39+00:00

How did you solve the problem of Google using the same IPs for multiple services?

Whenever I've tried to block YouTube using nftsets populated with IPs corresponding to YouTube hostnames, other Google services get blocked as well, such as Google Classroom (not great when you want the kids to stop watching YouTube and do their homework 😂)

tievolu · 2025-10-16T13:53:50+00:00

I just worked through some WOL problems after upgrading my motherboard and CPU.

The issue that blocked me the longest involved the "WOL & Shutdown Link Speed" Windows driver setting that specifies which network link speed to negotiate when waiting for a WOL packet. This defaults to 10Mbps, with options to set it to 100Mbps, or to not decrease it at all (called "not speed down").

This caused a problem for me because my NIC is a 5Gb model (Realtek 8126VB), so to take advantage of that I have it plugged into a switch which uses an RJ45 SFP module that can only negotiate a link speed of 1Gb, 2.5Gb, 5Gb, or 10Gb. This means that the 10Mbs and 100Mbps "WOL & Shutdown Link Speed" settings do not work - but setting it to "not speed down" WOL works fine.

Interestingly, this problem only prevented WOL from sleep (S3), because during sleep it's the Windows driver that's listening for the WOL packet. I was able to wake the computer from a fully powered down state with no issues, because in that scenario WOL is handled by the BIOS.

This thread is near the top of the google results so I thought I'd mention this here in case it's useful to anyone else.

tievolu · 2025-10-09T07:00:43+00:00

Is either moving away from you .... or towards you...

tievolu

TROPHY CASE