As I was observing the behavior of the Avast Firewall application and it's interaction with the GUI I have just a questions or two that I hope someone could shed some light on.  Mostly out of curiosity, as the issue for many does indeed appear to be a setting in their firewall at this time.

 

• With Firewall in original state:

Connection to Unraid GUI would be established, sometimes across several dynamic TCP ports, and then promptly report all closed.  Closing the tab, switching browsers, or relaunching a browser session would all report a single port connection as closed.

Avast Firewall logs this as a blocked address due to Port Scan Detection

 

• With Firewall disabled:

Connection with the Unraid GUI is established in Chrome, several dynamic TCP ports appear to be established.  I don't see a state change in the Avast logs.  Other tabs continue to report as Established.  Refreshing the Unraid GUI causes one or more dynamic ports to appear established until the refresh is complete.  Then they vanish from the Avast connections GUI again.

Chrome task manager reports the connection as active, with occasional transfers, & Windows resource manager shows these TCP connections as active.

It appears that Avast is using the Windows Task Manager to determine what they display in their Firewall Connections GUI.  As the listings appear to match what is listed as the active tabs for Chrome in TaskMan.

 

• With Firewall enabled but permissions for IP address changed:

Connection to Unraid GUI is established, several dynamic TCP ports are established.  Activity everywhere I look...

Avast Network Connections GUI reports Unraid IP address with numerous dynamic ports in a state of RST Wait, they load approx. 1KB and then the port connection is closed and a new one is established.  New connections are immediately reporting RST Wait and repeat the cycle, & connections are opened on ports sequentially ad infinitum. 

Windows Resource Manager reports the same behavior as I'm watching the TCP connections.  Approximately 6-8 connections at a time.

 

I do hope that the suggestions I made earlier aren't causing more issues or unnecessary activity.  Can anyone better summarize what is happening here?

 

If so, can you point me to a book or two to read up on how to understand this better? 

Edited April 21, 20179 yr by TheFullTimer

Update, 4/21/17 11:02p est

Disabling port scan detection in the Avast firewall exhibits the same behavior with numerous port connections starting & closing in a repeating cycle of RST Wait.   Disabling the Avast firewall does not show this same behavior.

Bump, hoping someone with more networking experience can understand what a neophyte is describing

Sent from my Nexus 6P using Tapatalk