This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Firewall: v21.0 EAP1: Feedback and experiences (EAP Thread)

Release Post:  Sophos Firewall v21 Early Access Announcement 

Whats New Link: https://assets.sophos.com/X24WTUEQ/at/7t8k46h9ttmxt6pn8g58k7wb/sophos-firewall-key-new-features-v21.pdf 

Please provide feedback using the option at the top of every screen in your Sophos Firewall as shown below or via the Community Forums.

NOTE: Sophos Firewall v21 does NOT include support for XG and SG Series appliances. XG Series EOL is March 31, 2025.
XG/SG Hardware will find them self until the EOL on the V20.0 Branche with MR2 + 
Sophos SFOS Home users are not affected, as SFOS Home is running the software version. 

For LE Related config issues, please review this post first:  Let´s Encrypt Deep Dive & Debugging in SFOSv21.0  



Prioritize
[edited by: emmosophos at 5:20 PM (GMT -7) on 18 Oct 2024]
[locked by: Raphael Alganes at 1:47 PM (GMT -8) on 5 Nov 2024]
Parents
  • Could the use of the route blackhole feature be informed? Will it create the same blackhole used to discard packets in NAT? How do you teach here on the forum?

    We used blackhole a lot in dnat to kill packets in general on the firewall without using block/denied rules, until then it seemed to have better performance, both for outgoing and incoming.

    We use this blackhole + geoip a lot.

  • Hi  ,

    When a blackhole route is configured, the firewall silently drops any packets destined for the blackholed route without sending back any "Destination Unreachable" messages to the source. This is easier than configuring the NAT rule with some unreachable destination.

    Internally, we create a null0 route (functionality offered by FRR engine)

  • While the functionality is essentially as described above, we are internally creating a route of the form : 

    "ip route 30.30.30.0/24 blackhole"   

    -> this would install the route in the kernel and result in silently dropping the packets destined to 30.30.30.0/24

  • thanks, very good, we also used DNAT Blackhole to baypass the IPS and not consume CPU from accesses coming from the web, eliminating unauthorized access without reviewing the IPS mechanism.

    This will help a lot!! thanks.

Reply Children
No Data