January 3, 2018 at 8:43 pm #44916
I keep my system up to date, so I am running ZS 3.8.2 with the 64-bit kernel. The only package I have installed is Nmap.
I have not used nDPI before, and want to explore it. When I go to the firewall and add a new rule and click on nDPI Manager, another window pops up. It has sections for “Available Protocols” and “Selected Protocols”, but both lists are empty.
Is there something else I have to install to get the protocols to show up?
Thanks in advance for your help.January 30, 2018 at 11:15 am #54661itanveerParticipant
I have also the same problem, after installing 4.4.96-ZS-64, the list of available protocols in nDPI manager is gone, however it was visible with kernel 4.4.95-ZS
Is there a way to get back the list or shall we step down our kernel?
Malik IlyasJanuary 30, 2018 at 12:15 pm #54662akhtarchMember
Facing the same problem 🙁
Downgraded the kernel for the time but want to use 64-bit kernel 4.4.96-ZS-64
because we are using 64Bit hardware.
Thank you in advance,
Akhtar Ali JavedJune 19, 2018 at 8:30 pm #64133
I still don’t have a solution to this problem. I took a loot at the Deep Packet Inspection post on the right side of this website and found a command to try:
iptables -mndpi –help
It returns the error:
iptables v1.4.21: xt_ndpi: kernel module not load.
Try `iptables -h’ or ‘iptables –help’ for more information.
Does that help identify the problem?February 25, 2020 at 1:50 pm #65836infiernoParticipantFebruary 25, 2020 at 10:16 pm #65842
I recently had a hardware failure and ended up reinstalling the current version (ZS 3.9.3 with 64-bit kernel 4.14.83). Even though I restored the configuration from a backup, the nDPI tables were now present. So, I think the original problem must have been due to some historical upgrade that messed it up.
If you need this functionality, I would backup your running configuration, reinstall ZS and restore the configuration. That should make it work.February 25, 2020 at 10:25 pm #65843
That’s funny. Forget everything I just said. It turns out I was accidentally running the 32-bit version and that’s why it’s working. So, reinstalling probably won’t help you. Just boot the 32-bit kernel instead.
- You must be logged in to reply to this topic.