ntopng gone from packages?

[lohphat]

Upgrading from 25.11.1 to 26.03 removed it.

Then this page said how to add it back. https://www.ntop.org/guides/ntopng/third_party_integrations/pfsense.html

It didn't work.

pkg install ntopng redis
Updating ntop repository catalogue...
pkg: Failed to fetch https://packages.ntop.org/FreeBSD/FreeBSD:16:armv7/latest/meta.conf: Failed writing received data to disk/application
pkg: Failed to fetch https://packages.ntop.org/FreeBSD/FreeBSD:16:armv7/latest/meta.txz: Failed writing received data to disk/application
repository ntop has no meta file, using default settings
pkg: Failed to fetch https://packages.ntop.org/FreeBSD/FreeBSD:16:armv7/latest/data.pkg: Failed writing received data to disk/application
pkg: Failed to fetch https://packages.ntop.org/FreeBSD/FreeBSD:16:armv7/latest/data.tzst: Failed writing received data to disk/application
pkg: Failed to fetch https://packages.ntop.org/FreeBSD/FreeBSD:16:armv7/latest/packagesite.pkg: Failed writing received data to disk/application
pkg: Failed to fetch https://packages.ntop.org/FreeBSD/FreeBSD:16:armv7/latest/packagesite.tzst: Failed writing received data to disk/application
Unable to update repository ntop
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
Error updating repositories!
pkg: Repository ntop cannot be opened. 'pkg update' required
pkg: No packages available to install matching 'ntopng' have been found in the repositories
pkg: No packages available to install matching 'redis' have been found in the repositories
[26.03-RELEASE][root@pfSense.localdomain]/usr/local/etc/pkg:

[patient0]

@lohphat in general ntopng is available in pfSense BUT your SG-3100 is a 32-bit ARM platform which is end of life and I think for a time it thought that it won't get 26.03. But obviously it got the OS update in the end

But some of the bigger packages are not available anymore for the 32-bit ARM platform because it's impossible to build them for that platform. ntopng seems to be one of them.

The installation instruction from ntop.org is not for the community edition but the Pro/Enterprise one. If you go to the repository link https://packages.ntop.org/FreeBSD/ you'll see that it seems only x86_64/amd64 packages are available.

Your best bet is to go back to 25.11.1 and look for a replacement device.

Maybe @stephenw10 can provide a link to the EOL information regarding SG-3100, I couldn't find it in the release notes. Or you open a TAC support ticket for it, https://www.netgate.com/tac-support-request.

Addition:

Ok, searching for '3100' in this forum brought up https://forum.netgate.com/post/1240123 and in it the following EOL information about the SG-3100:

https://docs.netgate.com/pfsense/en/latest/releases/24-03.html#netgate-3100-32-bit-arm-limitations

It would be helpful if Netgate provided the new limitations in the release notes.

[lohphat]

@patient0 I know it's out of support but they continue to be really vague about it.

If I have to upgrade, I might as well get a PA-415 from Palo Alto Networks.

[patient0]

@lohphat said in ntopng gone from packages?:

If I have to upgrade, I might as well get a PA-415 from Palo Alto Networks

You do that, it sound like Palo Alto are a bit pricy though.

[SteveITS]

@lohphat said in ntopng gone from packages?:

they continue to be really vague about it

Tbf I don't think they are trying to be vague. From a few other posts here by Netgate staff my understanding is they fully expected to not be able to deliver any more pfSense builds because of FreeBSD dropping support for 32 bit. However it sounds like they and/or someone has been updating FreeBSD anyway, so they have been able to carry pfSense forward for several years past expectation. However if third party package maintainers don't write compatible code then the package will no longer build/run on 32 bit, and there's not much they can do about that. Many/most/all of the packages on pfSense are binary files pulled in from FreeBSD, with some PHP scripts to handle the integration with pfSense. Ergo, the last couple years have been a bonus.

[lohphat]

@patient0 We use PANs at work so it gives me an opportunity to learn features.

[lohphat]

@SteveITS Then publish a date of NO NEW RELEASES and be done with it.

All other OEMs do that, publish and end of sale, end of support, end of patches/updates.

It's not that hard.

Without clear declarations, it's by definition, vague.

[dennypage]

FWIW, I would not have recommended running ntopng on small systems. ntopng consumes a tremendous amount of resources. I generally recommend using it for diagnostic purposes, rather than continual operation.

[lohphat]

@dennypage Which is why I had it installed and disabled for use only when needed.

[SteveITS]

@lohphat Netgate has always announced an end of sale and end of life date, and actually emailed registered purchasers about the 3100 (the "EOL in 5 days" email). However they have also provided pfSense for all models "until they can't anymore" due to insufficient RAM or other incompatibilities. It sounds like it is more of a "best effort" vs "guaranteed to work." Given we all had "5 days" notice I would consider multiple years' time as a bonus.

Perhaps what they need to do, if the package list is still dwindling, is to add a note on the 3100's package pages to explain why, if it's not in the release notes. Based on a prior discussion I once had, 3100 support is not mentioned in the current release notes because it is not a new issue/change, and (my interpretation) they assume one has read all previous notes.