FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › mt-daapd suddenly disappears from iTunes / FreeBSD 6.2
- This topic has 25 replies, 4 voices, and was last updated 17 years, 6 months ago by rpedde.
-
AuthorPosts
-
30/05/2007 at 5:17 PM #10335fogingParticipant
@foging wrote:
Wohoo! It works, it works! Now I’m just going to idle it for a days or so and se if it still works.
Thank you so much for your help and patience!
Damn! Doesn’t work anymore 🙁 Idled it for about 3 hours and then it suddenly disappeared from iTunes. Followed the Firestarter fix-link you posted. Worked for a while….
31/05/2007 at 3:07 AM #10336rpeddeParticipant@foging wrote:
@foging wrote:
Wohoo! It works, it works! Now I’m just going to idle it for a days or so and se if it still works.
Thank you so much for your help and patience!
Damn! Doesn’t work anymore 🙁 Idled it for about 3 hours and then it suddenly disappeared from iTunes. Followed the Firestarter fix-link you posted. Worked for a while….
Did the process stop, or did it just disappear from iTunes?
If it just disappeared, did you remember to additionally allow incoming UDP on port 5353?
31/05/2007 at 11:32 AM #10337fogingParticipantDid the process stop, or did it just disappear from iTunes?
Process still running, disappeared from iTunes.
If it just disappeared, did you remember to additionally allow incoming UDP on port 5353?
Yes, at least to my knowing. Is there any way I can post my firewall settings here? I don’t know in which file to look.
Edit: corrections
01/06/2007 at 2:29 AM #10338rpeddeParticipant@foging wrote:
Did the process stop, or did it just disappear from iTunes?
Process still running, disappeared from iTunes.
If it just disappeared, did you remember to additionally allow incoming UDP on port 5353?
Yes, at least to my knowing. Is there any way I can post my firewall settings here? I don’t know in which file to look.
Edit: corrections
Something like iptables -L should do it, although it might be ugly. Also, you might want to privatize any ip addresses you don’t want to make public.
Or email it to me directly at [email protected]. That would work, too.
— Ron
01/06/2007 at 8:28 AM #10339fogingParticipantfoging@basil:~$ sudo iptables -L
Password:
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT tcp — 10.0.1.1 anywhere tcp flags:!FIN,SYN,RST,ACK/SYN
ACCEPT udp — 10.0.1.1 anywhere
ACCEPT 0 — anywhere anywhere
ACCEPT icmp — anywhere anywhere limit: avg 10/sec burst 5
DROP 0 — anywhere 255.255.255.255
DROP 0 — anywhere 255.255.255.255
DROP 0 — 255.255.255.255 anywhere
DROP 0 — anywhere 0.0.0.0
DROP 0 — anywhere anywhere state INVALID
LSI 0 -f anywhere anywhere limit: avg 10/min burst 5
INBOUND 0 — anywhere anywhere
LOG_FILTER 0 — anywhere anywhere
LOG 0 — anywhere anywhere LOG level info prefix `Unknown Input’Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT icmp — anywhere anywhere limit: avg 10/sec burst 5
LOG_FILTER 0 — anywhere anywhere
LOG 0 — anywhere anywhere LOG level info prefix `Unknown Forward’Chain OUTPUT (policy DROP)
target prot opt source destination
ACCEPT tcp — 10.0.1.6 10.0.1.1 tcp dpt:domain
ACCEPT udp — 10.0.1.6 10.0.1.1 udp dpt:domain
ACCEPT 0 — anywhere anywhere
DROP 0 — 255.255.255.255 anywhere
DROP 0 — anywhere 0.0.0.0
DROP 0 — anywhere anywhere state INVALID
OUTBOUND 0 — anywhere anywhere
LOG_FILTER 0 — anywhere anywhere
LOG 0 — anywhere anywhere LOG level info prefix `Unknown Output’Chain INBOUND (1 references)
target prot opt source destination
ACCEPT tcp — anywhere anywhere state RELATED,ESTABLISHED
ACCEPT udp — anywhere anywhere state RELATED,ESTABLISHED
ACCEPT 0 — 224.0.0.251 anywhere
ACCEPT 0 — 10.0.1.0/24 anywhere
ACCEPT tcp — 224.0.0.251 anywhere tcp dpt:mdns
ACCEPT udp — 224.0.0.251 anywhere udp dpt:mdns
ACCEPT tcp — 10.0.1.0/24 anywhere tcp dpt:sunrpc
ACCEPT udp — 10.0.1.0/24 anywhere udp dpt:sunrpc
ACCEPT tcp — 10.0.1.0/24 anywhere tcp dpt:nfs
ACCEPT udp — 10.0.1.0/24 anywhere udp dpt:nfs
ACCEPT tcp — anywhere anywhere tcp dpt:ssh
ACCEPT udp — anywhere anywhere udp dpt:ssh
ACCEPT tcp — anywhere anywhere tcp dpt:daap
ACCEPT udp — anywhere anywhere udp dpt:daap
ACCEPT tcp — anywhere anywhere tcp dpt:1412
ACCEPT udp — anywhere anywhere udp dpt:1412
ACCEPT tcp — anywhere anywhere tcp dpt:6881
ACCEPT udp — anywhere anywhere udp dpt:6881
ACCEPT tcp — anywhere anywhere tcp dpt:mdns
ACCEPT udp — anywhere anywhere udp dpt:mdns
LSI 0 — anywhere anywhereChain LOG_FILTER (5 references)
target prot opt source destinationChain LSI (2 references)
target prot opt source destination
LOG_FILTER 0 — anywhere anywhere
LOG tcp — anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN limit: avg 1/sec burst 5 LOG level info prefix `Inbound ‘
DROP tcp — anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN
LOG tcp — anywhere anywhere tcp flags:FIN,SYN,RST,ACK/RST limit: avg 1/sec burst 5 LOG level info prefix `Inbound ‘
DROP tcp — anywhere anywhere tcp flags:FIN,SYN,RST,ACK/RST
LOG icmp — anywhere anywhere icmp echo-request limit: avg 1/sec burst 5 LOG level info prefix `Inbound ‘
DROP icmp — anywhere anywhere icmp echo-request
LOG 0 — anywhere anywhere limit: avg 5/sec burst 5 LOG level info prefix `Inbound ‘
DROP 0 — anywhere anywhereChain LSO (0 references)
target prot opt source destination
LOG_FILTER 0 — anywhere anywhere
LOG 0 — anywhere anywhere limit: avg 5/sec burst 5 LOG level info prefix `Outbound ‘
REJECT 0 — anywhere anywhere reject-with icmp-port-unreachableChain OUTBOUND (1 references)
target prot opt source destination
ACCEPT icmp — anywhere anywhere
ACCEPT tcp — anywhere anywhere state RELATED,ESTABLISHED
ACCEPT udp — anywhere anywhere state RELATED,ESTABLISHED
ACCEPT 0 — anywhere anywhereIs everything OK with the configuration?
03/06/2007 at 8:35 PM #10340rpeddeParticipant@foging wrote:
Is everything OK with the configuration?
Ya, that looks right. Might be instructive to look at your logs though, and see if anything is being blocked. You are logging drops, so check your syslog and see if you are dropping anything that looks mdns-ish. To or from 224.0.0.251 on port 5353. That’s what is broken.
— Ron
-
AuthorPosts
- The forum ‘Setup Issues’ is closed to new topics and replies.