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

Portmaster+Proxifier compatibility #1365

Closed
squromiv opened this issue Nov 19, 2023 · 12 comments
Closed

Portmaster+Proxifier compatibility #1365

squromiv opened this issue Nov 19, 2023 · 12 comments
Labels
in/compatibility TYPE: a report about in/compatibility stale ATTRIBUTE: this issue has not had recent activity

Comments

@squromiv
Copy link

Portmaster last version
Proxifier
Windows Server 2016 x64

Fails to intercept connections before Proxifier.

@squromiv squromiv added the in/compatibility TYPE: a report about in/compatibility label Nov 19, 2023
Copy link

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 can't find your software in the list, then a good starting point is our guide on How do I make software compatible with Portmaster.

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.

Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@Raphty
Copy link
Member

Raphty commented Nov 20, 2023

This message lacks in detail, can you specify what has failed? thanks!

@squromiv
Copy link
Author

squromiv commented Nov 30, 2023

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

We have not tested Proxifier with Portmaster app but from the description I see that it uses WFP technology on Widows.
Proxifier uses the same API, so conflicts are possible.

Need to use both apps by this way:

  1. filter apps and processes by Portmaster
  2. route "allowed" apps to different proxies or ethernet interfaces by Proxifier

That`s all. So is there any way to force these apps to work simultaneously?

@dhaavi
Copy link
Member

dhaavi commented Nov 30, 2023

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.

@squromiv
Copy link
Author

Author of Proxifier reported:

I have checked your link, the source code of Postmaster and Proxifier.
Postmaster sublayer weight is 0xFFFF. Proxifier is 0x800A. So Postmaster should be called before Proxifier.

@squromiv
Copy link
Author

squromiv commented Dec 13, 2023

But in fact, it is not working as it should. Or I do not understand smth.

As for example, in log of Proxifier I see

screen_2023 12 13 003

And in settings of Portmaster this app marked as totally blocked.

screen_2023 12 13 004

@Raphty
Copy link
Member

Raphty commented Dec 13, 2023

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.

@squromiv
Copy link
Author

but Portmaster always resolves the dns requests

It is not DNS query. ClipClip.exe attempts to connect to address q.blueswan.io in Proxifier besides of it is "blocked" in Portmaster.

@Raphty
Copy link
Member

Raphty commented Dec 14, 2023

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.

Copy link

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.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Feb 16, 2024
Copy link

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in/compatibility TYPE: a report about in/compatibility stale ATTRIBUTE: this issue has not had recent activity
Projects
None yet
Development

No branches or pull requests

3 participants