Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Ntop is NOT gone! (pfsense 1.2.* instruction for installation)

    Scheduled Pinned Locked Moved pfSense Packages
    23 Posts 12 Posters 25.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Soyokaze
      last edited by

      looks like we're forced to integrate ntop to pfsense manually.
      I've got one or two installations with working ntop, so in couple of days I'll upload xml and other needed files.
      Any help will be appreciated.

      Need full pfSense in a cloud? PM for details!

      1 Reply Last reply Reply Quote 0
      • S
        Soyokaze
        last edited by

        Moved to 1st post: http://forum.pfsense.org/index.php/topic,11937.msg65271.html#msg65271

        Need full pfSense in a cloud? PM for details!

        1 Reply Last reply Reply Quote 0
        • P
          phenam
          last edited by

          Great work Pan_2!   ;D

          Thought Id give it a go myself to test.  I followed your instructions but when I get to the part to check for ntop in packages, I receive this error "Unable to retrieve package info from 127.0.0.1. Cached data will be used."

          At first I thought I might be my squid/squid guard.  So I try to stop the service completely to see if this resolves the issue, but alas I still get the same error.

          I have searched through the forum for this exact thing, which gave me a couple of threads relating to this topic which dvserg has worked on.  I followed the several hints from those threads but I seem to be stuck as to what else to try.  I checked and rechecked that all the three files and code are in the right places too.

          Anything else anyone can suggest? thanks.

          Edit:  I just wanted to add that for some reason the pfsense box is unable to resolve the 127.0.0.1 address.  Although I cant think of the reason why this is so.  Which would explain my error above.  I am able to ping 127.0.0.1 from the shell.  Very odd indeed.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            From the CVS logs:

            reason for ntop package removal:
            
            * librrd_th.so.2 not being installed
            * package conflicts with base rrd package version (previous version)
            
            

            And it doesn't work right on FreeBSD regardless, due to threading bugs it'll chew up 100% CPU pretty routinely.

            1 Reply Last reply Reply Quote 0
            • D
              docwho76
              last edited by

              Is this a problem with the current version of the FreeBSD ntop port, or just the version of ntop that pfSense was using?

              1 Reply Last reply Reply Quote 0
              • S
                Soyokaze
                last edited by

                @phenam:

                Great work Pan_2!   ;D

                Thought Id give it a go myself to test.  I followed your instructions but when I get to the part to check for ntop in packages, I receive this error "Unable to retrieve package info from 127.0.0.1. Cached data will be used."

                At first I thought I might be my squid/squid guard.  So I try to stop the service completely to see if this resolves the issue, but alas I still get the same error.

                I have searched through the forum for this exact thing, which gave me a couple of threads relating to this topic which dvserg has worked on.  I followed the several hints from those threads but I seem to be stuck as to what else to try.  I checked and rechecked that all the three files and code are in the right places too.

                Anything else anyone can suggest? thanks.

                Edit:  I just wanted to add that for some reason the pfsense box is unable to resolve the 127.0.0.1 address.  Although I cant think of the reason why this is so.  Which would explain my error above.  I am able to ping 127.0.0.1 from the shell.  Very odd indeed.

                This goes then you don't change to local package info in right order in AltPkg or local package list is not written succesfully.
                try to go to http://yourpfsense/packages/pkg_config.xml , if it shows up - just try to reboot, change to default package source - save - change to local. should work someway.
                Also, try to do this on clean install (in virtual machine for example), at least you will be sure you are doing all right.

                @cmb:

                From the CVS logs:

                reason for ntop package removal:
                
                * librrd_th.so.2 not being installed
                * package conflicts with base rrd package version (previous version)
                
                

                And it doesn't work right on FreeBSD regardless, due to threading bugs it'll chew up 100% CPU pretty routinely.

                well, works fine in at least 4 installations. magic, I suppose =)

                Need full pfSense in a cloud? PM for details!

                1 Reply Last reply Reply Quote 0
                • S
                  Soyokaze
                  last edited by

                  @phenam:

                  Unable to retrieve package info from 127.0.0.1

                  last note - pfsense is very "picky" about pkg_config.xml, maybe you just try copy it again.
                  or save through "edit file" menu

                  Need full pfSense in a cloud? PM for details!

                  1 Reply Last reply Reply Quote 0
                  • P
                    phenam
                    last edited by

                    @pan_2:

                    @phenam:

                    Unable to retrieve package info from 127.0.0.1

                    last note - pfsense is very "picky" about pkg_config.xml, maybe you just try copy it again.
                    or save through "edit file" menu

                    I tried your suggestions on my own before I posted the problem on here but no matter what I do I got the same result.  Going to http://yourpfsense/packages/pkg_config.xml works as expected.

                    I stopped trying to get ntop to work since we were advised with the issues it currently has.  Id rather not risk using it, but thanks for all your effort to get it working =)

                    1 Reply Last reply Reply Quote 0
                    • T
                      techatdd
                      last edited by

                      @phenam:

                      Great work Pan_2!   ;D

                      Thought Id give it a go myself to test.  I followed your instructions but when I get to the part to check for ntop in packages, I receive this error "Unable to retrieve package info from 127.0.0.1. Cached data will be used."

                      At first I thought I might be my squid/squid guard.  So I try to stop the service completely to see if this resolves the issue, but alas I still get the same error.

                      I have searched through the forum for this exact thing, which gave me a couple of threads relating to this topic which dvserg has worked on.  I followed the several hints from those threads but I seem to be stuck as to what else to try.  I checked and rechecked that all the three files and code are in the right places too.

                      Anything else anyone can suggest? thanks.

                      Edit:  I just wanted to add that for some reason the pfsense box is unable to resolve the 127.0.0.1 address.  Although I cant think of the reason why this is so.  Which would explain my error above.  I am able to ping 127.0.0.1 from the shell.  Very odd indeed.

                      For me it worked as expected after changing GUI protocol to http and port to 80. But it added an entry to globals.inc ($g["xmlrpcbaseurl"]= "www.pfsense.com"; ) preventing GUI from working anymore. But after removing this with vi all works, and I have ntop again.

                      1 Reply Last reply Reply Quote 0
                      • T
                        tempress
                        last edited by

                        Does not work on 1.2.1 due to missing libraries (freebsd noob here).

                        1 Reply Last reply Reply Quote 0
                        • D
                          devnull
                          last edited by

                          Hey,

                          too bad about ntop. I needed it and could not find it and thought I was going crazy.
                          So I found this string but can't seem to get ntop working.
                          I keep getting the same error "Unable to retrieve package info from 127.0.0.1. Cached data will be used."

                          My version is 1.2-RC4 (Tue Jan 15 23:05:07 EST 2008)

                          Hope ntop gets working again sure could use it. :-(

                          Bye

                          1 Reply Last reply Reply Quote 0
                          • D
                            devnull
                            last edited by

                            Hi,

                            I've just tried again on a completely different PFS and got the same error about Local cache could not be retrieved. I did everything like as instructed accept for the uploading of the two files witch I did via scp but I checked everything and it shouldn't make a difference. But I still keep getting the same error. Is there something else that I should try when I switch to local a reboot or something else to get ntop going?

                            Thanks for the help and bye

                            1 Reply Last reply Reply Quote 0
                            • D
                              devnull
                              last edited by

                              Hi,

                              I finally figured out why I was not able to add the package.
                              I'm running a transparent proxy and so I had to move the web interface to a different port (81).
                              So I disabled the proxy and changed back the administration to non secure port 80 and it seems to work like a charm.

                              Hop this helps someone.

                              Best regards and bye

                              1 Reply Last reply Reply Quote 0
                              • R
                                Rossonero224
                                last edited by

                                It's wonderful. Thanks you so much. I installed ntop successfully. :D

                                1 Reply Last reply Reply Quote 0
                                • J
                                  John A
                                  last edited by

                                  Thank you pan_2. ntop installed and running.

                                  1 Reply Last reply Reply Quote 0
                                  • ?
                                    Guest
                                    last edited by

                                    ntop is in the 1.2.2 package list and beyond so this thread is now moot.  Do not follow these instructions with 1.2.2 and beyond or you will absolutely, positively break something.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.