OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 19.1 Legacy Series »
  • NAT and Floating rules
« previous next »
  • Print
Pages: [1]

Author Topic: NAT and Floating rules  (Read 2341 times)

BenKenobi

  • Newbie
  • *
  • Posts: 23
  • Karma: 4
    • View Profile
NAT and Floating rules
« on: May 22, 2019, 02:52:27 pm »
Can somebody have a look at priorities for blocking traffic vs port forwarding / NAT

I've just spotted this in my email server logs

lost connection after CONNECT from house.census.shodan.io[89.248.172.16]\nMay

but house.census.shodan.io is in a block list - (Alias configured as URL (IPs) and allocated to a floating block rule applied to all interfaces). The fact that this log entry exists tells me that something isn't working - shodan should have been blocked.

I don't want to debate the value of blocking such people - I don't invite strangers into my house to look around - this kind of intrusive scanning is no different to me.

I've also seen some 'attacked blocked' notices to port 80 on a system from Kaspersky but considered Kaspersky at fault as there is no port 80 forwarding to that system - now I'm not so sure OPNsense is doing what I expect.

For now I've moved the block rules to the interfaces and put them before any NAT generated rules, I'll be a bit disappointed if I see entries that I shouldn't in event logs going forward.
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 19.1 Legacy Series »
  • NAT and Floating rules
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2