Running mt-daapd on openWRT

[rpedde]

@steinb_i wrote:

yes! iTunes finds another mt-daapd that is running on a Ubuntu sysytem. The problem must be on the openWRT system

It might be that it doesn’t see the interfaces right… they have some kind of crazy interfaces on those — vlans, etc.

Do you have a howl or a avahi package for that platform? Maybe you can use howl or avahi for advertisement and then run mt-daapd without the mdns advertiser (-m)

[steinb_i]

there is a howl package, but i have no idea how to use that thing! 😉

[rpedde]

@steinb_i wrote:

there is a howl package, but i have no idea how to use that thing! 😉

Should be able to install the howl package and set a mDNSResponder.conf (int /etc/howl?) that looks like:

My-server _rsp._tcp local. 3689

My-server _daap._tcp local. 3689

Then run the mDNSResponder and it should show up in iTunes, even without mt-daapd running (course, you won’t be able to connect…)

Then start mt-daapd with the -m argument, and it will not try to advertise mdns.

— Ron

[steinb_i]

hmmm! interessting:

root@OpenWrt:~# mDNSBrowse
[assert] error: 146 (Connection refused)
[assert] where: “socket.c”, “sw_socket_tcp_connect”, line: 720

could that be the prolem with mt-daapd?

[rpedde]

@steinb_i wrote:

hmmm! interessting:

root@OpenWrt:~# mDNSBrowse
[assert] error: 146 (Connection refused)
[assert] where: “socket.c”, “sw_socket_tcp_connect”, line: 720

could that be the prolem with mt-daapd?

certainly seems to be a problem of some kind, although I’m not sure what that is. Firewalled against localhost? Hostname set to the external interface, not the internal interface?

[Author]

Posts