Multiple static routes that use the same next hop cause apinger issues
When you have multiple static routes that reference the same next-hop gateway we create multiple apinger targets for the same gateway, this is a static route upgrade bug. It appears to not take multiple routes into calculation.
This should be easy to fix for upgrades. People coming from 1.2.3 will hit this. People that have been using 2.0 do not have this issue, the UI does not allow for entering the same address twice.
Updated by Seth Mos over 10 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
I've coded a fix that keeps a table of what mapping we've created for the static routes.
Hope that works