T4 miniDLNA setting up multiple Share Folders

[Crucible]

This seems to be a bug in the T4 miniDLNA setup, but I couldn't find any mention of it in forums, so it might be my mistake.

I tried to add an extra Share Folder to the miniDLNA configuration. It seemed the mechanism is to navigate to the folders, choosing them with "Select" (yellow). When all were selected, choose "Save" (green). then "Save" (red?!). The list of selected folders then appears in the "Share Folders" box as a comma separated list. If I then attempt to stop and restart the service using the green button, it remains in "Stopped" state.

Looking at the file /etc/minidlna.conf, the comma separated list has been entered as a "media_dir=" line. The comments say this is incorrect. The folders should be specified as multiple "media_dir=" lines.

Code: Select all

# set this to the directory you want scanned.
# * if have multiple directories, you can have multiple media_dir= lines
# * if you want to restrict a media_dir to a specific content type, you
#   can prepend the type, followed by a comma, to the directory:
#   + "A" for audio  (eg. media_dir=A,/home/jmaggard/Music)
#   + "V" for video  (eg. media_dir=V,/home/jmaggard/Videos)
#   + "P" for images (eg. media_dir=P,/home/jmaggard/Pictures)
media_dir=/media/hdd/Recordings/, /media/hdd/movie/

If I edit the .conf file directly, splitting the line, the server will start, the folders are served correctly, but only the second (last?) line is displayed in the miniDLNA setup display.

Easy to fix, but only by editing files. Perhaps I've just misunderstood the setup GUI?

[prl]

... the miniDLNA configuration. ... "Save" (green). then "Save" (red?!). ...

Bug #327: Poor coloured button choice in DLNA server setup screen

[prl]

I've had time to go back and have a look at the main problem, and I can confirm both that the problem is there and that it can be worked around in the way you describe.

Bug #412: Configuring multiple shares in DLNA server setup causes miniDLNA server to fail.

[prl]

Also found a couple of other bugs in miniDLNA setup:

• From MENU>Setup>Setwork>Network services>DLNA server, if you do MENU, then RED Save immediately, without making any changes, the "media_dir" setting value is removed (i.e. media_dir=).
• From MENU>Setup>Setwork>Network services>DLNA server, MENU, GREEN Shares should have ticks on directories that are already in the "media_dir" settings, but it doesn't.

[prl]

I've submitted fixes to:
#327: Poor coloured button choice in DLNA server setup screen
Bug #412: Configuring multiple shares in DLNA server setup causes miniDLNA server to fail
to the code repositry.

Th fixes for #412 also include fixes to the oher bugs in my previous post.

[Swanny]

I got all my gear networked nicely and recordings through miniDLNA onto my iPad.
The internet crashed ans the network restarted, most ip addresses were reassigned excepting the router and Fetch!
The miniDLNA as disappeared off my iPads and I have lost connection and can't see either T4s on VLC.

Is it possible to get miniDLNA going again? It was all going so well

I did set up T4 shares folders on the IMac. Is this the problem. The posts above suggest it might be. It seems to have coincided with the outage and network restart and the shares folder set up. If so how can I delete the folders and reset the miniDLNA to work.

[Bluebird]

Swanny,
Maybe you should think about assigning permanent ip addresses to the mac numbers of your various devices.
Then if your router restarts, everything is where it was before.

[Swanny]

Yes that is a good idea. I am sure the Fetch has a fixed address as it always retains its 10.1.1.6.
I have opened my modem/router but I could not find the list to fix.
Some pointers would be helpful.

I have I think created a static address on one of the T4s
I left its current IP address as (10.1.1.13) and deselected automatic
i left the other numbers as found on the dynamic window
It might work!

I seem to be posting a lot, it is important to me to make the most of the T4s. So far so good.

[Grumpy_Geoff]

I have opened my modem/router but I could not find the list to fix.
Some pointers would be helpful.

We could give some if only we knew what your modem/router brand/model was

I have I think created a static address on one of the T4s
I left its current IP address as (10.1.1.13) and deselected automatic
i left the other numbers as found on the dynamic window
It might work!

