Project

General

Profile

Actions
Copy link

Bug #6588

closed

PHP suhosin max value length prevents Quagga OSPF from storing a very large zebra.conf

Added by Fisher Wei almost 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jim Thompson
Category:
Web Interface
Target version:
-
Start date:
07/07/2016
Due date:
% Done:

0%

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

Description

pfsense 2.3.1-RELEASE-p5 (amd64)
Quagga_OSPF net 0.6.14

I tried to add some static routes in Services>Quagga OSPFd>Raw Config>zebra.conf.
8000 entries is OK.

But 30000 entries will FAIL, I pasted routes(content size about 900kb), and save, the page will refresh and return a blank zebra.conf.

BTW: Maybe someone want to know why I need 30000+ static routes?
Because, in China, the National Firewall blocked so many ip addresses, so we have to build a VPN gateway, and maintain a huge blacklist for keeping internet accessible.

Actions
Copy link
 #1

Updated by Chris Buechler almost 8 years ago

  • Affected Version changed from 2.3.1 to All
  • Affected Architecture All added
  • Affected Architecture deleted (amd64)
Actions
Copy link
 #2

Updated by Jim Thompson over 7 years ago

  • Assignee set to Jim Pingle

Yet another Chris left so the bug went into an unassigned state.

JimP please verify, and assign back to me if we can recreate this.
(or fix it if it's a simple fix)

Actions
Copy link
 #3

Updated by Jim Pingle over 7 years ago

  • Project changed from pfSense Packages to pfSense
  • Subject changed from Quagga OSPF zebra.conf max limit to PHP suhosin max value length prevents Quagga OSPF from storing a very large zebra.conf
  • Category changed from Quagga OSPF to Web Interface
  • Assignee changed from Jim Pingle to Jim Thompson

Attempting to store that large of value hits a suhosin variable limit. I updated the description of the ticket to match what's actually happening:

suhosin.post.max_value_length = 500000

I generated a huge list of static routes and copied and pasted chunks in and confirmed it dies around when it would hit that total limit in bytes of the field when submitted.

That's already a fairly large limit for one variable and I'm not sure we want to encourage storing such large amounts of raw entry in the config.

If we do want to change it, it's an easy change where we setup the limits in PHP:

source:src/etc/rc.php_ini_setup#L260

We might also have to change the get and request limit to match the post limit if we do change that value.

Actions
Copy link
 #4

Updated by Jim Pingle over 4 years ago

  • Status changed from New to Closed

That limitation shouldn't be present these days (no suhosin on current PHP versions)

Actions
Copy link

Also available in: Atom PDF