-
-
Notifications
You must be signed in to change notification settings - Fork 315
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
Portmaster+Proxifier compatibility #1365
Comments
Hey @squromiv, thank you for reporting on a compatibility. We keep a list of compatible software and user provided guides for improving compatibility in the wiki - please have a look there. If you have managed to establish compatibility with an application, please share your findings here. This will greatly help other users encountering the same issues. |
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
|
This message lacks in detail, can you specify what has failed? thanks! |
In detail: Portmaster fails to intercept connections before Proxifier. So it does not work correctly and does not filter traffic with applied rules. The developer of Proxifier noticed, that
Need to use both apps by this way:
That`s all. So is there any way to force these apps to work simultaneously? |
If I understand correctly, Proxifier will have to change their Filter Weight Assignment if they want to be run after other software: https://learn.microsoft.com/en-us/windows/win32/fwp/filter-weight-assignment Nothing we can do here to influence that. Here is where Portmaster's weight is set: https://github.com/safing/portmaster-windows-kext/blob/28593163f29c2976efa16f3458d809bf3577aafc/pm_kext/src/pm_register.c#L154 I don't know of other ways how to influence WFP callout order. |
Author of Proxifier reported:
|
not sure what your screenshot shows, but Portmaster always resolves the dns requests, so you get the info where the connection would be going... otherwise you would not see the destination ip or country.... resolving a domain is a different connection. it also does not connect to the provider, it only goes to the DNS server. |
It is not DNS query. ClipClip.exe attempts to connect to address q.blueswan.io in Proxifier besides of it is "blocked" in Portmaster. |
it does try yes, and to do so it needs to resolve the DNS first. Which Portmaster does, and then Portmaster blocks the actual connection. I am not familiar with proxifier so I cant say how you think you know that there is direct connection established. But pleas shed some more light on this. |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions. If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord. |
Portmaster last version
Proxifier
Windows Server 2016 x64
Fails to intercept connections before Proxifier.
The text was updated successfully, but these errors were encountered: