Windows 10 OpenWrt name

Installing and Using OpenWrt
22

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.

1 Like
23

I close the subject and I consider it a bug

1 Like
24

I think there is confusion here between:

  • miniupnpd - a daemon to negotiate/establish dynamic port forwardings.
  • minidlna - a daemon to distribute media in a LAN to mediaplayers.

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.

1 Like
25

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.