sbin/routed/input.c

172 	} else if (rip->rip_vers > RIPv2) {
173 		rip->rip_vers = RIPv2;
187 	 * RIPv2 messages, but only if configured for that silliness.
189 	 * RIPv2 authentication is lame.  Why authenticate queries?
190 	 * Why should a RIPv2 implementation with authentication disabled
191 	 * not be able to listen to RIPv2 packets with authentication, while
195 	    && rip->rip_vers == RIPv2
198 		       "RIPv2 message with authentication from %s discarded",
263 		if (rip->rip_vers == RIPv2
265 			v12buf.buf->rip_vers = RIPv2;
320 				 * we are sending RIPv2.  But do offer
326 					    trace_pkt("ignore; sending RIPv2");
346 				/* Respond with RIPv1 instead of RIPv2 if
354 				       ? RIPv2 : RIPv1,
709 			/* We can receive aggregated RIPv2 routes that must
713 			 * via other RIPv2 interfaces.
716 			 * length netmasks" lets RIPv2 listeners understand,
834 	 * from a distant RIPv2 router with the standard
979 				       "wrong MD5 RIPv2 packet length of %d"
996 					       "unknown MD5 RIPv2 auth len %#x"
1003 					       "unknown MD5 RIPv2 family %#x"
1009 					       "MD5 RIPv2 hash has %#x"