Skip to content

Conversation

@BPplays
Copy link
Contributor

@BPplays BPplays commented Dec 7, 2025

  • add the option to configure what addresses to listen on
  • add automatic configuration from the Redis plugin for Redis password and port
  • add an option to override the Redis server to use
  • ntopng seems to have a limit of only 1 listen address on HTTPS; that is checked in performValidation
  • add a limit to Redis not allowing \ or ` for ntopng see the --redis option here (i feel like the simpler option is to disallow a Redis password that is invalid for ntopng but i could remove that check and add a warning to ntopng)
  • update ntopng config when Redis settings are applied (in case the user changed the Redis password or port)

requires opnsense/core#9500

P.S. is there any way to change the permissions of files; both redis.conf and ntopng.conf seem to be readable to all users and contain passwords

@fichtner
Copy link
Member

fichtner commented Dec 8, 2025

To be frank we shouldn't do this. There's IPPortField which can do all of this (optional port) and continuing to drive a wedge between ports and address lists as separate entities in the model increase risks of bugs, misconfiguration and future maintenance.

@BPplays
Copy link
Contributor Author

BPplays commented Dec 14, 2025

@fichtner i changed to using IPPortField but i believe this means i should also make a migration to copy over the old httpport and httpsport but im having trouble figuring out how to set the new values it just says the migration failed because of a validation error (a cert is selected but no addresseshttps value), i've also tried without changes addresseshttps just addresseshttp then nothing happens it just silently gets set to default.

i also can't figure out a way to get output from a migration, writing to the console doesn't seem to work and writing to a file seems to also do nothing and the error im getting from /usr/local/opnsense/mvc/script/run_migrations.php also isn't descriptive at all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants