Anthony Cornehl

Yup, my patch does the wrong thing, and should be doing sizeof(&rtm) instead to accomplish the same effect. On November 30, 2019 4:14:46 PM PST, Nick Briggs wrote: >nbriggs commented...

In OpenBSD, `struct rt_msghdr->rtm_addrs` and `struct ifa_msghdr->ifam_addrs` point to the same offset in the buffer. This is not true in FreeBSD, so the bitmask wasn't being passed to `get_rtaddrs` with...

> No SIGSEGVs now. It does get a bit confused if you delete the only IPv4 address off the interface it's listening on -- a situation that wouldn't have made...

I just realized that bug #31 will more easily trigger with this PR, since more addresses are added to the fixed-size array. I'll have to add a fix for that...

DNS responses from the daemon now send all addresses from all interfaces and can respond to mdnsctl with the appropriate address from any interface (eg. em0 being IPv6 only and...

After looking at the code, this is probably triggered by `PGE_RR_MAX` being set to 32 and the limit never being checked when adding reverse records via `pge_initprimary`, setting up the...

I've started work on plumbing in IPv6 at https://github.com/twinshadow/mdnsd/tree/ipv6 Right now, `mdnsd` will bind an IPv4 and IPv6 listening socket, but only the IPv4 is wired-up and `mdnsctl` can parse...

> The first thing I ran into was in mdnsd/mdnsd.c:155 where you are using a "struct sockaddr addr" for storage on the stack. It's not big enough (should probably be...

You can fix this by changing the value of `MAXPACKET` in `mdnsd/packet.c` to a larger value. I don't know the reasoning behind the current value, so I'll do some more...

Currently the functions `recv_packet` and `pkt_sendto` allocate the buffer on the stack using `buf[MAXPACKET]`. Instead, they should be allocating the buffer based on the size of the interface MTU.