From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: IPFire meets Suricata - Call for tester
Date: Sun, 16 Dec 2018 21:28:57 +0100 [thread overview]
Message-ID: <0c384081-dcdf-e4d4-763e-c7c73a1db34b@link38.eu> (raw)
In-Reply-To: <4b2449de-a247-df6f-d7ac-d8a0e5dae3e7@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]
Hello Stefan,
to be a bit more precise about the NAT issue:
My setup is the IPFire Suricata test VM running in KVM, with
two clients (Debian and OpenBSD) directly attached to it.
The Debian machine is located in GREEN, OpenBSD in ORANGE.
RED interface is connected via bridge to my actual testing LAN;
for the first testing, any outgoing traffic to the internet
was allowed (I will test upstream proxy behaviour later).
While GREEN was using IPv4 range 192.168.100.0/24, with IPFire
as 192.168.100.1, enabling Suricata caused packets coming from
GREEN not to be NATted anymore: Instead of using the firewall's
RED IP for destination, it was the internal GREEN IP.
Let me know whether is is useful or not. :-)
Thanks, and best regards,
Peter Müller
> Hello Stefan,
>
> back again. :-)
>
> The new IDS WebUI looks quite good so far - enabling/disabling
> Suricata works as well as selecting the rule source and the
> operation mode (IDS/IPS).
>
> I was also able to download the "Snort/VRT Community" ruleset.
> Trying to switch to the "Emerging Threats" ruleset is possible,
> but downloading its ruleset afterwards is not: The GUI simply
> stalls, printing a message that "Snort (!) is performing a task".
>
> The WebUI services page still shows IDS status for each interface,
> which does not seem to work anymore (everything is stopped, but
> Suricata was active on RED and GREEN).
>
> Further, a client located in GREEN behind the test firewall
> instance is unable to browse the internet as soon as Suricata is
> enabled. If disabled, downloading ET rulesets work as well as
> internet traffic. At the moment, I am flying blind here, but it looks
> like packets are not NATted anymore if Suricata is active.
>
> Any outgoing connection is in state "SYN_SENT" if Suricata is active.
>
> A portscan against the firewall (GREEN interface) is not detected,
> even though ET SCAN ruleset is enabled (used nmap with NSE active).
>
> Especially the outgoing connection/NAT/? issue mentioned above
> breaks things in my scenario. Anything else are minor issues (of
> course, a portscan should be detected, this needs further investigation
> indeed). WebUI works fine so far.
>
> Thanks again for your work; I hope the feedback can appreciate it somehow. :-)
>
> Let me know if there are questions.
>
> Thanks, and best regards,
> Peter Müller
>
--
Microsoft DNS service terminates abnormally when it recieves a response
to a DNS query that was never made. Fix Information: Run your DNS
service on a different platform.
-- bugtraq
next prev parent reply other threads:[~2018-12-16 20:28 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 19:43 Stefan Schantl
2018-12-11 20:53 ` Peter Müller
2018-12-12 20:54 ` Peter Müller
2018-12-16 20:28 ` Peter Müller [this message]
2018-12-17 14:21 ` Stefan Schantl
2018-12-17 17:05 ` Michael Tremer
2018-12-17 19:08 ` Stefan Schantl
2018-12-19 16:30 ` Michael Tremer
2018-12-20 13:03 ` Stefan Schantl
2018-12-20 14:05 ` Michael Tremer
2018-12-21 16:03 ` Tim FitzGeorge
2018-12-25 19:17 ` Stefan Schantl
2018-12-25 21:56 ` Michael Tremer
2018-12-25 19:03 ` Stefan Schantl
2019-01-01 13:32 ` Stefan Schantl
2019-01-02 15:54 ` Michael Tremer
2019-02-06 8:58 ` Stefan Schantl
2019-02-14 14:28 ` Stefan Schantl
2019-02-14 15:20 ` ummeegge
2019-02-14 18:01 ` Matthias Fischer
2019-02-14 21:49 ` Stefan Schantl
2019-02-14 23:16 ` Matthias Fischer
2019-02-14 23:36 ` Mentalic
2019-02-15 7:51 ` Stefan Schantl
2019-02-15 0:03 ` Mentalic
2019-02-15 7:54 ` Stefan Schantl
2019-02-17 11:58 ` Stefan Schantl
2019-02-17 12:59 ` Michael Tremer
2019-02-17 19:57 ` Stefan Schantl
2019-02-18 11:44 ` Michael Tremer
2019-02-18 13:09 ` Stefan Schantl
2019-03-03 11:37 ` ummeegge
2019-03-03 18:48 ` Stefan Schantl
2019-03-04 6:28 ` ummeegge
2019-02-18 13:16 ` Stefan Schantl
2019-02-18 22:11 ` Mentalic
2019-02-19 11:33 ` Stefan Schantl
2019-02-19 22:12 ` Mentalic
2019-02-19 23:22 ` Mentalic
2019-02-20 7:55 ` Stefan Schantl
2019-02-21 21:56 ` Mentalic
2019-02-22 10:21 ` Michael Tremer
2019-02-22 11:08 ` Stefan Schantl
2019-02-22 10:59 ` Stefan Schantl
2019-02-22 18:40 ` Mentalic
2019-02-20 7:19 ` Stefan Schantl
2019-03-03 14:39 ` Stefan Schantl
2019-03-03 17:33 ` Mentalic
2019-03-04 19:54 ` Mentalic
2019-03-05 9:31 ` Michael Tremer
[not found] <E1gf64O-0003zJ-Kt@smtprelay03.ispgateway.de>
2019-01-06 13:26 ` IPFire meets Suricata - Call for Tester Stefan Schantl
[not found] <79FF884C-B36B-42F5-A620-F2636E3706FC@gmail.com>
2019-02-06 9:57 ` IPFire meets Suricata - Call for tester Stefan Schantl
2019-02-06 10:43 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0c384081-dcdf-e4d4-763e-c7c73a1db34b@link38.eu \
--to=peter.mueller@link38.eu \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox