On Wed, Oct 7, 2020 at 5:39 PM Tom Eastep wrote:
>
> I work around this with the following rule in both the INVALID and NEW
> sections of my rules file.
>
> FIN(ACCEPT) { SOURCE=all, DEST=all }
>
> I also have this in the same two locations:
>
> RST(ACCEPT) { SOURCE=all, DEST=all }
Thank
On 10/7/20 4:14 AM, Vieri Di Paola wrote:
> Hi,
>
> If my rules allow HTTP and HTTPS access (ports 80, 443) with an ACCEPT
> rule such as the following
>
> ACCEPTlan1:10.215.144.0/23wantcp,udp80,443
>
> I'd like to know why I am seeing the following in the shorewall log
> when a
> On Wed, Oct 7, 2020 at 1:31 PM Simon Matter
> wrote:
>>
>> > Hi,
>> >
>> > If my rules allow HTTP and HTTPS access (ports 80, 443) with an ACCEPT
>> > rule such as the following
>> >
>> > ACCEPTlan1:10.215.144.0/23wantcp,udp80,443
>> >
>> > I'd like to know why I am seeing the fo
On Wed, Oct 7, 2020 at 1:31 PM Simon Matter wrote:
>
> > Hi,
> >
> > If my rules allow HTTP and HTTPS access (ports 80, 443) with an ACCEPT
> > rule such as the following
> >
> > ACCEPTlan1:10.215.144.0/23wantcp,udp80,443
> >
> > I'd like to know why I am seeing the following in th
> Hi,
>
> If my rules allow HTTP and HTTPS access (ports 80, 443) with an ACCEPT
> rule such as the following
>
> ACCEPTlan1:10.215.144.0/23wantcp,udp80,443
>
> I'd like to know why I am seeing the following in the shorewall log
> when a user accesses a web page:
>
> kernel: Shorewa
Hi,
If my rules allow HTTP and HTTPS access (ports 80, 443) with an ACCEPT
rule such as the following
ACCEPTlan1:10.215.144.0/23wantcp,udp80,443
I'd like to know why I am seeing the following in the shorewall log
when a user accesses a web page:
kernel: Shorewall:wan-lan1:DROP:I
