FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › Why Won’t mt-daapd Work Unless It’s Open to the Internet? › Reply To: Why Won’t mt-daapd Work Unless It’s Open to the Internet?
26/06/2007 at 12:57 AM
#11212
josephwinston
Guest
I have the same problem on ubuntu feisty. At startup:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
I used:
# iptables -A INPUT -s 192.168.2.0/24 -d 224.0.0.0/4 -j ACCEPT
# iptables -A INPUT -s 192.168.2.0/24 -d 255.255.255.255 -j ACCEPT
# iptables -A OUTPUT -s 192.168.2.0/24 -d 224.0.0.0/4 -j ACCEPT
# iptables -A OUTPUT -s 192.168.2.0/24 -d 255.255.255.255 -j ACCEPT
Giving:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- 192.168.2.0/24 BASE-ADDRESS.MCAST.NET/4
ACCEPT 0 -- 192.168.2.0/24 255.255.255.255
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- 192.168.2.0/24 BASE-ADDRESS.MCAST.NET/4
ACCEPT 0 -- 192.168.2.0/24 255.255.255.255
But no joy. What am I missing? Or how do I parse the spew from the logging?