Posted: Sun Dec 24, 2023 13:30 Post subject: Getting DLNA server visible to the LAN?
I had a look through the dd-wrt tutorials, found the one on getting USB and file sharing working, but nothing on Mini DLNA. I've found how-to's on Mini DLNA on on dd-wrt
on other sites but they're extremely out of date.
I'm setting up Mini DLNA to use a drive connected to my router's USB 3 port. I have successfully shared two folders using SMB and have them mounted on a Windows 10 system that is connected by Ethernet cable to the router. I've also confirmed that Mini DLNA is running on the router via its status webpage.
What's not happening is Windows isn't seeing the DLNA server. Nor is my phone when connected by WiFi to the router. VLC on it does see DD-WRT and in that it only sees one of the two shares, and claims it's empty despite there being a folder of video files the phone is capable of playing. Windows sees the two shares mounted as drives, and their contents, with full read/write access.
What's next to make the DLNA server visible to the LAN outside the router?
Another issue is routing DLNA across subnets on different IP ranges.
Since T-Mobile Home Internet apparently hates Samsung Smart TVs (both the Silver Cylinder and Black Cuboid refuse to give my TV an IP address etc) I resorted to using an EA2700 with old stock firmware from before they removed bridge support. (I have used the last dd-wrt for it but the lack of 5Ghz was a bit too crippling.)
Well yesterday the EA2700 up and went *poof*. So the only thing I had handy with the capability to wirelessly work with the TV is an old RAVPOWER router in WISP mode. I set it up to connect wirelessly to both the T-Mobile device and other devices. Worked perfectly with everything *except the TV*. T-Mobile still ragging on the Samsung.
So I put the Ravpower by the TV and hooked it up with a cable. Good to go, back on YouTube.
The problem is the Ravpower router does not allow its LAN and WAN/WiFi to be on the same IP range, but it transparently routes internet traffic across. LAN traffic? That's a No from it. I can share stuff on my PC but nothing connected by cable to the Ravpower can see it. Connected by WiFi it works because it's in the 192etc range. I haven't yet tried the TV to see if it sees the DLNA server but I'm confident it will not because I previously tried using the Ravpower router where my current office router (the one I'm setting up DLNA on now) is and ran into its brick wall inability to allow non-internet traffic through. (The Saga of the 2011 Mac Mini OMV/DLNA Server is another story, but its sudden onset of not functioning is the reason for attempting DLNA on the router.)
WiFi / T-Mobile / rest of my LAN is in 192.168.12.xxx while the Ravpower's LAN side is 10.10.10.xxx
So I assume what's needed is a way for Mini DLNA (once it's working properly so it's visible outside the router) to 'convince' the Ravpower box that it's *internet* traffic so it will get routed across the 192etc / 10etc division.
The Ravpower router also supports DLNA but it only has a USB 2.0 port and I don't know if the bloody (its housing is red) thing makes its own DLNA accessible to both its WiFi and LAN sides. So that feature is turned off.
The *simplest* solution would be running a cable under the house between TV and T-Mobile Black Cuboid but at my age and state of health, that's far from the *easiest* solution.
