Project

General

Profile

Bug #1348

Multiple static routes that use the same next hop cause apinger issues

Added by Seth Mos about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Routing
Target version:
Start date:
03/13/2011
Due date:
% Done:

100%

Estimated time:
1.00 h
Affected Version:
2.0
Affected Architecture:
All

Description

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.

http://forum.pfsense.org/index.php/topic,34203.0.html

Associated revisions

Revision a6bcda39 (diff)
Added by Scott Ullrich almost 12 years ago

Be more verbose on logging so that we can correctly deterimine protocol, etc.

Ticket #1348

History

#1 Updated by Seth Mos about 8 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.
http://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/323f3f9c17d9307ab9eb820cbd05cc7629ce80b9

Hope that works

#2 Updated by Seth Mos about 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF