We were creating the pimreg device with a
created ifindex of 255. This was causing
issues when a interface was assigned a ifindex
of 255 by the kernel. Subsuquently pim
would stay in a hosed up state.
Modify the ifindex used for the pimreg device
to be 0.
Ticket: CM-14625
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
return -1;
}
- if (ifp->ifindex < 1) {
+ if (ifp->ifindex < 0) {
zlog_warn("%s: ifindex=%d < 1 on interface %s",
__PRETTY_FUNCTION__,
ifp->ifindex, ifp->name);
* Don't come running to me if this assumption is bad,
* fix it.
*/
-#define PIM_OIF_PIM_REGISTER_VIF (MAXVIFS - 1)
-#define PIM_MAX_USABLE_VIFS (MAXVIFS - 2)
+#define PIM_OIF_PIM_REGISTER_VIF 0
+#define PIM_MAX_USABLE_VIFS (MAXVIFS - 1)
struct channel_counts