Thanks for the info! Forgot about few such examples, such as sources don't signal so there is a timeout counter for (s,g) that need to be monitored, traffic utilization that might trigger SFP and I guess many more....
On Mon, Dec 11, 2017 at 11:33 PM, Claudio Jeker <cje...@diehard.n-r-g.com> wrote: > On Tue, Dec 12, 2017 at 02:32:06PM +1000, David Gwynne wrote: > > > > > On 12 Dec 2017, at 02:41, Dan Shechter <dans...@gmail.com> wrote: > > > > > > I know I am about to be hammered here but... > > > > > > Without reading the sources, and being a Cisco admin, I am asking this > > > question: What PIM got to do with the kernel? PIM is just a > > > signaling/routing protocol, like OSPF/BGP. It should just update the > mroute > > > tables. > > > > i have wondered that too. maybe it still works? > > > > The problem is that multicast needs a bit more then just a lookup table. > The signaling includes joining and leaving of groups but also traffic flow > information. PIM extended the ioctl interface that mrouted used to enable > some of the advanced features (and maybe also to just be a bit > better/different). I'm for sure no fan of the ioctl() interface used for > those protocols and would prefer to use a routing socket for that (but > that's just my opinion). > > > > > > > Is it about the register unicast? > > > > > > On Sun, Dec 10, 2017 at 8:59 AM, Joachim Nilsson <troglo...@gmail.com> > > > wrote: > > > > > >> Hi, > > >> > > >> my name i Joachim and I'm the current upstream maintainer of the > > >> original pimd[1] and mrouted[2] multicast routing daemons. > > >> > > >> First of all, I'd like to give a huge thank you to the OpenBSD team > > >> for all the hard work you put in with Stanford to relicense mrouted > > >> under a BSD license[4]! I don't think you know this, but your work > > >> also freed pimd[1], which in large parts is based on mrouted. > > >> > > >> Now, I've got a few worried questions recently about the removal[3] > > >> of PIM support in OpenBSD, so I thought I'd ask here. Why have you > > >> removed it? I'd be very happy if someone could just fill me in, or > > >> provide a pointer to a mailing list discussion (I couldn't find any). > > >> At the very least I'd like to have up to date information to provide > > >> my users. > > >> > > >> There are currently three major open source PIM implementations for > > >> UNIX that I know of: pimd[1] which today supports both PIM-SM and > > >> PIM-SSM, Xorp pimd[5] (PIM-SM only), and the Quagga PIM-SSM only > > >> pimd[6]. All of them support(ed) OpenBSD, and at least I tested > > >> regularly on OpenBSD. I think the community could greatly benefit > > >> from keeping the PIM kernel support, however, I do understand that > > >> you primarily only support your in-tree applications, like mrouted. > > >> > > >> Best regards > > >> /Joachim Nilsson > > >> > > >> [1]: https://github.com/troglobit/pimd/ > > >> [2]: https://github.com/troglobit/mrouted/ > > >> [3]: https://marc.info/?l=openbsd-cvs&m=148240469327159 > > >> [4]: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/ > mrouted/LICE > > >> NSE > > >> [5]: https://github.com/greearb/xorp.ct/ > > >> [6]: https://github.com/FRRouting/frr/ > > >> > > >> > > > > -- > :wq Claudio >
