Closed M33FT closed 2 years ago
could you please provide the image you built so i can test locally
ipset seems to be a forgotten dependency... extra_command only works with Snapshot but that's of no use. I'll fix those problems
Thank you for your prompt response. I compiled Luci-app-xray in two version.
I tested both versions. But I did not succeed. The ipset package is automatically downloaded and installed from Repo when installed, but I do not know if this version has a problem with luci-app-xray or not.
actually ipset
command is not kmod-ipt-ipset
module. maybe try opkg install ipset
You are right. I did not know. The ipset problem seems to be fixed but still not connected. Is there anything else I need to follow in the logs?
that seems like a correct startup log. check your LuCI for configuration pages
I'm going to Luci . . .
Let me explain first. Before using your app on the official openwrt version, I used Passwall on custom Lionel or Coolwolf versions and was really confused because there was no setup guide. I want to say that if I messed up somewhere, please do not laugh too much lol. I do not fully understand the settings, because it is complicated xD
Server side config:
Server: topsecret Port: 443 Protocol: VLESS Stream Security: XTLS ID: d301635e-fae9-468b-8877-cd1b526caa13 Transport Protocol: TCP Flow: xtls-rprx-splice
Thank you for looking at the photos carefully so that I do not enter any wrong settings.
I do not live in China, but where I am, many proxies fail. Where I live, they interfere with proxy DNS requests to interfere with proxies, which I used to block the Stubby or https-dns-proxy package. Now my question is whether there is a need to activate these packages?
I have to say that I use V2rayN (with the said settings) on my PC and I have no problem.
Are the settings I made correct? Can you guide me? Because I'm really confused and I do not know what to do. Thanks ;-)
Where I live, they interfere with proxy DNS requests to interfere with proxies,
This package uses Xray to deal with all DNS queries so you don't need https-dns-proxy or other DNS proxies (and they are quite likely to interfere with Xray DNS server).
In your case specify 1.1.1.1 for all 3 DNS servers in the DNS tab to make sure all DNS queries is forwarded by Xray
Other configuration seems fine.
One more thing: if you use domain names to connect to your top secret host, you have to ask dnsmasq to resolve your domain name with a local dns server or it would result in a dead loop trying to figure out your host
Thanks for taking the time to answer my questions.
Now I'm sure the only part I'm having trouble with is the DNS partition, which makes it impossible to resolve.
According to what you said, I changed three DNS to 1.1.1.1
I deleted dnsmasq and installed the dnsmasq-full version instead
But in DHCP and DNS I did not understand what you mean. Can you explain more precisely?
Now I use Domain logically instead of Xray ip server. You assume this is my server address "topsecret.com".
You mean now in the DNS Forwarding section I have to enter the value "/topsecret.com/1.1.1.1" Enter. it's true?
And in this case, there is no need to activate the "ignore resolve file" option. it's true ??
Of course, I entered what I said, but I did not connect. I'm sure I misunderstood somewhere (▱˘︹˘▱)
I deleted dnsmasq and installed the dnsmasq-full version instead
no need to do that...
And in this case, there is no need to activate the "ignore resolve file" option. it's true ??
no need to activate that...
You just need to specify your own top secret host domain to be resolved by a local dns (in your case try 192.168.0.3) here like /topsecret.com/192.168.0.3
.
if it does not work
/topsecret.com/114.114.114.114
in the section beforeThank you very much for your help. In these three hours, based on what you said, I did a lot of tests, but unfortunately it did not work (▱˘︹˘▱) Thanks for your guidance. Good luck bro
closing due to inactivity
After I was able to compile the package with your help, the next problem that occurred to me after installation is clear in the image:
The ipset package is installed, but it looks like there is a problem with the Config file. I do not understand. Where can the problem be ? I have to say that I am using the official precompiled version 19.7.6 for RaspberryPi 3B.
Thanks ;-)