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

    Strikeback with iplog and nmap

    Scheduled Pinned Locked Moved pfSense Packages
    53 Posts 24 Posters 49.6k 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
      seattle-it
      last edited by

      @tommyboy180:

      All those things should be done automatically.

      During the install process pkg_add -r iplog is ran. The username is also changed to root (you can also do this via the GUI).
      The only thing that I can think of is that when the pkg_add command is ran the command doesn't install iplog due to the freeBSD repo not being contacted or the connection being interrupted.

      I will be able to look into this more tomorrow.

      Also I had to manually add nmap .. it didn't pull it in for whatever reason

      My tech blog - seattleit.net/blog

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

        That means the FreeBSD repo is un-reliable. I'll look into other options.

        -Tom Schaefer
        SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

        Please support pfBlocker | File Browser | Strikeback

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

          I finished my testing. The package is working correctly.

          First thing new users should do it go to the setting page and click save. This will overwrite the config file.
          Next go back to the main strikeback page, Check enable, and click save. I tested on the latest version of RC3.

          I didn't run into any issue while testing.

          -Tom Schaefer
          SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

          Please support pfBlocker | File Browser | Strikeback

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

            not to hijack this thread, but I remember testing this package a couple of months ago and remember that iplog wouldn't auto-start on a reboot… Was this fix or is it still the case?

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

              @Cino:

              not to hijack this thread, but I remember testing this package a couple of months ago and remember that iplog wouldn't auto-start on a reboot… Was this fix or is it still the case?

              You're not hijacking at all. You are right about the auto start. That item is now on my to-do list.

              -Tom Schaefer
              SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

              Please support pfBlocker | File Browser | Strikeback

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

                @tommyboy180:

                @Cino:

                not to hijack this thread, but I remember testing this package a couple of months ago and remember that iplog wouldn't auto-start on a reboot… Was this fix or is it still the case?

                You're not hijacking at all. You are right about the auto start. That item is now on my to-do list.

                looking at my notes, i used this to auto start it i believe /usr/local/etc/rc.d/iplog.sh
                its been awhile so I can't remember it worked correctly work not…

                
                #!/bin/sh
                # This file was automatically generated
                # by the pfSense service handler on other machine :).
                
                rc_start() {
                	/usr/local/sbin/iplog -d -z
                }
                
                rc_stop() {
                	/usr/bin/killall iplog
                }
                
                case $1 in
                	start)
                		rc_start
                		;;
                	stop)
                		rc_stop
                		;;
                	restart)
                		rc_stop
                		rc_start
                		;;
                esac
                
                
                1 Reply Last reply Reply Quote 0
                • T
                  tommyboy180
                  last edited by

                  overwriting the current iplog file in /usr/local/etc/rc.d/iplog will break the script. I'm working on an update now to solve this issue.

                  -Tom Schaefer
                  SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

                  Please support pfBlocker | File Browser | Strikeback

                  1 Reply Last reply Reply Quote 0
                  • W
                    WetWilly
                    last edited by

                    I like this. Thanks for releasing!

                    Just a small bug report, there is a typo "Stikeback" under the Services tab.

                    1 Reply Last reply Reply Quote 0
                    • N
                      Nachtfalke
                      last edited by

                      Is this package available for amd64 ?
                      Where can I download/test this package ?

                      1 Reply Last reply Reply Quote 0
                      • A
                        ataru75
                        last edited by

                        Hi, i try this package and when i execute strikeback i get this message

                        Warning: Invalid argument supplied for foreach() in /usr/local/www/packages/strikeback/parse.php on line 252
                        Nmap scan results (condensed)

                        in the system log i have this

                        php: /packages/strikeback/strikeback.php: The command 'mkdir /usr/local/www/packages/strikeback/reports' returned exit code '1', the output was 'mkdir: /usr/local/www/packages/strikeback/reports: File exists'

                        php: /packages/strikeback/strikeback.php: The command 'mkdir /var/run/iplog' returned exit code '1', the output was 'mkdir: /var/run/iplog: File exists'

                        can you help me?
                        thanks
                        Simone

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

                          @ataru75:

                          Hi, i try this package and when i execute strikeback i get this message

                          Warning: Invalid argument supplied for foreach() in /usr/local/www/packages/strikeback/parse.php on line 252
                          Nmap scan results (condensed)

                          in the system log i have this

                          php: /packages/strikeback/strikeback.php: The command 'mkdir /usr/local/www/packages/strikeback/reports' returned exit code '1', the output was 'mkdir: /usr/local/www/packages/strikeback/reports: File exists'

                          php: /packages/strikeback/strikeback.php: The command 'mkdir /var/run/iplog' returned exit code '1', the output was 'mkdir: /var/run/iplog: File exists'

                          Confirmed - Pfsense i386, 2.0-RC3

                          1 Reply Last reply Reply Quote 0
                          • H
                            hubsd
                            last edited by

                            just installed this on 2.0 final

                            not working, I think iplog is missing

                            Nov 1 13:58:08 php: /packages/strikeback/strikeback.php: The command '/usr/local/etc/rc.d/iplog start' returned exit code '127', the output was '/usr/local/etc/rc.d/iplog: not found'
                            Nov 1 13:58:08 php: /packages/strikeback/strikeback.php: The command 'rm /usr/local/etc/rc.d/iplog-e' returned exit code '1', the output was 'rm: /usr/local/etc/rc.d/iplog-e: No such file or directory'
                            Nov 1 13:58:08 php: /packages/strikeback/strikeback.php: The command '/usr/bin/sed -i -e 's/iplog_enable="NO"/iplog_enable="YES"/g' /usr/local/etc/rc.d/iplog' returned exit code '1', the output was 'sed: /usr/local/etc/rc.d/iplog: No such file or directory'

                            also tryed pkg_add -r iplog

                            Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/iplog.tbz: File unavailable (e.g., file not found, no access)

                            < typo forum, it add http:// but for real it doesnt …

                            packages-8.1-release doesnt exist anymore

                            1 Reply Last reply Reply Quote 0
                            • johnpozJ
                              johnpoz LAYER 8 Global Moderator
                              last edited by

                              you can find 8-1 packages here

                              ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/8.1-RELEASE/packages/All/

                              An intelligent man is sometimes forced to be drunk to spend time with his fools
                              If you get confused: Listen to the Music Play
                              Please don't Chat/PM me for help, unless mod related
                              SG-4860 24.11 | Lab VMs 2.8, 24.11

                              1 Reply Last reply Reply Quote 0
                              • K
                                kevross33
                                last edited by

                                So if I spoofed my IP address during scanning to say be some military or government IP I can have you port scanning away in "response"? I am sure they would like that. Portscan detections are also notoriously unreliable as they are prone to false positive events.

                                I think detection is fine and then silently blocking if so desired but no revenge strikes. What would you do after port scanning someone? Go hunting for vulnerabilities to take your revenge on them? I think snort's sfportscan preprocessor may be better for detection. All it does it:
                                a) leaves you open to manipulation to portscan sensitive places in response
                                b) reveals yourself to the attacker (unlike a nice silent drop)
                                c) If it was a hacker (script kiddies get detected would perhaps be caught by this, pros no) and they saw you portscanning them they may be encouraged to seek revenge.

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

                                  I'm away on business right now. When I return I will take some time to update the package.

                                  -Tom Schaefer
                                  SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

                                  Please support pfBlocker | File Browser | Strikeback

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    jhaye
                                    last edited by

                                    Hi There,

                                    I have a kind of similar issue. I'm running the latest PFsense 2.0 official release on an ALIX board. I have succesfully intalled STRIKEBACK package. As recommended, I went to Strikeback SETTINGS tab and clicked on SAVE, resulting in an updated /usr/local/etc/iplog.conf file. Then I go to LOG VIEWER tab and enable StrikeBack then click on SAVE. The System Logs reveal the following:
                                    Nov 15 10:35:13 php: /packages/strikeback/strikeback.php: The command '/usr/bin/sed -i -e 's/iplog_enable="NO"/iplog_enable="YES"/g' /usr/local/etc/rc.d/iplog' returned exit code '1', the output was 'sed: /usr/local/etc/rc.d/iplog: No such file or directory'
                                    Nov 15 10:35:13 php: /packages/strikeback/strikeback.php: The command 'rm /usr/local/etc/rc.d/iplog-e' returned exit code '1', the output was 'rm: /usr/local/etc/rc.d/iplog-e: No such file or directory'
                                    Nov 15 10:35:13 php: /packages/strikeback/strikeback.php: The command '/usr/local/etc/rc.d/iplog start' returned exit code '127', the output was '/usr/local/etc/rc.d/iplog: not found'

                                    I'm stuck in figuring out how to even figure out weither or not iplog is indeed installed  ???

                                    Any help greatly appreciated. Thanks in advance  :)

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

                                      @jhaye:

                                      Hi There,

                                      I have a kind of similar issue. I'm running the latest PFsense 2.0 official release on an ALIX board. I have succesfully intalled STRIKEBACK package. As recommended, I went to Strikeback SETTINGS tab and clicked on SAVE, resulting in an updated /usr/local/etc/iplog.conf file. Then I go to LOG VIEWER tab and enable StrikeBack then click on SAVE. The System Logs reveal the following:
                                      Nov 15 10:35:13 php: /packages/strikeback/strikeback.php: The command '/usr/bin/sed -i -e 's/iplog_enable="NO"/iplog_enable="YES"/g' /usr/local/etc/rc.d/iplog' returned exit code '1', the output was 'sed: /usr/local/etc/rc.d/iplog: No such file or directory'
                                      Nov 15 10:35:13 php: /packages/strikeback/strikeback.php: The command 'rm /usr/local/etc/rc.d/iplog-e' returned exit code '1', the output was 'rm: /usr/local/etc/rc.d/iplog-e: No such file or directory'
                                      Nov 15 10:35:13 php: /packages/strikeback/strikeback.php: The command '/usr/local/etc/rc.d/iplog start' returned exit code '127', the output was '/usr/local/etc/rc.d/iplog: not found'

                                      I'm stuck in figuring out how to even figure out weither or not iplog is indeed installed  ???

                                      Any help greatly appreciated. Thanks in advance  :)

                                      It appears if the iplog binary did not get installed. Run pkg_add -r iplog to install it.

                                      -Tom Schaefer
                                      SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

                                      Please support pfBlocker | File Browser | Strikeback

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        jhaye
                                        last edited by

                                        Tom, many thanks for the very fast reply. Unfortunately, I did try this last trick already, as I had read through the forum. This results in the following error message:

                                        Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/iplog.tbz: File unavailable (e.g., file not found, no access)
                                        pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/iplog.tbz' by URL

                                        :-(

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

                                          You have to change an environment variable to use pkg_add -r or you can add it directly via URL.

                                          Try```
                                          pkg_add -r ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/iplog.tbz

                                          -Tom Schaefer
                                          SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

                                          Please support pfBlocker | File Browser | Strikeback

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

                                            Does nmap have some sort of conf file that tells it what interface to use. I can scan the local network from within pfsense nmap ui.

                                            Nov 16 09:58:59 	php: /packages/strikeback/strikeback.php: The command '/usr/local/bin/nmap -oX /usr/local/www/packages/strikeback/reports/58.104.179.126.xml -vv -sS -sU -sY -O 58.104.179.126' returned exit code '1', the output was ' Starting Nmap 5.51 ( http://nmap.org ) at 2011-11-16 09:58 EST WARNING: Unable to find appropriate interface for system route to 10.20.21.36 WARNING: Unable to find appropriate interface for system route to 10.20.21.36 WARNING: Unable to find appropriate interface for system route to 10.20.21.36 nexthost: failed to determine route to 58.104.179.126 QUITTING!'
                                            Nov 16 09:58:59 	php: /packages/strikeback/strikeback.php: The command 'mkdir /usr/local/www/packages/strikeback/reports' returned exit code '1', the output was 'mkdir: /usr/local/www/packages/strikeback/reports: File exists'
                                            

                                            And get this same error from Nmap within the shell

                                            [2.0-RELEASE][root@pfsense.domain.local]/root(2): nmap -v -sn 58.104.179.126
                                            
                                            Starting Nmap 5.51 ( http://nmap.org ) at 2011-11-16 10:19 EST
                                            WARNING: Unable to find appropriate interface for system route to 10.20.21.36
                                            
                                            

                                            I tried adding the -e switch with the wan interface but I still am getting the same error.

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