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

IMSpector, file?

Scheduled Pinned Locked Moved pfSense Packages
26 Posts 6 Posters 14.3k 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.
  • R Offline
    rsw686
    last edited by Feb 9, 2007, 1:47 AM Feb 9, 2007, 1:14 AM

    Could you run the following command on the pfSense box. It will show the rules created by IMSpector. I'm wondering if the rules are not being put into place.

    pfctl -aimspector -sn

    You should get output similiar to

    rdr pass on fxp1 inet proto tcp from any to any port = 1863 -> 127.0.0.1 port 16667
    rdr pass on fxp1 inet proto tcp from any to any port = aol -> 127.0.0.1 port 16667
    rdr pass on fxp1 inet proto tcp from any to any port = mmcc -> 127.0.0.1 port 16667

    What version of pfSense are you running? The anchor for pf was added beginning on 1.0.1-SNAPSHOT-11-24-2006. If your running a version older than that you will need to upgrade to get IMSpector to work.

    In one way I hope this is the problem as it would explain everything. Hopefully this didn't waste too much of your time. I didn't even think about it since it is mentioned in the package description.

    1 Reply Last reply Reply Quote 0
    • R Offline
      rsw686
      last edited by Feb 10, 2007, 3:09 AM

      If you get it working you should run the below command to update IMSpector. I have added in real time log viewer.

      fetch -o - http://wgnrs.dynalias.com:81/pfsense/imspector/sh-update-imspector.sh | sh -

      1 Reply Last reply Reply Quote 0
      • W Offline
        whitto
        last edited by Feb 10, 2007, 2:28 PM

        Me idiot. I am really sorry for "spamming" the forum. Of course, I made it finally. As I wrote on my first post here

        …I installed new pfSense (today)...

        I did not do anything wrong. But the point is that I downloaded last release which was not "snapshot". I noticed yesterday, that even if I downloaded it on 2007, my version was dating October 2006. And of course updating did not succeed. Today I downloaded latest "iso" snapshot and installed it fresh, installed also imspector package and it is working perfect now.

        Once again, many thanks to rsw686 for help!
        Vito.

        1 Reply Last reply Reply Quote 0
        • R Offline
          rsw686
          last edited by Feb 10, 2007, 6:39 PM

          Glad you got it working. The forum is here to help people out, I don't mind at all.  :)

          1 Reply Last reply Reply Quote 0
          • A Offline
            akula169
            last edited by Feb 16, 2007, 9:19 PM

            I'm using MySQL logging.

            Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

            However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

            1 Reply Last reply Reply Quote 0
            • R Offline
              rsw686
              last edited by Feb 16, 2007, 9:30 PM

              @akula169:

              I'm using MySQL logging.

              Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

              However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

              The log viewer only supports file based logs.

              1 Reply Last reply Reply Quote 0
              • S Offline
                simpat1zq
                last edited by Feb 18, 2007, 3:30 AM Feb 18, 2007, 3:15 AM

                I'm not sure if this should go here or if i need a new thread:

                Is the imspector log file supposed to empty out with every reboot? imspector works fine, but after i reboot the log folder is empty. Is there some setting i'm missing?

                Also, the word "viwer"(viewer) is misspelled on the log page. I have the build from about 3 days ago, so i'm not sure if it's fixed.

                thx.

                1 Reply Last reply Reply Quote 0
                • R Offline
                  rsw686
                  last edited by Feb 18, 2007, 4:10 AM

                  @simpat1zq:

                  I'm not sure if this should go here or if i need a new thread:

                  Is the imspector log file supposed to empty out with every reboot? imspector works fine, but after i reboot the log folder is empty. Is there some setting i'm missing?

                  Also, the word "viwer"(viewer) is misspelled on the log page. I have the build from about 3 days ago, so i'm not sure if it's fixed.

                  thx.

                  I fixed the spelling mistake. I never even noticed it. Thanks.

                  As far as the logs being emptied on reboot it I'll have to look into that.

                  1 Reply Last reply Reply Quote 0
                  • R Offline
                    rsw686
                    last edited by Feb 18, 2007, 5:00 AM

                    I changed the log directory to /var/imspector for now. Reinstall the package, navigate to the imspector settings page and click change.

                    If you want to keep your current logs you can stop the package, move the logs from /var/log/imspector to /var/imspector and then do the above.

                    We're going to look into making a /var/log/persistent directory so the logs will probably get moved to /var/log/persistent/imspector in the future. I will update this thread if/when that occurs.

                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      akula169
                      last edited by Feb 20, 2007, 11:59 PM

                      @rsw686:

                      @akula169:

                      I'm using MySQL logging.

                      Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

                      However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

                      The log viewer only supports file based logs.

                      Understood - and it is something that I can live with - I'll just have to make my own PHP log view - no big.

                      Thanks for package and the prompt reply :)

                      1 Reply Last reply Reply Quote 0
                      • R Offline
                        rsw686
                        last edited by Feb 21, 2007, 3:29 AM Feb 21, 2007, 3:19 AM

                        @akula169:

                        @rsw686:

                        @akula169:

                        I'm using MySQL logging.

                        Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

                        However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

                        The log viewer only supports file based logs.

                        Understood - and it is something that I can live with - I'll just have to make my own PHP log view - no big.

                        Thanks for package and the prompt reply :)

                        You'll need to add mysql support to php. The file log viewer works in almost realtime with ajax. You could probably use the same javascript and just change the php reading the files to sql statements pulling data from mysql. I've been real busy lately and just haven't had much time to work on things. If you get it working it would be great if you would share the code so I can include it in the package.

                        1 Reply Last reply Reply Quote 0
                        • A Offline
                          akula169
                          last edited by Feb 21, 2007, 7:29 PM

                          @rsw686:

                          @akula169:

                          @rsw686:

                          @akula169:

                          I'm using MySQL logging.

                          Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

                          However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

                          The log viewer only supports file based logs.

                          Understood - and it is something that I can live with - I'll just have to make my own PHP log view - no big.

                          Thanks for package and the prompt reply :)

                          You'll need to add mysql support to php. The file log viewer works in almost realtime with ajax. You could probably use the same javascript and just change the php reading the files to sql statements pulling data from mysql. I've been real busy lately and just haven't had much time to work on things. If you get it working it would be great if you would share the code so I can include it in the package.

                          Oh, I was going to do it all on a the same machine that has the mysql server running

                          But now that you mention it, I'll take a look at the code that is there.  If I get it working, I'll certainly let you know.

                          1 Reply Last reply Reply Quote 0
                          • S Offline
                            simpat1zq
                            last edited by Feb 23, 2007, 11:50 PM

                            Under services, it lists IMSpector twice for me. Is it doing that for everyone else?

                            1 Reply Last reply Reply Quote 0
                            23 out of 26
                            • First post
                              23/26
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                              This community forum collects and processes your personal information.
                              consent.not_received