Yep, that'd work, but given your list of equipment (viewtopic.php?f=43&t=9489&p=126827#p126827), I think it's better to have a central place to have these IP addresses assigned (i.e. IP address reservation in your modem/router)

[Swanny]

The modem router is a Boblite by iinet.
I have found in its pages the DHCP list. The headings on the table are I shall type them vertically

Client number. E.g. 1
IP Address. 10.1.1.3
Name Tivo
Mac Address. Lots of alphanumeric
Wireless or Ethernet
Fixed IP to that unit (check box)
Release IP. Blue text
On line or not.

I am guessing that I check the "fixed box" to make the IP address fixed.

[prl]

... I am guessing that I check the "fixed box" to make the IP address fixed.

That's almost certainly the way to do it.

But I thought DLNA had a server discovery protocol and it shouldn't matter if the servers change their addresses.

[Swanny]

Thank you all for pushing me beyond my comfort zone.
I won't make any changes but I will make a note of how to if I continue to have problems.

VLC and AV Player still have not been able to reconnect with the 2 Wizes as they were before the major network restart.
I think the Mini DLNA is not working Not much I can do. It may reset.

I did notice that although on the major reset the Wiz 1 was assigned 10.1.1.13
In its setup/network/ it was still showing 10.1.1.27. I set that to Static 10.1.1.13 in the Wiz.

This is what makes me feel static addresses like the Fetch which always is seen may be the way to go.

[peteru]

If you assign static IP addresses on individual devices and those addresses are in the same range as the router uses for DHCP assignments, you are guaranteed to have trouble on your entire network.

These days, static IP address allocation is almost always not a good choice.

The best way to manage IPs is through the "fixed IP" option on your router.

[Grumpy_Geoff]

The modem router is a Boblite by iinet.
I have found in its pages the DHCP list. The headings on the table are I shall type them vertically ...

That appears to be the place to enter details for the IP address reservation. What you want to achieve is every time a device asks the router for an IP address (DHCP enabled), the router gives it the same IP address based on the requesting device's MAC address.
The IP address that you reserve for each device should be outside the range that the router would assign if a reserved entry is not present. The range should already be defined in the Bob Lite - Local area network settings / 4 Set your IP address pool here: / 4a. IP range start: / 4b. IP range finish:
Once you've noted the DHCP pool range, go back to the DHCP list and enter the MAC address for each device that you want to have a reserved (fixed) IP address and enter the unique IP address for it, and 'Fix' it. You probably want to reserve the addresses for your - Fetch, iMac, Tivos, and T4s.
If the Bob Lite won't let you enter the MAC and IP addresses, then just 'Fix' the relevant entries.

After you've made the reservation entries, you'd need to restart the devices so they'd get the new IP address.

[Swanny]

Thank you, I found the window.
The range seems excessive - 10.1.1.2 to 10.1.1.254.
It would mean that I set IP addresses for critical units to numbers above 10.1.1.254.

[prl]

Thank you, I found the window.
The range seems excessive - 10.1.1.2 to 10.1.1.254.
It would mean that I set IP addresses for critical units to numbers above 10.1.1.254.

Most routers let you change the DHCP range.

If your netmask is 255.255.255.0 there are no usable addresses above 10.1.1.254. 10.1.1.255 is reserved for broadcast. There are no addresses available below 10.1.1.2, either. Your router will almost certainly be 10.1.1.1 and 10.1.1.0 is reserved as the wildcard "any address (on the network").

[Grumpy_Geoff]

The range seems excessive - 10.1.1.2 to 10.1.1.254.
It would mean that I set IP addresses for critical units to numbers above 10.1.1.254.

I suggest you set the upper address to something like 10.1.1.99, and start your reserved IP addresses above that - that way you'd know what device/reserved addresses are working and what devices are still getting a randomly assigned IP address.

[Gully]

It might be worth checking before changing the range though as that was my practice using a Billion router/modem which I tried to apply to my TP-Link but it turns out that with TP-Link the DHCP allocation and fixed IPs happen within the same range and it causes problems to do otherwise.

[peteru]

You are complicating things too much.

For any device that will be connected to your home network permanently:
* ensure that the device is using automatic DHCP configuration
* reboot the device
* select the "Fix IP" checkbox on your router config screen for that device

