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

XG230 - Web radio lost connection - Invalid traffic in the log => Could not associate packet to any connection

Hello,

i'm trying to found the origin of this problem : The connection to a web radio is lost after few minutes, there is a lot of Could not associate packet to any connection in the log to the IP of the web radio : 

I created a rules, this rules works

i did a packet filter : 

The rule 13

ip of radios.rtbf.be is 212.3.234.219, why have i a lot of Could not associate packet to any connection and some connection passed without any problem? 

 thank you for your help !



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

    has your access ever worked?

    Do you have do not scan streaming media ticked?

    The could not associate a packet means the connection has failed or timed out that means the firewalll blocks/dropa it.

    Ian

    XG115W - v19.5.1 mr-1 - Home

    If a post solves your question please use the 'Verify Answer' button.

  • Concerning the dropped packet, is that mean i need a specific firewall rules to solved it? Policy? How can i determine the origine of the problem to solve it? Thank you

  • "could not associate a packet" means that the remote site send a packet while firewall cannot associate that anymore to an existing connection. It's not something that a rule can fix as far as I know. It's more that XG thinks that the connection is closed and then again gets a packet for the previous connection.


    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

Reply
  • "could not associate a packet" means that the remote site send a packet while firewall cannot associate that anymore to an existing connection. It's not something that a rule can fix as far as I know. It's more that XG thinks that the connection is closed and then again gets a packet for the previous connection.


    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

Children
No Data