On Mon, Oct 30, 2006 at 07:44:56AM -0500, Keith Mitchell wrote: > Trent Lloyd wrote: > > Hi Keith, > > On Sun, Oct 29, 2006 at 04:22:12PM -0500, Keith Mitchell wrote: > > > I've been doing some debugging on this today and traced through the code > in gdb and it looks like it is making it all the way to the sendmsg() call > and that is succeeding, but nothing still makes it out the wire. Pokign > around inside gdb, the src and dest addresses on the packets it is trying > to send out look ok to me (src is the ip address on the interface and dst > is the mDNS mcast group -- 224.0.0.251). Any idea on how to debug what is > happening once the sendmsg system call is made? I would assume sendmsg > would get a failure code if there was something wrong with the packet it > got sent and it didn't know where to send it, etc.? I even took wireshark > and looked at the physical ethernet interface just to make sure it wasn't > get sent out on the physical interface untagged and the packets didn't > show up at all (either vlan tagged or not). > > Since none of the previous versions work for me, its possible that this > has something to do with my vlan setup, but i'm not not quite sure where > to look from here. > > > Is it possible to try without VLANs on this system? > > > Yeah, I plan on trying that, I just have to schedule a down time for this > since there is other stuff running on the box. I'll try and get that done > tonight.
Hrm, if it's easier I mean I can try replicate your setup sometime soon, don't go breaking too much on our account ;) .... but if you could do that I'd appreciate it. Trent > > Also what does 'netstat -gn' say? does it show it as having jointed the > multicast groups on these interfaces? > > > It definitely joins the mcast group on all of the interfaces. My packet > traces see the igmp membership reports go out all of the interfaces so > that is indeed happening. The 'netstat -gn' confims this. > > 224.0.0.251 01:00:5e:00:00:fb vlan100 > 224.0.0.251 01:00:5e:00:00:fb vlan110 > 224.0.0.251 01:00:5e:00:00:fb vlan111 > 224.0.0.251 01:00:5e:00:00:fb vlan112 > 224.0.0.251 01:00:5e:00:00:fb vlan113 > 224.0.0.251 01:00:5e:00:00:fb vlan114 > 224.0.0.251 01:00:5e:00:00:fb vlan115 > 224.0.0.251 01:00:5e:00:00:fb vlan128 > > Cheers, > Trent > > > > Thanks. > > Keith Mitchell wrote: > > I went back and tried 0.6.10, 0.6.5, and 0.6 and saw the same thing with > all of them. So far I haven't had much luck with 0.5 since that was > before it went into the FreeBSD port system and its looking for some > older libs and such that I don't have installed. Is there anything I > can look at/debug that would help pinpoint where the problem is? > > Thanks. > > Keith Mitchell wrote: > > No, I never see anything go out even on a browse. The browse just > lists things as they are announced by the other system periodically. > > Trent Lloyd wrote: > > Hi Keith, > > Do you see *any* packets sent out by avahi at all? (e.g. if you do a > browse do you see packets go out? It's possible there > is a problem with the FreeBSD support there has been a few changes etc > and unfortunately its hard to track 100% cross platform ability. > > I would appreciate it if you could go back a few versions and try it, > e.g. give 0.6.10, 0.6.5, 0.6.0 and 0.5 a test and let me know the first > you have success in (once you find that if you could then edge forward > until you find the release that broke it it would be double plus good) > > Following that I'll see what I can do to try fix it for you. > > Cheers, > Trent > > On Fri, Oct 27, 2006 at 09:05:58AM -0400, Keith Mitchell wrote: > > > Hi, > > I've been trying to get avahi (0.6.14) up and running for the last > couple of days under FreeBSD 6.1 and have not had much success. My > setup is a little unusual in that I am running an ethernet dot1q trunk > to my machine and have several logical vlan interfaces that I am trying > to get avahi to use. The ifconfig for the main and logical interfaces > are as follows: > > sk1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > options=8<VLAN_MTU> > inet6 fe80::20c:41ff:fe1a:3c68%sk1 prefixlen 64 scopeid 0x2 > ether 00:0c:41:1a:3c:68 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > vlan100: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::213:d4ff:fe5b:d7a%vlan100 prefixlen 64 scopeid 0x6 > inet 192.168.100.3 netmask 0xffffff00 broadcast 192.168.100.255 > ether 00:0c:41:1a:3c:68 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > vlan: 100 parent interface: sk1 > vlan111: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::213:d4ff:fe5b:d7a%vlan111 prefixlen 64 scopeid 0x8 > inet 192.168.111.3 netmask 0xffffff00 broadcast 192.168.111.255 > ether 00:0c:41:1a:3c:68 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > vlan: 111 parent interface: sk1 > vlan112: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::213:d4ff:fe5b:d7a%vlan112 prefixlen 64 scopeid 0x9 > inet 192.168.112.3 netmask 0xffffff00 broadcast 192.168.112.255 > ether 00:0c:41:1a:3c:68 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > vlan: 112 parent interface: sk1 > vlan113: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::213:d4ff:fe5b:d7a%vlan113 prefixlen 64 scopeid 0xa > inet 192.168.113.3 netmask 0xffffff00 broadcast 192.168.113.255 > ether 00:0c:41:1a:3c:68 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > vlan: 113 parent interface: sk1 > vlan114: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::213:d4ff:fe5b:d7a%vlan114 prefixlen 64 scopeid 0xb > inet 192.168.114.3 netmask 0xffffff00 broadcast 192.168.114.255 > ether 00:0c:41:1a:3c:68 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > vlan: 114 parent interface: sk1 > vlan115: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::213:d4ff:fe5b:d7a%vlan115 prefixlen 64 scopeid 0xc > inet 192.168.115.3 netmask 0xffffff00 broadcast 192.168.115.255 > ether 00:0c:41:1a:3c:68 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > vlan: 115 parent interface: sk1 > > > Avahi starts up ok and does send out the multicast join on all of the > vlan interfaces as I would expect and acts like it is working from the > logs, but I never see it try to send any annoucnements out. > avahi-browse does see announcements from the macs on my network, but it > never sends out any announcements of its own. I used tcpdump on both > this machine and a mac and both machines do see the 'igmp' messages but > not any actual mdns announcements from the FreeBSD machine running > avahi. I do, however, see the mdns announcements from the mac. > > Output from 'avaha-daemon --debug': > > Found user 'avahi' (UID 558) and group 'avahi' (GID 558). > Successfully dropped root privileges. > avahi-daemon 0.6.14 starting up. > WARNING: No NSS support for mDNS detected, consider installing nss-mdns! > Loading service file /usr/local/etc/avahi/services/afp.service. > Loading service file /usr/local/etc/avahi/services/sftp-ssh.service. > Loading service file /usr/local/etc/avahi/services/ssh.service. > New relevant interface vlan115.IPv4 for mDNS. > Joining mDNS multicast group on interface vlan115.IPv4 with address > 192.168.115.3. > New relevant interface vlan114.IPv4 for mDNS. > Joining mDNS multicast group on interface vlan114.IPv4 with address > 192.168.114.3. > New relevant interface vlan113.IPv4 for mDNS. > Joining mDNS multicast group on interface vlan113.IPv4 with address > 192.168.113.3. > New relevant interface vlan112.IPv4 for mDNS. > Joining mDNS multicast group on interface vlan112.IPv4 with address > 192.168.112.3. > New relevant interface vlan111.IPv4 for mDNS. > Joining mDNS multicast group on interface vlan111.IPv4 with address > 192.168.111.3. > New relevant interface vlan100.IPv4 for mDNS. > Joining mDNS multicast group on interface vlan100.IPv4 with address > 192.168.100.3. > Network interface enumeration completed. > Server startup complete. Host name is inferno.local. Local service cookie > is 220508407. > Service "Remote Terminal on inferno" > (/usr/local/etc/avahi/services/ssh.service) successfully established. > Service "SFTP File Transfer on inferno" > (/usr/local/etc/avahi/services/sftp-ssh.service) successfully established. > Service "AFP service on inferno" > (/usr/local/etc/avahi/services/afp.service) successfully established. > > > My config: > > [server] > use-ipv4=yes > use-ipv6=no > enable-dbus=yes > disallow-other-stacks=yes > > [wide-area] > enable-wide-area=yes > > [publish] > disable-publishing=no > disable-user-service-publishing=no > add-service-cookie=yes > publish-addresses=yes > publish-hinfo=yes > publish-workstation=yes > publish-domain=yes > > [rlimits] > rlimit-core=0 > rlimit-data=4194304 > rlimit-fsize=0 > rlimit-nofile=30 > rlimit-stack=4194304 > rlimit-nproc=3 > > > Anyone know what is wrong or what I could be doing wrong here? > > Thanks. > > -- > Keith Mitchell > Email: [EMAIL PROTECTED] PGP key available upon request > > _______________________________________________ > avahi mailing list > [EMAIL PROTECTED] > [3][3]http://lists.freedesktop.org/mailman/listinfo/avahi > > > > > -- > Keith Mitchell > Email: [EMAIL PROTECTED] PGP key available upon request > > > ------------------------------------------------------------------ > > _______________________________________________ > avahi mailing list > [EMAIL PROTECTED] > [6][6]http://lists.freedesktop.org/mailman/listinfo/avahi > > > -- > Keith Mitchell > Email: [EMAIL PROTECTED] PGP key available upon request > > > > ------------------------------------------------------------------ > > _______________________________________________ > avahi mailing list > [EMAIL PROTECTED] > [9][9]http://lists.freedesktop.org/mailman/listinfo/avahi > > > -- > Keith Mitchell > Email: [EMAIL PROTECTED] PGP key available upon request > > References > > Visible links > 1. [11]mailto:[EMAIL PROTECTED] > 2. [12]mailto:[email protected] > 3. [13]http://lists.freedesktop.org/mailman/listinfo/avahi > 4. [14]mailto:[EMAIL PROTECTED] > 5. [15]mailto:[email protected] > 6. [16]http://lists.freedesktop.org/mailman/listinfo/avahi > 7. [17]mailto:[EMAIL PROTECTED] > 8. [18]mailto:[email protected] > 9. [19]http://lists.freedesktop.org/mailman/listinfo/avahi > 10. [20]mailto:[EMAIL PROTECTED] > > > > > _______________________________________________ > avahi mailing list > [EMAIL PROTECTED] > [22]http://lists.freedesktop.org/mailman/listinfo/avahi > > > > > > -- > Keith Mitchell > Email: [EMAIL PROTECTED] PGP key available upon request > > References > > Visible links > 1. mailto:[EMAIL PROTECTED] > 2. mailto:[EMAIL PROTECTED] > 3. http://lists.freedesktop.org/mailman/listinfo/avahi > 4. mailto:[EMAIL PROTECTED] > 5. mailto:[EMAIL PROTECTED] > 6. http://lists.freedesktop.org/mailman/listinfo/avahi > 7. mailto:[EMAIL PROTECTED] > 8. mailto:[EMAIL PROTECTED] > 9. http://lists.freedesktop.org/mailman/listinfo/avahi > 10. mailto:[EMAIL PROTECTED] > 11. mailto:[EMAIL PROTECTED] > 12. mailto:[email protected] > 13. http://lists.freedesktop.org/mailman/listinfo/avahi > 14. mailto:[EMAIL PROTECTED] > 15. mailto:[email protected] > 16. http://lists.freedesktop.org/mailman/listinfo/avahi > 17. mailto:[EMAIL PROTECTED] > 18. mailto:[email protected] > 19. http://lists.freedesktop.org/mailman/listinfo/avahi > 20. mailto:[EMAIL PROTECTED] > 21. mailto:[email protected] > 22. http://lists.freedesktop.org/mailman/listinfo/avahi > 23. mailto:[EMAIL PROTECTED] > _______________________________________________ > avahi mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/avahi -- Trent Lloyd <[EMAIL PROTECTED]> Bur.st Networking Inc. _______________________________________________ avahi mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/avahi
