FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › mt-daapd over subnet in other network range
- This topic has 4 replies, 2 voices, and was last updated 17 years, 5 months ago by rpedde.
-
AuthorPosts
-
09/06/2007 at 10:33 PM #1458bbreukelenParticipant
Hi there,
I’ve been using mt-daapd to share my music and playlist throughout my house.
Recently I changed my network setup and now is doesn’t work anymore.I created two networks, one for wired clients and one for wireless in between is a gateway routing all traffic.
I did this to allow guests and others to access the internet using my WIFI access-points without being able to reach my local network.
The trusted clients (my and my girlfriend’s laptop) are allowed to forward any traffic over the networks through the gateway by mac address.This works for every application but not for mt-daapd.
This seems strange to me because the two networks are in the same subnet.Subnet: 255.255.255.0
Network wired: 10.0.0.*
Network WIFI: 138.0.0.*What can I do to share music? I have a NAS server running mt-daapd and I connect to it using a Win XP laptop and a Powerbook G4.
Thanks in advance,
Boudewijn
11/06/2007 at 4:44 AM #11074rpeddeParticipant@bbreukelen wrote:
Hi there,
This works for every application but not for mt-daapd.
This seems strange to me because the two networks are in the same subnet.If they don’t have the same ip addressing scheme, then they aren’t on the same subnet. Based on what you wrote below, they aren’t on the same subnet. They get routed through your wireless router.
In order to see multicast between different subnets, you need a router that will pass multicast traffic. Check your router and see if it has configuration to enable multicast.
— Ron
17/06/2007 at 1:26 PM #11075bbreukelenParticipantHi Ron,
Thanks for the reply. You’re right. I was a bit of there. I actually meant they are in the same subnet mask. But yes, in different subnets.
I looked into forwarding multicast traffic on my gateway debian box but with no success. I found traffic on 224.0.0.251 which is mDNS I think and that’s probably the traffic which needs to be forwarded.
Any pointers on how this can be done?Thanks,
Boudewijn
17/06/2007 at 1:59 PM #11076bbreukelenParticipantI found the solution.
Very simple realy.
I installed avahi-daemon
apt-get install avahi-daemonIn avahi-daemon.conf I changed:
enable-reflector=yes
reflect-ipv=yesThat did the trick.
Cheers
20/06/2007 at 1:13 AM #11077rpeddeParticipant@bbreukelen wrote:
I found the solution.
Very simple realy.
I installed avahi-daemon
apt-get install avahi-daemonIn avahi-daemon.conf I changed:
enable-reflector=yes
reflect-ipv=yesThat did the trick.
Cheers
Wow.. you have ipv6-only machines?
-
AuthorPosts
- The forum ‘Setup Issues’ is closed to new topics and replies.