MASQUE + Psiphon chain connects with a long delay (much faster in other clients)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- networking
Research direction
The payload names no files or entry points, only the MASQUE and Psiphon chain and a related issue #171 about chain order. Start by reading the chain handling that #171 touches and reproduce the connect delay with logs. Done means the tunnel becomes usable at a time comparable to the other client, shown by a before-and-after connect timing.
Written by the indexing model from the issue text.
Description
Summary
When a MASQUE config is chained with Psiphon, the connection is established only after a noticeable delay. The same combination connects much faster in another client.
Steps to reproduce
- Add a MASQUE config.
- Combine/chain it with Psiphon.
- Connect and observe how long it takes until the tunnel is usable.
Expected
Connection time comparable to other clients using the same MASQUE + Psiphon setup.
Actual
Connection succeeds, but with a significant delay before it becomes usable.
Notes
- Possibly related to the MASQUE chain handling in #171 (different symptom: chain order there, connection latency here).
- Needs: app/core version, platform, the approximate connect time in Hiddify vs. the other client, and logs from the connect attempt.
- Dominant language
- Go
- Stars
- 237
- Forks
- 206
- Avg merge
- 3h 44m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hiddify/hiddify-core
-
interesting_feature_todo
Difficulty 4/5 1-2 days Newbie friendliness 45/100
hiddify/hiddify-core#173 ·
-
bug useful
Difficulty 3/5 1-2 days Newbie friendliness 48/100
hiddify/hiddify-core#171 · 5 comments ·
-
documentation interesting_feature_todo
Difficulty 5/5 Over a week Newbie friendliness 35/100
hiddify/hiddify-core#167 · 1 comment ·
-
useful
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hiddify/hiddify-core#124 ·
-
مشکل در openwrtOpenuseful
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hiddify/hiddify-core#80 ·
All issues in hiddify/hiddify-core
Similar issues
-
ssa: wait errors drop the kstatus message, so health check failures don't say whyPossibly taken @schdief claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Pin and verify Security Insights schema in lintinsights targetPossibly taken @imshubham22apr-gif claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gemaraproj/gemara#618 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
a2aproject/a2a-go#597 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
scopes: GetAllowedTopics, GetProtectedTopics, and GetScopedTopics include empty topic names and do not trim whitespace charactersPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day