From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing Issues with core165 Development Build: next/cad86575
Date: Fri, 11 Mar 2022 16:28:53 +0000 [thread overview]
Message-ID: <5B9713D0-5822-4A0F-BE8A-A98019A8F72E@ipfire.org> (raw)
In-Reply-To: <24603ae9-dc06-4f58-a26f-eb413033db4d@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]
Hello,
I tried to reproduce this and I can’t.
Could you please send the output of “iptables -L -nv” to help me debug this?
-Michael
> On 8 Mar 2022, at 20:13, Charles Brown <cab_77573(a)yahoo.com> wrote:
>
> Just tried again with next/2022-03-08 09:59:43 +0000-32ce7ab4/x86_64
> It seems simple to reproduce. See attached log.
> At initial boot after fresh install, cannot ping local private address gateway -- DROP_HOSTILE
> After editing settings in /var/ipfiire/optionsfw/settings -- changing DROPHOSTILE to off -- and rebooting, things worked as expected.
> I then changed DROPHOSTILE setting to on and rebooted -- resulting again with DROP_HOSTILE when pinging my local gateway.
>
>
> On 3/8/2022 9:47 AM, Michael Tremer wrote:
>> Hello Charles,
>>
>>> On 7 Mar 2022, at 12:26, Charles Brown <cab_77573(a)yahoo.com> wrote:
>>>
>>> Did a fresh install of core165 Development Build: next/cad86575
>>>
>>> 1) Private Network is ‘Hostile’ – should it be?
>> No, it shouldn’t.
>>
>>> Initially, I had no access to red zone. All traffic was getting DROP_HOSTILE.
>>> My test setup has gateway through a 192.168 private network. Could not ping my 192.168 gateway without disabling the “drop hostile” feature. Somehow I thought that private network range would not be considered ‘hostile’.
>> Do you have some log files so I can look at what matched?
>>
>> What build are you running?
>>
>> -Michael
>>
>>> 2) Web page ids.cgi stops loading after header
>>> The page header down through "Intrusion Prevention System <?>" is displayed and then stops -- nothing else on the page
>>> Log in httpd error shows as:
>>> "Unable to read file /var/ipfire/suricata/ignored at /var/ipfire/general-functions.pl line 883. "
>>> I went to the directory and created the 'ignored' file and chowned it to nobody:nobody.
>>> That allowed the page to complete loading
>>>
>>> -cab
>>>
> <hostile_private_net.log>
next prev parent reply other threads:[~2022-03-11 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <06172f89-90ad-7851-ad93-25cd8d390c38.ref@yahoo.com>
2022-03-07 12:26 ` Charles Brown
2022-03-08 15:47 ` Michael Tremer
2022-03-08 20:13 ` Charles Brown
2022-03-11 16:28 ` Michael Tremer [this message]
2022-03-11 23:40 ` Charles Brown
2022-03-17 15:52 ` Michael Tremer
2022-03-17 19:34 ` Charles Brown
2022-03-18 9:14 ` Michael Tremer
[not found] <16a1fbd2-c1fc-50a5-8c58-5a85a0528f5c@yahoo.com>
2022-03-07 16:51 ` Stefan Schantl
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=5B9713D0-5822-4A0F-BE8A-A98019A8F72E@ipfire.org \
--to=michael.tremer@ipfire.org \
--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