FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › Firefly and multiple network interfaces?
- This topic has 1 reply, 2 voices, and was last updated 17 years, 4 months ago by rpedde.
-
AuthorPosts
-
12/05/2007 at 3:23 PM #1380GonzoParticipant
Hi,
first of all: I just realized i’ve been using mt-daapd for over 1.5 years now. Thank you, Ron!
I’ve now installed a second network interface into my server so my neighbour can listen too.
I’m now using mt-daapd with the built-in zeroconf support, but the daap service only shows up on my old network, not the new one.
How do I configure mt-daapd to broadcast its service description over zeroconf to both network interfaces?
Or do I have to start two instances of mt-daapd?
Best regards,
Constantin13/05/2007 at 8:32 PM #10654rpeddeParticipant@Gonzo wrote:
Hi,
first of all: I just realized i’ve been using mt-daapd for over 1.5 years now. Thank you, Ron!
I’ve now installed a second network interface into my server so my neighbour can listen too.
I’m now using mt-daapd with the built-in zeroconf support, but the daap service only shows up on my old network, not the new one.
How do I configure mt-daapd to broadcast its service description over zeroconf to both network interfaces?
Or do I have to start two instances of mt-daapd?
Best regards,
ConstantinThe apple embeddable mdns stuff isn’t super configurable. Best is probably to use a real mdns responder like avahi or howl. (avahi is probably best).
Then configure with –enable-avahi, and you should be in business. The avahi stuff has fine configuration for what interfaces and all that.
I noticed that avahi is now in unslung, so I’ll be moving the nightlies for nslu2 to use avahi soon. Avahi is in pretty much all the distros now, too, so I may make avahi the default, and deprecate the built-in mdns.
— Ron
-
AuthorPosts
- The forum ‘Setup Issues’ is closed to new topics and replies.