• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

[dlna-filter] Filter out DLNA traffic to prevent crashes.

MymsMan said:
By default on installing dlna-filer the humax server becomes invisible unless you specify the ip address of a least one other server in settings
Click to expand...
That's the whole point of it... to stop incoming traffic crashing the Humax server.
MymsMan said:
It seemed to me that instead of needing to find server addresses it would be more user friendly to have a seting that effectively says don't filter out the humax.
Click to expand...
It's incoming client addresses that you are filtering. If you want to black-list one or more clients, just put their IP addresses in the config., then everything apart from them is allowed but they are not. I do think it would be useful to have white-list functionality as an alternative to black-list though (so everything apart from the ones you specify would be blocked).
If you want to play with iptables manually, then you can do stuff like iptables -I INPUT 1 -p tcp --dport 50001 -s ip.ad.dr.ess -j ACCEPT to add white-list items without rebooting. These are NOT persistent.
iptables -L INPUT gives you a list of what's happening - order is important!

You can find out what's incoming by installing tcpdump and then running it with tcpdump tcp dst port 50001 and see what you get. Then you stand a chance of working out the incomer that causes crashes.

If the client you want to connect from causes the server to crash, then you are just plain out of luck.
 
Last edited:
BH wrote:
It seems that the crashes are induced by the DLNA service discovery transactions from some servers. ...
Click to expand...

What I assumed too. But I read that the service discovery function (this would be the spec from the era of the Humax implementation: https://openconnectivity.org/upnp-specs/UPnP-arch-DeviceArchitecture-v1.1.pdf) is a basic UPnP function using SSDP on port 1900. So there must be some DLNA thing on top of that that is being blocked on 50001, and plainly doing that also blocks player connections.
 
I'm adding this on the end of what i think is the most relevant previous post. Please excuse me if this in improper etiquette.

I've been suffering synchronised crashes across multiple boxes for some time now and tried various things to no avail.
My first assumption was that this was the DLNA discovery problem (port 1900 UDP packets) so I installed dlna-filter on all boxes with no change to it's settings but the crashes still occur.
The crashes usually happen once a week and all occur mostly within a 30 minute timeframe. I'm assuming they are all seeded at the same time but that they eventually crash dependent on what else is happening on the box.
Currently, the crashes happen, mostly on a Monday between 3pm and 4pm and the boxes reboot and continue, as far as I can tell, normally but I usually run fix-flash-packages to be sure.
Not being sure of the underlying technology used by dlna-filter, I tried entering the IP addresses of the devices on the network (comma delinited) that show as network attached devices in the media list (blue button on RC) into the settings.
This approach was terminated due to the fact that I could only enter 15 IP addresses into the box in the settings.
I'm now doubting that this is caused by DLNA by the number of people that say the their problems went away after installing dlna-filter.

Anyone any ideas on how to proceed? I am going to remove the ethernet cable from one of the boxes to isolate it from the network to see if it stays up when the others crash.
From the previous crash dumps I've tried to investigate the crash is caused by a segmentation fault in humaxtv.
 
Last edited:
You must log in or register to reply here.
Back
Top