Repository navigation
Dialerproxy and Fragment #4658
Replies: 10 comments 5 replies
|
@patterniha |
|
the tlshello-fragment(fragtls) length must be at least 6.(you set 2) |
|
کامل رو بفرست |
|
{ }, ], "routing": { } } |
|
The configuration main logic is as follows: tlshello does not work at any condition On PC. the second: and the first is the most efficient and has incredibly no delay compared to second one. (obviously) |
|
این چیه دیگه؟ |
|
یه سروره که دامنه ها بهش redirect میشن. |
|
اگر مشکل همینه میشه برداشتش؛ ولی مشکل از این نیست. |
|
خلاصه هدفت رو متوجه نشدم. باید با vless ی چیزی وصل شی به سرورت، سرور از کجا بفهمه به کجا باید وصل شه بعدش، مخصوصا وقتی فرگمنت هم بشه sniffing هم سمت سرور کار نمیکنه دیگه |
|
Found a way. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello there!
I'm struggling with a problem where in android , when i set fragment to tlshello and interval 0 , it works, however, on pc it just works if only i set to packet 1-1 and the size must not be over 4 and the interval is also 0
so I thought to use dialerproxy and try to chain tlshello and packet 1-1 , so both will be fragmented and my config would be unified.
but the problem came when i saw dialerproxy won't forward fragmented packets to frag1-1.
please help me figure this out.
the routing is set to fragtls.
on android, using packet 1-1 would not work.
{
"tag": "fragtls",
"protocol": "freedom",
"settings": {
"streamSettings": {
"sockopt": {
"dialerProxy": "frag1-1"
}
},
"fragment": {
"packets": "tlshello",
"length": "2",
"interval": "0"
}
}
},
{
"tag": "frag1-1",
"protocol": "freedom",
"settings": {
"redirect": "myserver:0",
"domainStrategy": "ForceIP",
"fragment": {
"packets": "1-1",
"length": "1",
"interval": "0"
}
}
}
All reactions