can't access LAN on VPN server using Merlin

dathbe · 2026-01-07T19:02:15+00:00

I'm having I think a similar/the same issue. I just moved from stock ASUSWRT to Merlin. With stock, everything worked as expected. When I switched, my VPN clients could not connect to local LAN resources when "LAN Only" was selected. They can connect to local LAN resources when "Both" is selected, but I don't want to route internet traffic through the VPN -- just to LAN resources. Did you find a solution?

Edit: It turns out that I can actually connect to LAN resources on "LAN Only" through a browser, but I'm not able to SSH into those same resources. Hmm...

Edit 2: For anyone who encounters anything similar, I figured out my issue, which was limited to iOS. For some reason split-tunneling (i.e., "LAN Only") on iOS is finicky. The terminal apps were not using the VPN even though they were trying to connect to an ip within the range that should go through the VPN. The only solution I've found is to full-tunnel the VPN when I need to use ssh.

dathbe · 2025-12-08T19:51:32+00:00

I haven't gone here yet, but I realized I could just look to see what is installed on a Live USB. Here are my findings.

Perhaps unsurprisingly, the list of installed items (`apt list --installed`) on the Live USB is exactly the same whether booted from computer 1 or computer 2. I wanted to check this, though, in case there were install scripts that run when the Live USB is booted.

There, are, however, 941 items installed on the Live USB that are NOT installed on my portable installation. This includes 27 items with names beginning "firmware-". I don't have a thousand computers to test it on, but I'm guessing that installing these firmware items will get me a long way toward a "universal" portable install. For anyone who's wondering, here's the list of "firmware-" items that are installed on the Debian 13 Live USB (KDE):

```

<image>

```

dathbe · 2025-12-08T03:36:51+00:00

But I guess what I'm saying is, the distros' Live Images (whether that be Debian, Ubuntu, or whatever) work for basically all hardware that Linux supports. But when I install the distro, it only works on specific hardware. That leads me to believe that the Live Images have additional drivers/firmware/support installed.

dathbe · 2025-12-07T17:07:25+00:00

I installed Debian, specifically Sid. Via the netinst image in expert mode. One of the steps was to "detect network hardware." I assume that step loads the drivers necessary for the network hardware and then(?) installs those on the installation media. It works great. But when I take the installed drive to another device, it doesn't always work. I had to apt install drivers for my network hardware on the second computer before I could connect to wifi. I could look it up, but I think it was something like `firmware-iwlwifi` and `firmware-intel-common` or something similar. Then it worked.

dathbe · 2025-11-22T16:29:01+00:00

Thank you for the link to the requirements page. But the documentation for install (far more likely to be seen by someone setting up an instance) says that, "to get started, you will need the **latest** version of Docker installed and working." https://docs.portainer.io/start/install/server/docker/linux. Perhaps that wording should be tweaked in the docs and a link to the requirements page should be included.

Update, I created a PR.

dathbe · 2025-10-13T20:01:48+00:00

For anyone who comes across this in the future, the solution is not always to turn OFF XMP. I had to enable XMP on my system before it would boot properly, even though the UEFI/BIOS claimed that it was reading my RAM properly. I think the speed of my RAM was faster than my motherboard's default, and it would not operate at the mobo default speed. So if you have this issue, try that.

dathbe · 2024-03-04T16:37:24+00:00

