finalMask is not applied in Base64 Hysteria2

Баг-репорты
1

Hi
Hysteria inbounds have hardcoded QUIC parameters as:

"quicParams" : {"congestion" : "brutal"},

that we cannot edit no matter what we put in server-side or client-side, I don’t know if it is intentional and design choice or a bug.

I’ll appreciate any clarifications.

Thanks

2

There is no hardcoded fields.

What exactly are we talking about? These parameters are passed to the client side via finalMask. The panel doesn’t modify finalMask in any way and only passes on what you’ve specified in it.

3

Hysteria inbound does not have any quicParams. Use finalMask in inbound configuration.

4

yes, i’m aware of it, i’m talking about this. no matter we change it to what, it stays same. even if we change the client-side final mask, it will send the congestion brutal but not our client-side udp mask and quic params

Screenshot 1405-04-01 at 22.23.34
Screenshot 1405-04-01 at 22.23.34810×626 46.3 KB

5

I think you should have clarified from the start that you were using a base64 subscription, not xray-json.

7

Seems like for base64 subscription finalMask is not passed for Hysteria2.

8

I think you should have clarified from the start that you were using a base64subscription, not xray-json.

You are right, sorry.

Seems like for base64 subscription finalMask is not passed for Hysteria2.

It should be, right? :smiley: Because as far I understood, it is clearly stated that finalmask will be sent to client with both json and base64 (in client-side finalmask modal)
However I’m just using the server-side mask, only for tests I changed the client side one.

Also I tried to use packetSize under salamander mask, it completely broke the hysteria and also was not sent to client(should be?)

9

Honestly, I’m not sure.

URI Scheme - Hysteria 2 – link is built according to the Hysteria2 documentation, as in the Xray documentation (VMessAEAD / VLESS 分享链接标准提案 · XTLS/Xray-core · Discussion #716 · GitHub) hysteria2:// is missing.

10

Should be fixed in latest dev.

11

Thanks! I’ll try with new build.

P.S: Confirmed, it now sends what is actually written in the inbound.