miimon, arp_interval and the code
Posted on Wednesday, 4th July, 2007 in Life
After today’s adventure with the kernel bonding, I just took a look at the code …
if (miimon) { printk(KERN_INFO DRV_NAME ": MII link monitoring set to %d msn", miimon); } else if (arp_interval) { int i; printk(KERN_INFO DRV_NAME ": ARP monitoring set to %d ms, validate %s, with %d target(s):", arp_interval, arp_validate_tbl[arp_validate_value].modename, arp_ip_count); for (i = 0; i < arp_ip_count; i++) printk (" %s", arp_ip_target[i]); printk("n"); } else { /* miimon and arp_interval not set, we need one so things * work as expected, see bonding.txt for details */ printk(KERN_WARNING DRV_NAME ": Warning: either miimon or arp_interval and " "arp_ip_target module parameters must be specified, " "otherwise bonding will not detect link failures! see " "bonding.txt for details.n"); }
If I read it right, you only get the KERN_WARNING for “either miimon or arp_interval” only if miimon or arp_interval isn’t set … but at least my config says it is .. *shrug* .. bed time for me ![]()