Skip to content

Navigation Menu

Sign in
Sign up

Правила роутинга по ссылке #456

Unanswered
UncleStark asked this question in Q&A
Discussion options

Не нашёл в приложении возможности добавить правила роутинга от подписки. Я не говорю даже о json singbox, например в Happ есть возможность передать в ссылке вида happ://routing/onadd base64 json правил. Даже если бы принимались правила с того же pastebin в формате экспорта exclave было бы удобно обновлять их централизованно

You must be logged in to vote

Replies: 3 comments 3 replies

Comment options

  • Please use English or Chinese. I can't understand other languages.
  • It is possible to specify an outbound for a rule, so rules are outbound-related, making it impossible to import/export rules and not import/export the related outbounds without losing the conplete information.
  • Routing rules contain device-specific information like UID, app and SSID. A remote provider can't know what is installed on your device and what SSID your local network environment has. Exportedd rules can't be guaranteed to work normally on others' devices.
  • Remote fetching app-dependent content should be prevented to avoid vendor lock-in.
  • Why should routing rules ever be provided remotely?
You must be logged in to vote
0 replies
Comment options

Because that's the current standard. Subscriptions in JSON format and subscriptions in Clash format also transmit routing rules, which are accepted by the client. The happ client accepts routing rules in base64 format along with outbounds links.

You must be logged in to vote
0 replies
Comment options

Really, it is needed to have a sample of the config (profile) file that can be used to be imported.
For example, can you just provide the sample profile file for mieru?
Any profile I used was declined as "no proxy server provided"

You must be logged in to vote
3 replies
Comment options

Port range parsing seems incorrect. Try https://github.com/ExclaveNetwork/Exclave/actions/runs/33387518096/job/99473371304
(mihomo config or share link, and backup before update)

Comment options

Port range parsing seems incorrect.

Great, thank you

Comment options

Just found that mieru config of another format is suitable with no changes in the code.
mierus://name:password@ip?handshake-mode=HANDSHAKE_STANDARD&mtu=1400&multiplexing=MULTIPLEXING_HIGH&port=yourport&profile=ProfileName&protocol=TCP
For mieru config you can set your own data instead of name; password; ip; yourport (for ip);ProfileName (Any word).
Thank you for great app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /