Project

General

Profile

Actions

Regression #12110

closed

PHP error in firewall_nat.inc on line 329

Added by Dan W 4 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Rules / NAT
Target version:
Start date:
07/06/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
21.09
Release Notes:
Force Exclusion
Affected Version:
2.6.0
Affected Architecture:

Description

This seems to be happening when adding ICMP rules to two separate WANs.

Can't get them both to respond to ping requests.

I'm stuck on one or the other.

All other rules seem ok.

Crash report begins.  Anonymous machine information:

amd64
12.2-STABLE
FreeBSD 12.2-STABLE devel-12-n226655-5bff64636ea pfSense

Crash report details:

PHP Errors:
[06-Jul-2021 18:53:57 Europe/London] PHP Warning:  Invalid argument supplied for foreach() in /usr/local/pfSense/include/www/firewall_nat.inc on line 329
[06-Jul-2021 18:55:00 Europe/London] PHP Warning:  Invalid argument supplied for foreach() in /usr/local/pfSense/include/www/firewall_nat.inc on line 329

No FreeBSD crash data found.

Files

PHP_errors (1).log (308 Bytes) PHP_errors (1).log Dan W, 07/06/2021 02:13 PM
Actions #1

Updated by Jim Pingle 4 months ago

  • Tracker changed from Bug to Regression
  • Subject changed from 2.6.0 to PHP error in firewall_nat.inc on line 329
  • Assignee set to Steve Beaver
  • Plus Target Version set to 21.09
Actions #2

Updated by Steve Beaver 4 months ago

  • Status changed from New to Feedback
  • Assignee changed from Steve Beaver to Dan W

Fix should appear in 7/07 development snapshot

Actions #3

Updated by Steve Beaver 4 months ago

  • % Done changed from 0 to 100
Actions #4

Updated by Jordan Greene 3 months ago

tested on plus 21.09.a.20210708.1151 - added icmp rules on separate WAN and successfully pinged one from the other

Actions #5

Updated by Renato Botelho 3 months ago

  • Status changed from Feedback to Resolved
Actions #6

Updated by Jim Pingle about 2 months ago

  • Release Notes changed from Default to Force Exclusion

Not a problem in a release.

Actions

Also available in: Atom PDF