For any other device (such as friends phones, when they visit):
* ensure that the device is using automatic DHCP configuration
* do nothing on your router

For all devices connected to your network:
* ensure that the device is using automatic DHCP configuration

Never mind about the DHCP IP range. As long as the router gives an address to only one device, you'll be fine. The problems will start if you configure an IP manually on a device - so don't do it.

P.S. - Yes, I know I keep repeating myself, but "make sure everything is configured for DHCP"

[Swanny]

Thank you Grumpy_Geoff, Gully and peteru,
I do not take your wisdom lightly and appreciate your contribution to the Forum.
It makes the BWs so expansive.
I proceed carefully.

peteru's advice seems to be to make sure all permanent units are set to automatic and restart if changed, in fact all units. I have done this but Fetch I am not sure of I think it is sort of fixed as 10.1.1.6 as it never changes, so I can make that it's fixed address?
Go to the IP allocation page in BobLite and check the 'fixed' check box for permanent units such as Airport and the BWs etc. That is don't create any new addresses used the allocated ones.
Restart all devices.
If I have misunderstood this let me know.

[peteru]

Go to the IP allocation page in BobLite and check the 'fixed' check box for permanent units such as Airport and the BWs etc. That is don't create any new addresses used the allocated ones.
Restart all devices.
If I have got misunderstood this let me know.

That is correct.

However, you should first configure all your devices for DHCP, then restart them, then go to the router to "fix" their IPs.

The order is important, you want to make sure that the addresses you are "fixing" are actually the addresses that are in use at the time.

[Swanny]

Yes, I have printed all this info.
I have not fixed any addresses as yet, I may not need too.
I am beginning to think the real problem is in the T4 miniDLNA.
My network is now quite stable and the IP locations remain consistent (I used Fing to check)
A third TV on the network can see the T4 recordings but says " unable to play, check network"
The VLC player cannot see them at all. The miniDLNA symbol not longer appears (penguin I think)
The AVPlayerHD cannot see the miniDLNA symbol either and T4 folders
Fetch appears eventually.
I blamed the internet outage and the fiddling before I realized the Internet was down.
In this down time I did get the miniDLNA working and both T4s were accessible on the VLC and AVPlayerHD and recordings playable.
I also set up Window Shares on the IMac. This may have caused the miniDLNA on the T4s to fail (this thread)
The T4s see each other and we can play recordings from either on TVs.
In SetUp somewhere the "shares" folder has a small blue symbol on it but the folder is not accessible.
I don't know if the Setting up the shares on the iMac interfered with the shares folder on the T4s, if so I don't know how to undo it.
For a while it all worked very well but it is not working now.
It just may be in the too hard basket and I will accept this if it is so.

[scotty]

Could the problem be that there are two DLNA servers on the network called "miniDLNA" which are conflicting?

Not sure exactly how DLNA discovery works but it may be worth changing the name of one or both of them on the two T4s to be something different. It will also have the added benefit of being able to more easily identify which T4 you're accessing.

The name can be changed in the DLNA setup screen.

Scotty

[prl]

Could the problem be that there are two DLNA servers on the network called "miniDLNA" which are conflicting? ...

I'm not sure about the details of DLNA server discovery, but it sounds like that could be the problem.

I asked about why the IP addresses should matter when DLNA has a mechanism to find the IP addresses of servers earlier on in this discussion, but no-one seemed to be interested in the question.

[peteru]

Could the problem be that there are two DLNA servers on the network called "miniDLNA" which are conflicting?

It should not matter. I've had four "miniDLNA" servers on the network and the only issue is figuring out which one you want to select.

[Swanny]

The panic is off a bit.
The WizOz app has decided to play recordings from both T4s without pixilation.
The only downside is that the other apps showed subtitles.
But we do get a good picture and the UK English dialogue is clear.

Thanks so much
I will still work to a solution

Update: we had to turn off the power today for some other work.
When power was restored one of the T4s appeared on the VLC miniDLNA.
I think the reboot may have done it to one of them. But not the other.
I think I will leave well alone and be happy with one.
Update 2. Rebooted the second T4 and the miniDLNA appeared on the VLC player so all is up and running again.
I am very impressed with the T4s