Missing Xray's advanced settings

[TheLordOfTheKings]

Hi @alireza0 jan,
Some extra parameters make PBR, Chain proxying, TCP optimization, etc a lot easier and are currently missing in X-UI panels.

For Outbounds:

Mux and Fragmentation settings.
UseIPv4v6 and UseIPv6v4 as domain strategies.

For both inbounds and outbounds objects in X-UI:

TLSObject -> disableSystemRoot

and:

SockoptObject ->
"domainStrategy"
"dialerProxy"
"tcpKeepAliveInterval"
"tcpcongestion"
"interface"
"tcpMptcp"
"tcpNoDelay"

[alireza0]

Dear @Arash88 ,
Thank you for your kind suggestions.

X-UI is not going to provide all the features of xray-core.
I expect this panel to provide simple solutions for simple users.
Advanced users can do all in xray-core itself.

Regarding features:

• Mux: Is not usefull for server's outbounds and make it more slow! I am thinking to add it to JSON-SUB
• Fragment is implemented a long time ago
• Based on documentation, Domain strategies in routing object has not such these options. Query strategy in DNS has not as well
• disableSystemRoot: Most people don't have any idea about how it works. Adding this feature is not usefull for a big part of users.
• Sockopt is also a kind of advanced option. I am thinking to add some other parts in JSON-SUB

IMHO we should have a balance between providing all options and simplifying usage.
I would like to keep this issue, to add the options for JSON-SUB

[TheLordOfTheKings]

Dear @Arash88 , Thank you for your kind suggestions.

X-UI is not going to provide all the features of xray-core. I expect this panel to provide simple solutions for simple users. Advanced users can do all in xray-core itself.

Regarding features:

• Mux: Is not usefull for server's outbounds and make it more slow! I am thinking to add it to JSON-SUB
• Fragment is implemented a long time ago
• Based on documentation, Domain strategies in routing object has not such these options. Query strategy in DNS has not as well
• disableSystemRoot: Most people don't have any idea about how it works. Adding this feature is not usefull for a big part of users.
• Sockopt is also a kind of advanced option. I am thinking to add some other parts in JSON-SUB

IMHO we should have a balance between providing all options and simplifying usage. I would like to keep this issue, to add the options for JSON-SUB

Thanks a lot for responding, dadashi
All is fair with your view but please reconsider the Sockopt object, just the dialerProxy brings a lot of new possibilities for the end user and it's so simple to use and understand.
Sockopt's other options are amazing, simple, and valuable too, like Interface, tcpcongestion, ...
Please just think about extending support of Sockopt .🤓

Best regards bro.

[alireza0]

I will keep it in my mind.
Thank you for your hint :)

[pulsarice]

• Based on documentation, Domain strategies in routing object has not such these options. Query strategy in DNS has not as well

It seems that the documentation is outdated:
https://github.com/XTLS/Xray-core/blob/1c8375997d627d6ae40df4f4c242293d01659974/proxy/freedom/config.go#L9

[alireza0]

@pulsarice
Thank you for providing these information.
It is also exists in chinese version of documentation and is added since 1.8.6 as new features.

I will try to deploy it for next version.

[TheLordOfTheKings]

Thanks again @alireza0 joon,
Another thing is that enabling "External Proxy" for inbounds doesn't actually produce anything inside the xray-core configs, am I correct? I can't find anything about this function in Project X's wiki either. Does this thing actually mimic a genuine and secure TLS connection over Vless?

[pulsarice]

AFAIK it only affects the config links generated for users.

for example, I access my panel using this URI: domain.name:port/panel. I actually use another domain for connections from cloudflare CDN. if I don't fill external proxy, all user configs will use panel's domain.name to access the server. I add external proxies to mitigate that. (entering CDN domain name in external proxy). you can also enter additional clean IPs to be added your configs using "external proxy".

[alireza0]

DNS new strategies and outbound sockopt is now added to x-ui and will be available in next version.

[MK0ltra]

Some other missing features for freedom outbound that i noticed:
proxySettings and sendThrough

When i try to add this settings with "Add outbound with json" feature, they will be removed from final configuration and won't be saved. The only way i found to add them is through xray template.

[TheLordOfTheKings]

Some other missing features for freedom outbound that i noticed: proxySettings and sendThrough

When i try to add this settings with "Add outbound with json" feature, they will be removed from final configuration and won't be saved. The only way i found to add them is through xray template.

+1
Yes and also these options for inbounds are necessary and the developer must decide to implement them. Although some of these options need Autocomplete/Multi-select elements in GUI.

sockopt -> "dialerProxy"
sockopt -> "interface"

Anyway thanks @alireza0 jan

[alireza0]

Some other missing features for freedom outbound that i noticed: proxySettings and sendThrough

When i try to add this settings with "Add outbound with json" feature, they will be removed from final configuration and won't be saved. The only way i found to add them is through xray template.

@MK0ltra
sendThrough is not an option only for freedom protocol. I will add it soon for all the outbounds.
proxySettings is not recommended due to conflict with sockopt. dialerProxy (which is already added).
BTW: If you want to add an advanced config, it is beter to have it in Advanced Template tab.

@Arash88
sockopt. dialerProxy is already added and will be available in next release.
I assume that interface is a kind of enterprise usage which could not be useful for most of users. Although you are free to use all available configurations in Advanced Template tab.

[alireza0]

Thanks a lot for your suggestions.
I will close this issue and looking forward to hearing more helpful ideas based on common needs in new issues.