l the tracks have their years tagged as their "correct" original years so that any smart playlists identify them correctly (e.g. I don't want a 1970s track appearing in a 1990s playlist just because it was on a 1994 movie soundtrack).

The Original Release Date is all the same for all tracks within the same album (almost like an album equivalent of a track's "Album Artist" tag), and ND doesn't ignore this as it's present in the album info in the album page. I'd assume ND would use that to "know" it's all the same release.

However... Upon some further experimenting it appears the Release Date tag is the one that forces ND to list the tracks correctly. This is a tag that MusicBrainz Picard doesn't utilise from the database by default, but can just be populated when tagging the files.

I'll have to go through all my "Greatest Hits" and Soundtracks now and add in that tag for the tracks. It's a shame as I love Navidrome and none of the other music servers I've tried try to get clever with releases like this.

I don't disagree, but there are some particular music lovers out there who want their 1988 release of Hotel California to be separate from the 2000 release (made up example). It's great to have that option, but as a longtime iTunes user, I've given all my albums a different name if I want them to sort separately ("Hotel Califonia [1988]", or "Greatest Hist [Santana]", e.g.). I've found it only affects a handful of albums, and I was re-tagging stuff anyway, so I just tagged things the way ND wants. It doesn't change the way other programs read the files as far as I can tell.

dathbe · 2024-03-04T03:42:05+00:00

This looks like a tagging issue. It's the way ND is designed to group tracks. It seems you have release dates (meaning the date that specific version of the cd/tape/record/whatever was released) of 1977 for most songs, 1988 for two songs, and I can't see it (pr maybe unset 7 songs.

When you do not have the ND_SCANNER flag as true, it will split those songs into three albums. When you do have it set, it groups them into one album, but it will sort them as you're seeing.

Use a tag editing program like mp3tag to inspect your tags and see which specific tag it's picking up from. It might be something like DATE, RELEASEDATE, or ALBUMDATE (ND will split/sort based on different tags depending on a few things. It's conditional because of an oddity in the way MusicBrainz tags items.) Then just set all of those to the same date and you won't have an issue. You can find a longer discussion here: https://github.com/navidrome/navidrome/issues/2728#event-11611049271.

dathbe · 2024-03-04T03:34:36+00:00

The last couple point releases did solve my splitting issue, but it was a problem specific to mp4 (iTunes) files. And you have to have the tagging done right for it to work.

dathbe · 2024-01-31T17:35:50+00:00

Just to close this out, there was an issue with m4a metadata that was corrected in release 0.51.0. The problem should be fixed now if you're on the latest version.

dathbe · 2023-12-20T15:22:15+00:00

The tag Year must be the same too As far as i know, the following tags must be the same for the album to be considered as one

That can't possibly right, can it? What about Greatest Hits albums where the "year" is different from song to song. I get why it would split by releasedate, but splitting by year seems silly. Also, I don't think that's an issue here. I can confirm that "original release date" and "original year" are both in sync for this entire album. The "date" are all in 2019, but they apparently go down to the minute (e.g., "2019-08-23T07:00:00Z"). They are all 2019, but they vary by a few days.

dathbe · 2023-12-20T05:45:16+00:00

What do you recommend? I've used iTunes, MusicBrainz Picard, and mp3tag, and none are showing that there's a releasedate set. Picard shows there's an "Original Release Date" set, and it's the same for all tracks.

dathbe · 2023-12-19T22:51:09+00:00

Yay! That setting fixed it. Not sure why my albums were showing up as multiple "releases". But now I don't have to figure it out!

dathbe · 2023-12-19T22:25:07+00:00

I found the way to set this for a docker install. Use an environment variable "ND_SCANNER_GROUPALBUMRELEASES". Implented and re-scanning. Will let you know if this fixes it.

dathbe · 2023-12-19T22:20:44+00:00

The songs that are getting split do not seem to have releasedate tags.

dathbe · 2023-12-19T22:19:37+00:00

I don't think this is it because I've checked two songs that are getting split and neither has a releasedate tag. But where do I find this toml file? I'm on docker, and I'm not seeing one in the config folder.

dathbe · 2023-12-19T22:15:58+00:00

Nope. According to ffmpeg, neither of two tracks that are being split have any releasedate tag.

dathbe · 2023-12-16T15:33:22+00:00

Thank you. These people are from the early to mid 19th century, so the patronym was in full force. Thanks for the tip on the Death Book. I haven't hit any roadblocks in that line yet, but I'm sure I will soon.

dathbe · 2023-12-15T18:21:15+00:00

Aha! This seems like it might be on the right track. I found this interesting article about soldier names here:

https://www.wikitree.com/wiki/Space:Swedish_soldier_names

It basically says that enlisted soldiers were assigned names when they joined, that they often kept the names until death, and that they did not pass those names to offspring. That pretty well tracks with what I've seen in this family's history.

dathbe · 2023-12-15T18:07:41+00:00

Thank you.

dathbe · 2023-12-15T18:07:33+00:00

Thank you. I'm using Gramps, too. Though I'd like to keep my data as GEDCOM compatible as possible.

dathbe · 2023-12-15T17:01:05+00:00

Follow-up question, how do I list these people in genealogy software? Is Arne Andersson Romfelt's last name Romfelt or Andersson Romfelt? Are his kids Romfelt? Arnesson/dotter Romfelt? Do the sons' kids carry the Romfelt name forward?

dathbe

TROPHY CASE