Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 11256 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

Invalid Traffic Issuce

Jugnoo

I am receiving invalid traffic issue in my logs. Screenshots attached. please guide.

 



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

    Hi  

    Do you experience any network or application issues when using the 192.168.0.71 device when these invalid traffic drops occur?
    Could you also please share the details of the firewall rule ID 2? I also noticed that the ingress interface appears to be a LAG interface, is this the case?

    Regards,

    FloSupport | Community Support Engineer

  • 0 in reply to FloSupport

     

     

    Both LAN (Port#1&4)& WAN(Port#2&5) are configured as LAG. 

  • 0 in reply to Jugnoo

    Hi  

    The information below comes from this post:

    "The logs 'Could not associate packet to any connection.', is generated in following case:

    • In case appliance receives any packet, which does not have an already established connection. Hence no associated conntrack is found for that particular packet.
    • The connection from the appliance has timed out, but client is still retrying by re-transmitting packets with old connection id.
    • This invalid log reason, is not due to any error in appliance or configuration issue. Rather it occurs due to network packets received by appliance for which it has no related connection.

    Invalid traffic logging can be turned OFF, to avoid logging these packets frequently.

    Earlier this logging was disabled by default, which could be the reason of not noticing these logging.We have enabled "Invalid traffic" logging in SFOSv17 with factory default configuration."

    You could try the suggestion posted here to test if this resolves the entries you are seeing.

    Regards,

    FloSupport | Community Support Engineer

Reply
  • 0 in reply to Jugnoo

    Hi  

    The information below comes from this post:

    "The logs 'Could not associate packet to any connection.', is generated in following case:

    • In case appliance receives any packet, which does not have an already established connection. Hence no associated conntrack is found for that particular packet.
    • The connection from the appliance has timed out, but client is still retrying by re-transmitting packets with old connection id.
    • This invalid log reason, is not due to any error in appliance or configuration issue. Rather it occurs due to network packets received by appliance for which it has no related connection.

    Invalid traffic logging can be turned OFF, to avoid logging these packets frequently.

    Earlier this logging was disabled by default, which could be the reason of not noticing these logging.We have enabled "Invalid traffic" logging in SFOSv17 with factory default configuration."

    You could try the suggestion posted here to test if this resolves the entries you are seeing.

    Regards,

    FloSupport | Community Support Engineer

Children
No Data