How i modify ?
I think it's programmed "hard" in the firmware
How i modify ?
I think it's programmed "hard" in the firmware
What packaged did you install?
Have you tried DLNA name?
https://openwrt.org/docs/guide-user/services/media_server/dlna
http://manpages.ubuntu.com/manpages/cosmic/en/man5/minidlna.conf.5.html
It appears there's a few settings you may be interested in:
Just checked mine out of curiosity and in Windows 10 my wrt1200 shows as OpenWrt Router in Other Devices too even though it shows as the hostname everywhere else, strange.
yes , strange
also when i click on i have a stupid address as this :
http://192.168.1.222:5000/192.168.1.222
http://192.168.1.221:5000/192.168.1.221
http://192.168.1.251:5000/192.168.1.251
http://192.168.1.252:5000/192.168.1.252
You should check from your router, which process (app) has the port 5000 opened.
E.g.
root@router1:~# netstat -nlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1956/uhttpd
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 3651/dnsmasq
tcp 0 0 192.168.1.1:53 0.0.0.0:* LISTEN 3651/dnsmasq
tcp 0 0 87.....181:53 0.0.0.0:* LISTEN 3651/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1302/dropbear
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1956/uhttpd
tcp 0 0 :::80 :::* LISTEN 1956/uhttpd
tcp 0 0 fe80::...:c627:53 :::* LISTEN 3651/dnsmasq
tcp 0 0 fe80::...:f3e6:53 :::* LISTEN 3651/dnsmasq
Ps. My openwrt router does not show up in Windows 10. It is about some package that you have installed in your router.
Launching miniupnp seems to trigger the "OpenWRT router" items into Windows network device list. I launched miniupnp in my router and "OpenWRT router" popped up in Windows device list.
And it naturally shows up in the listening port list at port 5000:
root@router1:~# netstat -nlp | grep 5000
tcp 0 0 :::5000 :::* LISTEN 13175/miniupnpd
I was going to write that it was upnp. I was searching if there was a setting with a device name in miniupnp, but didn't found one.
The funny thing is that before actually testing with miniupnp, I glimpsed through its OpenWrt packages sources and could not find the "OpenWRT router" text, and even after testin nd noticing that it is the culprit, I still can't quickly figure out where that text is actually coming from.
(Well, I guess one must grep the source repos with that mis-cased "OpenWRT" upper case string.)
But really it doesn't make much sense to change it. I see no harm of having the same name there,
Yeah, just my curiosity. The string seems to get hardcoded into the miniupnpd binary via setting OS_NAME as OpenWRT during the build config process. That is not set in the OpenWrt side package files but gets shown in the sources after compilation and then the final string in the binary:
perus@ub1904:/Openwrt/github/packages/net/miniupnpd$ grep -r -C2 "OpenWRT" .
./patches/100-build-on-OpenWrt.patch--fi
./patches/100-build-on-OpenWrt.patch-+case $OS_NAME in
./patches/100-build-on-OpenWrt.patch:+ OpenWRT)
./patches/100-build-on-OpenWrt.patch-+ echo "#define LIB_UUID" >> ${CONFIGFILE}
./patches/100-build-on-OpenWrt.patch-+ ;;
perus@ub1904:/Openwrt/r7800/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/miniupnpd-2.1.20190408$ grep -r "OpenWRT" .
./genconfig.sh:# OpenWRT special case
./genconfig.sh: OS_NAME=OpenWRT
./genconfig.sh: OpenWRT)
./genconfig.sh: OpenWRT)
./config.h:#define OS_NAME "OpenWRT"
./config.h:#define OS_VERSION "OpenWRT/SNAPSHOT"
Binary file ./.pkgdir/miniupnpd/usr/sbin/miniupnpd matches
Binary file ./ipkg-arm_cortex-a15_neon-vfpv4/miniupnpd/usr/sbin/miniupnpd matches
Binary file ./miniupnpd matches
./Changelog.txt: Some modifications thanks to Daniel Dickinson to improve OpenWRT
./Changelog.txt: daemon now tested on a Linksys WRT54G device running OpenWRT !
perus@ub1904:/Openwrt/r7800/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/miniupnpd-2.1.20190408$ strings miniupnpd | grep OpenW
Server: OpenWRT/SNAPSHOT UPnP/1.1 MiniUPnPd/2.1
OpenWRT router
OpenWRT
SERVER: OpenWRT/SNAPSHOT UPnP/1.1 MiniUPnPd/2.1
SERVER: OpenWRT/SNAPSHOT UPnP/1.1 MiniUPnPd/2.1
OpenWRT/SNAPSHOT UPnP/1.1 MiniUPnPd/2.1
GCC: (OpenWrt GCC 7.4.0 r10641-1d2b2e744e) 7.4.0
EDIT:
It is actually coming from upstream source code that detects OpenWrt build env ans sets that string:
Based on the investigation above, you have two main options:
But like Pilot6 said, having those similar items in the listing is rather harmless.
why you have miniupnpd active in several routers inside your LAN ?
i have 2 * WR1200JS in WDS for use a distant TV or computers connected in WIFI AC
i have 2 * XIAOMI in WDS for another distant TV connected or computers in WIFI AC ( not the same channel )
my router Orange <->gigabits <-> box openwrt WDS <-> wifi AC … wifi AC <-> box openwrt WDS <-> gigabits<-> TV or computers
i can use some HDD to play movies that I saved in USB HDD boxes
for the DLNA i have not a name problem .
The name problem is only with Windows computers !!!
It is not very important but it would still be nice to have the correct name when we program it with Luci …
That is a OpenWrt bug ...
It's not a bug at all. There is no goal to show different names in Windows for uPnP devices.
And it really makes no sense to have upnp enabled on all of them.
Pilot6 -> ??? but it's not just that name problem to look at what I get when I click on well-functioning cases and an Openwrt case
with good box i have only properties when i click on
with openwrt call web page as http://192.168.1.251:5000/192.168.1.251
Disable/uninstall miniupnpd from all OpenWrt boxes except one connected to Orange router.
And what is the use of clicking on these devices?
One could argue that this is not an OpenWrt issue but I think it also fair to say that the miniupnpd behaviour is suboptimal at best. At the very least it should use a generic URL that is actually likely to be reachable.
Using http://$lanip:5000/$lanip
makes no sense under any circumstances (I actually think that this is a bug/quirk either in windows or miniupnpd misintepreting a relative URL specification somewhere).
Also hardcoding "OpenWRT" (which is actually wrongly spelled) makes no sense either. I think another issue the OP was highlighting (apart from the fact that the URL is wrong) is that miniupnpd does not report vendor and model of the device it is running on.
Edit:
I think the 404 error could be mitigated by not advertising an URL at all. The two "working" Windows 10 dialog boxes state that no device URL is available, that is what likely prompts Windows 10 to open the property dialog instead. Such a default would make sense for miniupnpd as well.
I close the subject and I consider it a bug
I think there is confusion here between:
They way I understand you, you want only the function of minidlna, but have erroneosly installed both miniupnpd and minidlna.
For distributing media to DLNA AV clients, you don't need miniupnpd.
I think OP can use the Network Drive option in Windows 10 if he/she has different drives connected to different routers. This way the drive/share shows up as a network resource in the list.