Cannot get DLNA to work on my server

seth · 2026-07-06 06:00:39

So the network is unimpeded … it has to be the mdlna config - the only thing I can imagine is the interface limitation and the inbound not really coming from there.
Can you remove/comment the network_interface and just shut down the docker interfaces fro a moment to get them out of the way, restart minidlna and see whether that allows remote access?

PS: I absolutely love Minions ipsum, I'm going to start using it

https://bbs.archlinux.org/viewtopic.php … 2#p2303772

Al4st0r · 2026-07-10 09:46:51

Hi, sorry for the late reply, I've been busy lately...

I shut down everything, and reset everything i could. This means shutting down all docker containers (including NPM) and the docker network interfaces, I stopped ssh and stopped the cloudflare tunnel. Running `nmcli` now shows:

wlp3s0b1: connected to HOME_WIFI
        "Broadcom and subsidiaries BCM4313"
        wifi (brcmsmac), 08:ED:B9:2E:A0:DD, hw, mtu 1500
        ip4 default
        inet4 192.168.0.3/32
        route4 192.168.0.1/32 metric 600
        route4 default via 192.168.0.1 metric 600
        inet6 fe80::6ea1:e0dc:7344:2b3b/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

eno1: unavailable
        "Intel 82579LM"
        ethernet (e1000e), D4:BE:D9:2B:EB:9D, hw, mtu 1500

DNS configuration:
        servers: 192.168.0.1
        interface: wlp3s0b1

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.

Still, the dlna is not registering... I'm starting to think that this is unsolvable or it's a hardware issue? I don't know if that would make sense seeing as how the wifi itself works and stuff

seth · 2026-07-10 13:30:42

Did you also remove the "network_interface=wlp3s0b1" entry? Resp. reset the config to it's stock defaults?

It's not a hardware issue and also not unsolvable - minildna obviously reponds on the local host and netcat can operate on #8200 on the LAN route.
Something™ has to cut traffic and for all we can tell that something has to be minidlna

Arch Linux

#26 2026-07-06 06:00:39

Re: Cannot get DLNA to work on my server

#27 2026-07-10 09:46:51

Re: Cannot get DLNA to work on my server

#28 2026-07-10 13:30:42

Re: Cannot get DLNA to work on my server

Board footer