mt-dappd on multiple network interfaces

[dbeardsl]

I’ve got the mt-daapd media server up and running on a NAS device (that is aslo a router) BUT it doesn’t seem to use both network interfaces (eth0 and eth1)

I’ve got this box connected via its WAN (eth1) port to a LAN port of my linksys router.

iTunes sharing works great through the linksys router, so it’s letting multicasts through.

Is there any way to tell mt-daapd which network interface to use?
(I’m using version 0.2.4 compiled for the ARMeb architecture)

[rpedde]

@dbeardsl wrote:

Is there any way to tell mt-daapd which network interface to use?
(I’m using version 0.2.4 compiled for the ARMeb architecture)

There really isn’t with 0.2.4.

Do you have a way to compile howl? That would be the real solution, I think — to use howl as the mdns responder.

[dbeardsl]

Thanks, bummer.

I found a version of howl compiled for the ARM big endian architecture.

at
http://skrybele.wantstofly.org/fc3/RPMS.os/

But it’s in an RPM package… and I don’t have access to an RPM package system compiled for armeb. hmm.

ideas?

[rpedde]

@dbeardsl wrote:

Thanks, bummer.

I found a version of howl compiled for the ARM big endian architecture.

at
http://skrybele.wantstofly.org/fc3/RPMS.os/

But it’s in an RPM package… and I don’t have access to an RPM package system compiled for armeb. hmm.

ideas?

Do you have a working cross toolchain? I can show you where to patch it to force an interface, but you’ll have to recompile it.

[dbeardsl]

I don’t right now… but maybe in the future… but yeah, I’d like to know where to patch it. thanks.

[rpedde]

@dbeardsl wrote:

I don’t right now…

Can you use nslu2 packages? From unslung? Because I have on my todo list to submit a howl package for unslung.

[dbeardsl]

Yeah, that’s where I’ve gotten most of my packages.

I’m a frequenter of the FSG boards
http://openfsg.com

I’m actually retooling the ipkg bootstrap for the FSG right now… or trying to.

[Author]

Posts