Project

General

Profile

Actions
Copy link

Bug #15957

closed

NTOPNG generates duplicate variable in CONF file when using advanced configuration lines on pfsense+

Added by Benjamin Coussement 4 months ago. Updated 4 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
ntop
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
24.11
Affected Architecture:
7100

Description

Environment:

OS name: pfSense+
OS version: 24.11-RELEASE (FreeBSD 15.0-CURRENT)
Architecture: amd64
ntopng version/revision: 5.6.0_1
What happened:
When adding different ports under the advanced configuration like these:
--http-port=3000
--https-port=3001
It fails to start the service because now in the config file it has the following:
  1. This file is automatically generated -- do not edit
    --daemon=
    --pid=/var/run/ntopng.pid
    --data-dir=/var/db/ntopng/
    --no-promisc=
    --http-port=0
    --https-port=0.0.0.0:3000,[::]:3000
    --interface=lagg0.100
    --interface=lagg0.110
    --interface=lagg0.120
    --interface=lagg0.130
    --interface=lagg0.140
    --interface=lagg0.150
    --interface=lagg0.160
    --interface=tun_wg0
    --dns-mode=0
  2. Custom configuration options:
    --http-port=3000
    --https-port=3001
    This means I need to remove the 2 lines it automatically generated (http-port and https-port) and manually start the service via the pfsense WebUI.

How did you reproduce it?
You just need to create a small change via the WebUI of pfsense+ in the NTOPNG settings page and then you will find yourself the need for manually having to change the ntopng.conf file and manually having to start the service from the pfsense+ WebUI

Debug Information:
N/A
Platform: Netgate 7100 1U

Actions
Copy link

Also available in: Atom PDF