• 0 Votes
    5 Posts
    628 Views
    K
    I do have VPN setup on my server and also the client on my phone. I will need to gives this a test. Thanks,
  • 0 Votes
    2 Posts
    3k Views
    P
    Have you tried the service watchdog package? It sounds like it is written to do exactly what you want. EDIT: Maybe not exactly what you want, it doesn't work on a per interface basis. I don't know if it will work for you but it should if your system keeps marking the suricata service as down for some reason.
  • Suricata Pass List using Hostnames?

    3
    0 Votes
    3 Posts
    2k Views
    P
    OK thank you, I figured that would be the answer. I ended up just disabling & modifying some rules so that it's no longer a problem.
  • Snort build options

    2
    0 Votes
    2 Posts
    690 Views
    J
    I didn't know Snort could do this, and after a quick bit of searching I'm not convinced that the current version of Snort can do SNMP. I found some references to pre 2.0 Snort and SNMP, and some references to third party plugins, but nothing in the manual for 2.9.9 mentions sending alert info via SNMP. If your RMM supports Syslog you could use it.
  • Don't Alert any syn-scan!

    2
    0 Votes
    2 Posts
    474 Views
    U
    Did you enable Port scan detection? General preprocessor settings section –> enable 'Portscan Detection'
  • Two or More Snorby Sensors on PFsense

    1
    0 Votes
    1 Posts
    390 Views
    No one has replied
  • Suricata 3.1.3 update

    4
    0 Votes
    4 Posts
    953 Views
    R
    Hello, Suricata 3.2.1 is available on Fresh ports.
  • Suricata 3.2.1 Free-BSD port is available

    1
    0 Votes
    1 Posts
    370 Views
    No one has replied
  • Snort no longer working after 2.3.3 Upgrade

    2
    0 Votes
    2 Posts
    890 Views
    N
    I saw this in the logs after the update: /etc/rc.packages: [Snort] Removing all blocked hosts from <snort2c>table… /etc/rc.packages: [Snort] Removing package files… /etc/rc.packages: [Snort] Not saving settings… all Snort configuration info and logs will be deleted... /etc/rc.packages: [Snort] Flushing <snort2c>firewall table to remove addresses blocked by Snort… /etc/rc.packages: [Snort] The package has been completely removed from this system.</snort2c></snort2c> Snort showed up in Installed packages with "newer version available". Tried to update: Removing snort components… Menu items... done. Services... done. Loading package instructions... pfSense-pkg-snort-3.2.9.1_14: missing file /usr/local/share/licenses/pfSense-pkg-snort-3.2.9.1_14/ESF pfSense-pkg-snort-3.2.9.1_14: missing file /usr/local/share/licenses/pfSense-pkg-snort-3.2.9.1_14/LICENSE pfSense-pkg-snort-3.2.9.1_14: missing file /usr/local/share/licenses/pfSense-pkg-snort-3.2.9.1_14/catalog.mk pkg: Fail to rename /var/db/snort/sidmods/.disablesid-sample.conf.xmxAXuJE48b4 -> /var/db/snort/sidmods/disablesid-sample.conf: No such file or directory Failed Removed package. It threw some errors (attached). Rebooted. Installed snort again without a problem. It now shows up in services and my settings are there too. Have you tried turning it off and on again? [snort package removal error.txt](/public/imported_attachments/1/snort package removal error.txt)
  • Suricata alert.log deleted after 1 day

    3
    0 Votes
    3 Posts
    1k Views
    R
    The only way that I could find to fix this, after serious testing, was to do a full reinstall, and restoring the backup configuration. The topic can be closed.
  • Snort Setup

    2
    0 Votes
    2 Posts
    1k Views
    U
    First thing of rule in security for me is never use someone else rules or whitelist. You as the administrator of your network should know it best and determine what is good and what is not. From your alert ip: 2017-02-23 11:55:30  3  TCP  Unknown Traffic  192.168.0.12     88  192.168.0.10     3871  120:3     (http_inspect) NO CONTENT-LENGTH OR TRANSFER-ENCODING IN HTTP RESPONSE Should .12 accessing .10? Is so then for what reason? Is it device or server compromise? If so did you check logs or do a wireshark capture? Things you need to ask. 2017-02-23 11:52:08  3  TCP  Unknown Traffic  151.101.124.84     80  192.168.0.15     34412  119:31     (http_inspect) UNKNOWN METHOD 151.101.124.84 seems to be pinterest. Is .15 a device that is accessing pinterest at the moment is pinterest block? Content not showing? Most of the time http_inspect are errors with HTTP conversation. But not all the case, sometimes these can be some sort of consolidated attack on your servers or possibly of trying to use them in an attack against another server or servers. In this case most likely not and consider safe if it isn't affecting the website or content I just leave it along. Hope that helps.
  • Suricata Rules download error - pfsense 2.3.3

    Locked
    9
    0 Votes
    9 Posts
    3k Views
    H
    Thank you ;)
  • Latest update to Snort fails in latest Snapshot relesae.

    6
    0 Votes
    6 Posts
    2k Views
    D
    Yeah, remove and reinstall the package.
  • 0 Votes
    3 Posts
    912 Views
    S
    And why on earth is security software still using MD5?! :(
  • Snort VRT Rules fail to download (505 HTTP Version Not Supported)

    3
    0 Votes
    3 Posts
    866 Views
    L
    Thank you. I will try that when I'm back home. Out of the country for the next week.
  • How to make changes to snort.config for variables not in WebGui

    1
    0 Votes
    1 Posts
    485 Views
    No one has replied
  • 0 Votes
    2 Posts
    1k Views
    D
    Have you read the previous ~1356 threads about MD5 checksums mismatch? HTTP 429 - server too busy. Stop hammering it, and wait a day or two before someone bothered to fix the checksums again. Yeah, nothing at all will happen meanwhile, it's not like the signatures would be updated every 5 minutes or it'd be the end of the world to not have the latest ones. Do NOT hammer the server 20 times per hour. That won't fix it. Broken checksums and server too busy are not pfSense package issues.
  • Understanding Snort "Block Offenders" and "IPS Policy Selection" options

    1
    0 Votes
    1 Posts
    924 Views
    No one has replied
  • Suricata 3.1.2_2 - Inline mode killing WAN em0

    6
    0 Votes
    6 Posts
    1k Views
    O
    @Redyr: @OCKTechMag: Ok. But what if…i mean just what if i want to use "Inline mode"?  :-\ My NIC 'em' is so called supported right? So why not HELP if you can to help me work it out? But your response is snark-ish don't you think? Whats the point of a TECH forum if folks seeking help are going to be meant with response as such? Don't you THINK that like many people i know that 'legacy' mode is available and work? Come on now! What chipset your em nic use? NIC info em0@pci0:1:0:0: class=0x020000 card=0x6c401462 chip=0x10d38086 rev=0x00 hdr=0x00     vendor    = 'Intel Corporation'     device    = '82574L Gigabit Network Connection'     class      = network     subclass  = ethernet     cap 01[c8] = powerspec 2  supports D0 D3  current D0     cap 05[d0] = MSI supports 1 message, 64 bit     cap 10[e0] = PCI-Express 1 endpoint max data 128(256) NS link x1(x1)                 speed 2.5(2.5) ASPM disabled(L0s/L1)     cap 11[a0] = MSI-X supports 3 messages, enabled                 Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]     ecap 0001[100] = AER 1 2 fatal 0 non-fatal 5 corrected em1@pci0:2:0:0: class=0x020000 card=0x6c401462 chip=0x10d38086 rev=0x00 hdr=0x00     vendor    = 'Intel Corporation'     device    = '82574L Gigabit Network Connection'     class      = network     subclass  = ethernet     cap 01[c8] = powerspec 2  supports D0 D3  current D0     cap 05[d0] = MSI supports 1 message, 64 bit     cap 10[e0] = PCI-Express 1 endpoint max data 128(256) NS link x1(x1)                 speed 2.5(2.5) ASPM disabled(L0s/L1)     cap 11[a0] = MSI-X supports 3 messages, enabled                 Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]     ecap 0001[100] = AER 1 2 fatal 0 non-fatal 5 corrected xhci0@pci0:0:20:0:      class=0x0c0330 card=0x1e318086 chip=0x1e318086 rev=0x04 hdr=0x00     vendor    = 'Intel Corporation'     device    = '7 Series/C210 Series Chipset Family USB xHCI Host Controller'     class      = serial bus     subclass  = USB     cap 01[70] = powerspec 2  supports D0 D3  current D0     cap 05[80] = MSI supports 8 messages, 64 bit enabled with 1 message ahci0@pci0:0:31:2:      class=0x010601 card=0x1e038086 chip=0x1e038086 rev=0x04 hdr=0x00     vendor    = 'Intel Corporation'     device    = '7 Series Chipset Family 6-port SATA Controller [AHCI mode]'     class      = mass storage     subclass  = SATA     cap 05[80] = MSI supports 1 message enabled with 1 message     cap 01[70] = powerspec 3  supports D0 D3  current D0     cap 12[a8] = SATA Index-Data Pair     cap 13[b0] = PCI Advanced Features: FLR TP
  • PfSense, Snort and Splunk

    3
    0 Votes
    3 Posts
    6k Views
    F
    Hi pfBasic, All that is needed is a Splunk installation and the app is installed on Splunk. I am running it on a standalone Splunk installation and running it 24/7. When Splunk and Snort for Splunk is installed, the app is viewed through any browser that connects to the Splunk server. I haven't tried using Splunk and Snort for Splunk on a VM, but I can't see why it shouldn't be installed on a VM. The setup for the Splunk and Snort for Splunk would be:- 1.) Install OS of choice (Windows, Linux, Mac OS X, Solaris, FreeBSD(?)). I don't know if there are still versions of Splunk available for FreeBSD. 2.) Install Splunk Enterprise and get a free licence. 3.) Connect to the Splunk server via the IP address (eg. 192.168.0.1:8000). 4.) Install Snort for Splunk from the SplunkBase through the web interface of the Splunk server and start monitoring the Snort logs. That's about it. Hope this helps. fugglefeet.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.