On 02/04/13 11:30, Bob Williams wrote:
On 02/04/13 10:00, Togan Muftuoglu wrote:
On 04/01/2013 04:23 PM, Bob Williams wrote:
On 01/04/13 11:59, lynn wrote:
[snipped]
As you can see some files (but not .mp4s), I guess it's not a firewall problem. Nevertheless, this *may* help:
Edit the following lines in /etc/sysconfig/SuSEfirewall2
FW_DEV_EXT="eth0" # may be different interface in your case FW_SERVICES_EXT_TCP="8200" FW_SERVICES_EXT_UDP="1900" FW_SERVICES_EXT_IP="igmp"
I guess the OP is using the minidlna within the home network, so my question is why do you want these EXT_ ports and protocols to be opened to the world. If they are indeed needed than these should be INT_ but by default SuSEFfirewall2 does not protect from internal networks so they should not be needed
Last year I was having difficulty getting my minidlna traffic through the SuSEfirewall to my Bluray player attached to my router. I received a lot of help here, mainly from you [see thread in http://lists.opensuse.org/opensuse/2012-08/msg00706.html], which ended up with the above settings.
In the light of your comments, I shall try editing SuSEfirewall2, changing EXT to INT, to see if that works as well.
Bob
Actually, on further thought, I've come to the conclusion I haven't got a clue about this. From the point of view of SuSEfirewall2 running on this computer (which is running the minidlna server), my router *is* an external device. So what I want is DLNA traffic to pass unimpeded from this machine, through the router to the Bluray player/TV, without being exposed to the *real* outside world. That is, the internet cannot see that ports 8200 and 1900 are open. I need to do some homework. Bob -- Bob Williams System: Linux 3.7.10-1.1-desktop Distro: openSUSE 12.3 (x86_64) with KDE Development Platform: 4.10.1 "release 545" Uptime: 06:00am up 3 days 8:27, 3 users, load average: 0.33, 0.32, 0.32 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org