Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 1173 views
  • Users 0 members are here
Options
Suggested
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

Filter list BUG -- no filter for UDP 135

Bob M
There is no fliter for UDP port 135 in the Netbios group.

Thus people who think they are protected from Microsoft atttacks are not....

 


This thread was automatically locked due to age.
  • 0
    Bob M,

    sorry, but about what are you complaining? Astaro is blocking everything
    which is not explicetely allowed. Do you allow incoming port 135 connections 
    and do you have a NAT rule which makes those connections to a private
    network possible? 

    Greetings
    cyclops
        
  • 0 in reply to cyclops
    First if you want to ALLOW Netbios between two interfaces you typically MAY want to allow 135 (messaging service).

    If you are in a mode to ALLOW ANY (for example in a test), you may want to DENY somethings, like Netbios.

    But anyway, there is a Netbios group and it does not include even one of the most basic Microsoft ports:  135.

     
  • 0 in reply to Bob M
    So ? Define it if you wish to.

    As the previous poster stated, anything not explicitly ALLOWED through the firewall is blocked by default.
     
  • 0 in reply to Bob M
    An ANY allow rule even for testing is never nescessary but a potential security risk if you'd forget to switch it off again. With such a debugging rule you wouldn't receive any log entries (packet filter livelog) so I don't see the benefit.

    Greetings
    cyclops