Project

General

Profile

Bug #6828

Patch for "route change" is not present on 2.4 builds using FreeBSD 11

Added by Jim Pingle 7 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Category:
Routing
Target version:
Start date:
10/11/2016
Due date:
% Done:

100%

Affected version:
2.4
Affected Architecture:

Description

On 2.3 we have a patch to alter the behavior of "route change" so that it adds a route if it's not already in the table. This patch is not present on our 2.4 builds based on FreeBSD 11, which causes various failures in areas that rely on the behavior. The most common example is a simple static IP address setup which ends up missing a default gateway.

We either need to bring back some (better) version of the old patch or change all of the calls that use "route change" which rely on the patched behavior.


Subtasks

Bug #6850: FreeBSD 11.0 Route Syntax Change For Non-Local GatewayResolvedKen Sim

Associated revisions

Revision 94bd7fb3
Added by Renato Botelho 6 months ago

Fix #6828

Until 2.3.x pfSense carried a patch that changed the behavior of 'route
change' command, making it add the route when it fails to change.
On 2.4 this patch was removed and will not be added back. This change
adjust PHP code to deal with route add / change and make it work
without the patch

History

#1 Updated by Daryl Morse 7 months ago

Jim Pingle wrote:

On 2.3 we have a patch to alter the behavior of "route change" so that it adds a route if it's not already in the table. This patch is not present on our 2.4 builds based on FreeBSD 11, which causes various failures in areas that rely on the behavior. The most common example is a simple static IP address setup which ends up missing a default gateway.

We either need to bring back some (better) version of the old patch or change all of the calls that use "route change" which rely on the patched behavior.

I believe I encountered this problem (or a variation of it) while trying to configure a hurricane electric tunnel using a recent 2.4 development snapshot. The default ipv6 route was not being created, even though the gateway was set as the default route. The tunnel comes online, but doesn't work. When you have a patch for this bug, let me know and I'll give it a try.

#2 Updated by Renato Botelho 6 months ago

  • Assignee set to Renato Botelho

#3 Updated by Renato Botelho 6 months ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

#4 Updated by Jim Pingle 6 months ago

  • Status changed from Feedback to Resolved

Routing has been fine on 2.4 in every scenario I've tried so far.

Also available in: Atom PDF