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

Troubleshooting "Could not associate packet to any connection"

Hello,

A bit of an amateur question. I'm newer to network security, especially firewalls and still trying to grasp how everything works. Was wondering how to troubleshoot issues when the firewall is clearly blocking traffic but I'm not sure what ports to open.

I've recently installed an XG series firewall on my network. Two applications have stopped working for me since then; Plex which is a video streaming service (I'm not hosting it myself, I'm reaching out to a friend's device over WAN for media they create) and an openvpn service I'm subscribed to. They have previously worked without issue and I've tried them when they're not behind the firewall, no issues. Checked Rulz #1, all I'm seeing is that Firewall rule 0 is dropping connecting for reason "Could not associate packet to any connection." I can narrow it down to the firewall policies because when I set a blanket LAN/WAN to WAN/LAN rule allowing all communication from any host the applications resume functionality. 

Guess my question is from a learning perspective since I'll probably run into similar issues down the road, how would you troubleshoot and figure out which firewall rules to create/apply to your network for individual applications? I tried wireshark and checked the XG logs while trying to reconnect those applications. Getting a lot of denials for a range of ports and sometimes multiple IP addresses (although most of the time the source port remains the same). 

Thanks in advance!



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

    First of all, "Invalid Traffic" in logviewer is not a clear indicator for an issue there.

    https://community.sophos.com/kb/en-us/131754

     

    You are already familiar with wireshark? Nice! 

    Try to do the dump on the XG and download the dump.

    https://community.sophos.com/kb/en-us/127647

     

    Most cases, those applications need a "helper" for the stateful firewall. And there is the issue.

    Can you "google" all needed Ports? 

    __________________________________________________________________________________________________________________

  • I've tried to Google extensively prior to posting. Not sure what you mean by "helper", can you please clarify?

    I think the Invalid Traffic is the issue since the same pattern always shows up when I try to launch this particular application. I'll watch the log viewer as I hit the refresh button and this is what I'm seeing every time. I've tried to create firewall rules to allow those ports, allow the IPs, and forward them to my LAN since it looks like they are being stopped at my WAN port. Not sure what I'm doing wrong here but I think if I get these to go through I should be set.

     

  • Hi,

    i can only comment, what i see, but seems like the XG firewall is not doing anything wrong here. 

    Those packets seems to be RST (RESET) Pakets and duplicate RST packets are normal and will be dropped by XG. 

    In fact, all stateful firewall do this.

    https://en.wikipedia.org/wiki/Stateful_firewall

     

    Your Client 172.16. already talked with the server. and the server or client wants to close the connection. 

    As you can see, source port 80 to high port is a already build up communication. 

    https://en.wikipedia.org/wiki/Transmission_Control_Protocol#Connection_establishment

    TCP handshake. 

    Like mentioned in the KBA, those packet drops are no issue at all. 

    Would suggest to check the application. This is no DNAT issue! Please delete the DNAT / WAN to LAN Rules. 

    __________________________________________________________________________________________________________________