With 2 Openwrt / Xiaomi i have the same name " OpenWrt Router "in others peripherals as this
How i change this ?
For dlna no problems i have not the same name
Thanks for infos
System -> System -> Hostname
in Luci
1 Like
That is not Luci for HostName i have already changed to XIAOMI-WDS-221 & XIAOMI-WDS-222 ( as for DLNA name )
I have also changed the shared network USB disk host name to XIAOMI-221 & XIAOMI-222
vgaetera >
Tested not the solution
I think it's programmed "hard" in the firmware
Sure that is in OpenWRT
I add 2 * WR1200JS and i have 4 * Openwrt router !!!
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:
- friendly_name
- model_name
- model_number
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
1 Like
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:
3 Likes
Based on the investigation above, you have two main options:
- disable miniupnpd in your routers.
- Ps. It is hard to understand why you have miniupnpd active in several routers inside your LAN (unless you have multiple WAN connections from different routers and you really need them all to be UPnP enabled...)
- compile personalised miniupnpd versions for each router, patching the string differently for each router
- (that of course assumes that you can/will patch the miniupnpd sources otherwise to still compile correctly after you change the detected target OS that is utilised in the compilation. Or you could look more closer to the sources and patch directly that place where the "router" is added to the shown string.)
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.
1 Like
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
- it does not matter but …
Disable/uninstall miniupnpd from all OpenWrt boxes except one connected to Orange router.
2 Likes
And what is the use of clicking on these devices?
1 Like