Show Posts
1
19.7 Legacy Series / [Solved] Default deny rule
« on: August 07, 2019, 02:33:43 pm »
I'm fairly new to OPNsense, running since March but came from m0n0wall through SmallWall
I have found it reasonably straightforward including IPv6 and I have followed the upgrades within some days of release since installing. Currently 19.7.2 on HP T610, Intel PRO/1000 quad NIC
The last few days when I have come to send large mails through Claws-Mail I am seeing Default deny rule messages between my desktop and my ISP's server. All was working well for large mails at least until mid June so I suspect changes since 19.1.10, perhaps 19.1.9?
Generally I am seeing this as the file uploads..
WAN Aug 7 13:17:25 [2001:myDekstop:6d2]:36552 [2001:ISPmail::21]:993 tcp let out anything from firewall host itself
in the past Claws has shown a progress bar as the message is sent, now it stalls with this..
WAN Aug 7 13:18:31 [2001ISPmail::21]:993 [2001:myDekstop:6d2]:36552 tcp Default deny rule
Earlier today I had similar Default deny rule but from LAN and src and dest swapped
What has changed and how should I deal with it here? What is triggering the Default deny rule and what controls it?
At the moment I am very tempted to revert to 19.1 but perhaps there is a simple answer.
TIA
fruit
I have found it reasonably straightforward including IPv6 and I have followed the upgrades within some days of release since installing. Currently 19.7.2 on HP T610, Intel PRO/1000 quad NIC
The last few days when I have come to send large mails through Claws-Mail I am seeing Default deny rule messages between my desktop and my ISP's server. All was working well for large mails at least until mid June so I suspect changes since 19.1.10, perhaps 19.1.9?
Generally I am seeing this as the file uploads..
WAN Aug 7 13:17:25 [2001:myDekstop:6d2]:36552 [2001:ISPmail::21]:993 tcp let out anything from firewall host itself
in the past Claws has shown a progress bar as the message is sent, now it stalls with this..
WAN Aug 7 13:18:31 [2001ISPmail::21]:993 [2001:myDekstop:6d2]:36552 tcp Default deny rule
Earlier today I had similar Default deny rule but from LAN and src and dest swapped
What has changed and how should I deal with it here? What is triggering the Default deny rule and what controls it?
At the moment I am very tempted to revert to 19.1 but perhaps there is a simple answer.
TIA
fruit