Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails to detect Firewall policy change #306

Closed
guyacosta opened this issue Oct 23, 2019 · 4 comments
Closed

Fails to detect Firewall policy change #306

guyacosta opened this issue Oct 23, 2019 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@guyacosta
Copy link
Contributor

Describe the bug
Select a firewall policy like outgoing network communications for Candy Crush. Run ASA. Change the policy e.g. from Allow or enable to disabled. Run ASA. Note the change is not detected. I have seen it work but not consistently...Spotify for instance but not CC. Also for Spotify it reports a page worth of policy changes...might be same change I will check and update in comments.

Expected behavior
Report the change in policy

Screenshots
See screenshot

System Configuration (please complete the following information):

  • OS: Windows
  • OS Version: [e.g. Windows 10 1803]
  • Application Version: [e.g. 2.1.30-beta
  • CLI or GUI: GUI
    asabug3

Additional Context
Add any other context about the problem here.

@guyacosta guyacosta added the bug Something isn't working label Oct 23, 2019
@gfs
Copy link
Contributor

gfs commented Oct 23, 2019

If the data isn't surfaced out of the API I call I cannot do anything about it. However, I also cannot reproduce this.

@gfs gfs closed this as completed Oct 23, 2019
@guyacosta
Copy link
Contributor Author

I can consistently but I'll send you a video.

@guyacosta guyacosta reopened this Oct 24, 2019
@gfs
Copy link
Contributor

gfs commented Nov 14, 2019

Try again with the latest. Here's what I did that does work:

Open Control Panel
Navigate to "Windows Defender Firewall"
Navigate to "Advanced Settings"
Select "Inbound Rules"
Open an Administrator terminal window
Run asa.exe collect -F
Right Click a Rule and Delete it
Right Click another Rule and Disable it
Run asa.exe collect -F
Run asa.exe export-collect

@gfs
Copy link
Contributor

gfs commented Nov 14, 2019

I've also repro'd the correct behavior in the GUI. I suspect this may have been caused by a known issue which is now fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants