I don't know anything about igmpproxy. I assume your question relates to this guidance from the igmpproxy(8) man page:
Code:
Since igmpproxy only uses IGMP signalling, the daemon is only suited
for situations where multicast traffic comes from only one neighbouring
network. In more advanced cases, 'mrouted' or 'pimd' is probably more
suited. The daemon is not designed for cascading, and probably won't
scale very well.
There has been no change to this port since June of 2013. The underlying system has changed.
I've looked at the port. The error message is produced by mroute-api.c, line #147 (with the OpenBSD port's patch applied):
Code:
if ( setsockopt( MRouterFD, IPPROTO_IP, MRT_ADD_VIF,
(char *)&VifCtl, sizeof( VifCtl ) ) )
log( LOG_ERR, errno, "MRT_ADD_VIF" );
See
setsockopt(2). For further assistance, you might reach out to the ports' maintainer, Markus Friedl (markus@), directly, or make an informal query on the ports@ mailing list. Either way, be sure to include a
dmesg(8) so that no one has to guess which snapshot you happen to be running.