"
Hi, I am having the same issue.
Disabling circular logging fixed it as a workaround.
Disabling circular logging fixed it as a workaround.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
20.7 Legacy Series / Re: Why does the firewall sometimes flag blocked packets that are actually allowed?
November 26, 2020, 02:00:58 PM
Well I see the same thing.
I am pretty sure it did NOT happen before the 20.7.5 upgrade.
This is my backup machine trying to sync to the cloud (via p443).
For whatever reason default deny rule kicks in. Then after a few mins traffic gets through.
I am a bit puzzled but glad I just saw this post.
No changes in ruset...here is a block
this one passes
I am pretty sure it did NOT happen before the 20.7.5 upgrade.
This is my backup machine trying to sync to the cloud (via p443).
For whatever reason default deny rule kicks in. Then after a few mins traffic gets through.
I am a bit puzzled but glad I just saw this post.
No changes in ruset...here is a block
Code Select
__timestamp__ Nov 26 13:54:40
ack 4159507402
action [block]
anchorname
datalen 0
dir [in]
dst 185.179.130.30
dstport 443
ecn
id 30707
interface lagg0_vlan1
interface_name INT_MgmtVLAN_VL1
ipflags none
label Default deny rule
length 52
offset 0
proto 6
protoname tcp
reason match
rid 7ca0bdbea8e636fba2e984923ed67866
ridentifier 0
rulenr 38
seq
src 10.0.1.243
srcport 35072
subrulenr
tcpflags A
tcpopts
tos 0x0
ttl 64
urp 501
version 4
this one passes
Code Select
_timestamp__ Nov 26 14:01:55
ack
action [pass]
anchorname
datalen 0
dir [in]
dst 185.179.130.30
dstport 443
ecn
id 54761
interface lagg0_vlan1
interface_name INT_MgmtVLAN_VL1
ipflags none
label Allow HTTPS VL1
length 60
offset 0
proto 6
protoname tcp
reason match
rid deb4772f1e71b5c6ccd7ce018eb36304
ridentifier 0
rulenr 176
seq 3208949710
src 10.0.1.243
srcport 44558
subrulenr
tcpflags S
tcpopts
tos 0x0
ttl 64
urp 64240
version 4 #3
German - Deutsch / Re: System: Firmware: Reporter meldet Fehler in AcmeClient/certhelper.php
May 29, 2020, 10:22:20 AM
Ich habe diesen Fehler ebenfalls seit dem Update.
Er tritt nach jedem lauf des Acme Clients auf.
Ich habe bereits einen Fehlerreport verschickt.
Im englischen Forum wurde das ebenfalls erwähnt.
https://forum.opnsense.org/index.php?topic=17360.0
Es scheint schon einen Fix zu geben.
https://github.com/opnsense/plugins/commit/ee799d8c75f7aaffaee97439c95fd98263eb1b38
Müssen wir wohl abwarten, bis es im nächsten Release ist, oder selbst Hand anlegen.
Er tritt nach jedem lauf des Acme Clients auf.
Code Select
[29-May-2020 00:00:02 Europe/Berlin] PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /usr/local/opnsense/scripts/OPNsense/AcmeClient/certhelper.php on line 1421
[29-May-2020 00:00:02 Europe/Berlin] PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /usr/local/opnsense/scripts/OPNsense/AcmeClient/certhelper.php on line 1428
Ich habe bereits einen Fehlerreport verschickt.
Im englischen Forum wurde das ebenfalls erwähnt.
https://forum.opnsense.org/index.php?topic=17360.0
Es scheint schon einen Fix zu geben.
https://github.com/opnsense/plugins/commit/ee799d8c75f7aaffaee97439c95fd98263eb1b38
Müssen wir wohl abwarten, bis es im nächsten Release ist, oder selbst Hand anlegen.
Pages1
