Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 53 replies
  • Subscribers 2 subscribers
  • Views 48498 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

Firewall fails to block an established UDP connection...

GreatByte
Hello Guys,

I am have a weird situation here. I have a PC communicating with a server, both connected to my Sophos Firewall (Firmware: 9.100-16 - not an appliance).

I have a Rule that allows this connection, and it works. Without that Rule, the connection cannot be established. So far so good.
Once established, however, the communication continues even if I disable that rule, or add a rule above it to block that connection. [:S]
It just keeps on working and there doesnt seem to be a way to block it if I wanted to...

I tried it using a PC connected via the Internet and I can even disable the DNat Rule and the connection still continues. Only new connections are being blocked. Is this an expected behavior? Doesnt seem right to me.

Greatbyte


This thread was automatically locked due to age.
Parents
  • 0
    Hi ,

    I don't know if there is a bug .
    But you can not terminate an active connection with a rule.
    Only when this connection will end then the next connection will be blocked.
    About the first issue you described that need to be checked.

    All my best.
    Gilipeled

    Gil Peled.

    CEO- Expert2IT LTD.

    SOPHOS Platinum Partner.

    Gil@expert2it.co.Il.

  • 0 in reply to gilipeled
    My firewall rules that use "time definitions" used to disconnect active sessions (e.g. web, iMessage) when that time of day was reached.  This is a change of behavior in the firewall from version 8.x to version 9.x  

    Thanks,  

    Bob.
    [:S]
Reply
  • 0 in reply to gilipeled
    My firewall rules that use "time definitions" used to disconnect active sessions (e.g. web, iMessage) when that time of day was reached.  This is a change of behavior in the firewall from version 8.x to version 9.x  

    Thanks,  

    Bob.
    [:S]
Children
No Data
Unfiltered HTML