Project

General

Profile

Actions
Copy link

Bug #111

closed
JK

addresses ending in .224-239 will not policy route

Bug #111: addresses ending in .224-239 will not policy route

Added by Jon Klinck almost 17 years ago. Updated almost 17 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Rules / NAT
Target version:
1.2.3
Start date:
10/13/2009
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
1.2.3
Affected Architecture:

Description

This was reported in the forum, and I happened to be seeing the same behavior.
http://forum.pfsense.org/index.php/topic,19763.0.html
I am running 1.2.3rc3 nano on an Alix 2D3
I can not track this to anything obvious. If I change the default route to the second WAN, I can ping addresses ending in 224-239. Note that my setup is also using private addresses on the WANs. It is a test setup, so if you would like any information or want me to try something, let me know.

CB Updated by Chris Buechler almost 17 years ago Actions
Copy link
 #1

  • Target version set to 1.2.3

I can also replicate this.

EL Updated by Ermal Luçi almost 17 years ago Actions
Copy link
 #2

  • Status changed from New to Feedback

Feedback is needed after a new patch is in.
New builds of pfSense 1.2.3 are needed since this is a kernel patch.

JK Updated by Jon Klinck almost 17 years ago Actions
Copy link
 #3

I've tested with pfSense-1.2.3-2g-20091015-0138-nanobsd.img.gz and everything is now routing correctly.

CB Updated by Chris Buechler almost 17 years ago Actions
Copy link
 #4

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom