Re: mDNS
Do you got something I can play with? On Wed, May 13, 2009 at 02:55:25PM +0200, Antoine Jacoutot wrote: On Wed, 13 May 2009, Marco Peereboom wrote: I need an mdns solution as well. If you have something working please let me know. I'm working on avahi which I intend to finish at c2k9. -- Antoine
mDNS
I've installed howl on my fileserver and enabled multicast. From linux I can do this: ko...@arcology:~$ uname -a Linux arcology 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux ko...@arcology:~$ nslookup muzkabox.local Server: 192.168.1.254 Address:192.168.1.254#53 ** server can't find muzkabox.local: NXDOMAIN ko...@arcology:~$ ping muzakbox.local PING muzakbox.local (192.168.1.66) 56(84) bytes of data. 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=1 ttl=255 time=310 ms 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=2 ttl=255 time=3.19 ms 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=3 ttl=255 time=5.26 ms 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=7 ttl=255 time=2.44 ms ^C --- muzakbox.local ping statistics --- 7 packets transmitted, 4 received, 42% packet loss, time 6025ms rtt min/avg/max/mdev = 2.441/80.299/310.295/132.792 ms but on OpenBSD I get this: $ uname -a OpenBSD splat 4.5 GENERIC#1749 i386 $ nslookup muzakbox.local Server: 192.168.1.254 Address:192.168.1.254#53 ** server can't find muzakbox.local: NXDOMAIN $ ping muzakbox.local ping: unknown host: muzakbox.local Obviously linux's resolver is checking mDNS as well as regular DNS. Is there any way to get OpenBSD doing this too? The only thing I can think is that is has to do with the 'order hosts,bind' line, though bind doesn't seem to be install on the linux box Zeroconf is really convenient for me but it's kind of useless if it's going to force me into using Linux as a desktop. To head off the stupid questions: I had my computers all with static IPs but I've moved and there's a new (very locked down) router that I can't tamper with, and names are nicer anyway. .Actually I just solved my problem a different way because I discovered the dhclient.conf:send host-name hostname; option. I'm still curious about mDNS support in OpenBSD though (and this took me a couple hours of searching, so the archives could probably use this tip). -Nick
Re: mDNS
I need an mdns solution as well. If you have something working please let me know. On Wed, May 13, 2009 at 03:26:29AM -0400, Nick Guenther wrote: I've installed howl on my fileserver and enabled multicast. From linux I can do this: ko...@arcology:~$ uname -a Linux arcology 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux ko...@arcology:~$ nslookup muzkabox.local Server: 192.168.1.254 Address: 192.168.1.254#53 ** server can't find muzkabox.local: NXDOMAIN ko...@arcology:~$ ping muzakbox.local PING muzakbox.local (192.168.1.66) 56(84) bytes of data. 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=1 ttl=255 time=310 ms 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=2 ttl=255 time=3.19 ms 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=3 ttl=255 time=5.26 ms 64 bytes from muzakbox.local (192.168.1.66): icmp_seq=7 ttl=255 time=2.44 ms ^C --- muzakbox.local ping statistics --- 7 packets transmitted, 4 received, 42% packet loss, time 6025ms rtt min/avg/max/mdev = 2.441/80.299/310.295/132.792 ms but on OpenBSD I get this: $ uname -a OpenBSD splat 4.5 GENERIC#1749 i386 $ nslookup muzakbox.local Server: 192.168.1.254 Address: 192.168.1.254#53 ** server can't find muzakbox.local: NXDOMAIN $ ping muzakbox.local ping: unknown host: muzakbox.local Obviously linux's resolver is checking mDNS as well as regular DNS. Is there any way to get OpenBSD doing this too? The only thing I can think is that is has to do with the 'order hosts,bind' line, though bind doesn't seem to be install on the linux box Zeroconf is really convenient for me but it's kind of useless if it's going to force me into using Linux as a desktop. To head off the stupid questions: I had my computers all with static IPs but I've moved and there's a new (very locked down) router that I can't tamper with, and names are nicer anyway. .Actually I just solved my problem a different way because I discovered the dhclient.conf:send host-name hostname; option. I'm still curious about mDNS support in OpenBSD though (and this took me a couple hours of searching, so the archives could probably use this tip). -Nick
Re: mDNS
On Wed, 13 May 2009, Marco Peereboom wrote: I need an mdns solution as well. If you have something working please let me know. I'm working on avahi which I intend to finish at c2k9. -- Antoine
Re: mDNS
On Wed, May 13, 2009 at 8:55 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Wed, 13 May 2009, Marco Peereboom wrote: I need an mdns solution as well. If you have something working please let me know. I'm working on avahi which I intend to finish at c2k9. Thank you!
Re: daap/mdns multicast problems
Jonathan Kent [EMAIL PROTECTED] wrote: Been trying in vain to get daap/mdns traffic through my OpenBSD 4.1 firewall to talk to my mt-daap server. From tcpdumping I can see the multicast traffic coming into sis1 interface but not coming out of the sis0 interface so I can only assume that I have missed something. As Brian already pointed out, you need to enable multicast routing. You also need a multicast routing daemon to perform the actual forwarding. mrouted(8) will do for simple purposes. I haven't tried dvmrpd(8). However, the first thing you want to check is the TTL of these mdns packets. I suspect it's 1 and they are intended as local broadcasts, not as routable traffic. -- Christian naddy Weisgerber [EMAIL PROTECTED]
daap/mdns multicast problems
Hi,
Been trying in vain to get daap/mdns traffic through my OpenBSD 4.1
firewall to talk to my mt-daap server.
From tcpdumping I can see the multicast traffic coming into sis1
interface but not coming out of the sis0 interface so I can only assume
that I have missed something.
At present I don't block out traffic (sis0) just in (sis1) on pf and
have the following simple (at present) rule to allow this traffic in:
pass in quick proto { tcp, udp } from any to 224.0.0.251 port 5353 keep
state label mdns
I'm pretty certain its not pf getting in the way so my guess here is
that I need multicast routing enabled?? Been googling for info on this
to see if that was the case but can't find much on this of help. Of
course I could be completely off here :o)
Any pointers greatly received.
Thanks
Jon
