Closed padima2 closed 1 year ago
@padima2
Though, I don’t know where you stuck , I will say It’s simple for configuring for the first time.
As you mentioned, really haven’t enough guidance till now, Causes the project is in the early phase as @yichya indicates on documentation.
For the first time, just leave these 4 tabs in its default state, and no need adjusting anything there - - Proxy Settings, DNS Settings, HTTPS Server, Extra Options, Custom Options.
So, you can focus these 2 tabs only - - General Settings & Transparent Proxy Rules.
In tab “General Settings”, keep these 3 options checked - - Enable Transparent Proxy & Enable Sniffing & Route Only.
In tab “Transparent Proxy Rules”, cn for GeoIP Direct Code List, IPOnDemand for Routing Domain Strategy, if you use luci-app-xray in Mainland China. And just leave any other in default. It’s enough.
This project luci-app-xray is the best in my opinion, It’s really thin and elegant. I never see any other achieve its success on these 2 points.
I used lots of solutions such as Shadowsocks-libev, Passwall, Clash, on OpenWRT in the last 10 years, I will say, luci-app-xray is the best.
Keep going and wish you succeed to run it well.
@yukeiyang i ve tried exactly what you wrote above (after deleting all my settings and reinstalling xray) ,but unfortunately the result is not better: my ip is not changing , in my previous settings i was able to use the sokcs5 settings provided by xray to connect telegram with ,with your settings it s not working i had to add manually the two geo files as i didnt find them in the packages , and also i m not in mainland china so i dont think it ll be of any help is there any log or else will give you more info? let me know what you need and where i can find them thank you
and also i m not in mainland china
Try clearing GeoIP Direct Code List here
@padima2
1, Try the solution of @yichaya mentioned in the last post.
2, as you said.
i had to add manually the two geo files as i didnt find them in the packages , and also i m not in mainland china so i dont think it ll be of any help
you should adjust your Fast DNS as your local dns, for example, 192.168.1.1 or your ISP dns.
@yichya @yukeiyang i ve done both your suggested modification but no change ,this is the last log i ve copied, if you can see anything wich can help :
Thu Oct 13 07:49:54 2022 daemon.info xray[23519]: 2022/10/13 07:49:54 192.168.1.103:50734 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:54 2022 daemon.info xray[23519]: 2022/10/13 07:49:54 192.168.1.103:50735 accepted tcp:91.108.56.129:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:54 2022 daemon.info xray[23519]: 2022/10/13 07:49:54 192.168.1.103:50736 accepted tcp:91.108.56.129:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:55 2022 daemon.info xray[23519]: 2022/10/13 07:49:55 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:49:56 2022 daemon.info xray[23519]: 2022/10/13 07:49:56 192.168.1.103:50738 accepted tcp:142.251.37.106:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:56 2022 daemon.info xray[23519]: 2022/10/13 07:49:56 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:49:56 2022 daemon.info xray[23519]: 2022/10/13 07:49:56 192.168.1.103:50739 accepted tcp:91.108.56.129:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:56 2022 daemon.info xray[23519]: 2022/10/13 07:49:56 192.168.1.103:50740 accepted tcp:91.108.56.129:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:56 2022 daemon.info xray[23519]: 2022/10/13 07:49:56 192.168.1.103:50741 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:57 2022 daemon.info xray[23519]: 2022/10/13 07:49:57 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:49:57 2022 daemon.info xray[23519]: 2022/10/13 07:49:57 192.168.1.103:50742 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:58 2022 daemon.info xray[23519]: 2022/10/13 07:49:58 192.168.1.103:50743 accepted tcp:149.154.167.91:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:58 2022 daemon.info xray[23519]: 2022/10/13 07:49:58 192.168.1.103:50744 accepted tcp:149.154.167.91:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:58 2022 daemon.info xray[23519]: 2022/10/13 07:49:58 192.168.1.103:50745 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:49:58 2022 daemon.info xray[23519]: 2022/10/13 07:49:58 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:49:59 2022 daemon.info xray[23519]: 2022/10/13 07:49:59 192.168.1.103:50748 accepted tcp:142.251.36.106:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:00 2022 daemon.info xray[23519]: 2022/10/13 07:50:00 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:00 2022 daemon.info xray[23519]: 2022/10/13 07:50:00 192.168.1.103:50752 accepted tcp:91.108.56.129:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:00 2022 daemon.info xray[23519]: 2022/10/13 07:50:00 192.168.1.103:50753 accepted tcp:91.108.56.129:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:01 2022 daemon.info xray[23519]: 2022/10/13 07:50:01 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:01 2022 daemon.info xray[23519]: 2022/10/13 07:50:01 192.168.1.103:50756 accepted tcp:149.154.175.50:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:01 2022 daemon.info xray[23519]: 2022/10/13 07:50:01 192.168.1.103:50755 accepted tcp:149.154.175.54:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:01 2022 daemon.info xray[23519]: 2022/10/13 07:50:01 192.168.1.103:50754 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:01 2022 daemon.info xray[23519]: 2022/10/13 07:50:01 192.168.1.103:50758 accepted tcp:149.154.175.50:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:01 2022 daemon.info xray[23519]: 2022/10/13 07:50:01 192.168.1.103:50757 accepted tcp:149.154.175.54:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:02 2022 daemon.info xray[23519]: 2022/10/13 07:50:02 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:02 2022 daemon.info xray[23519]: 2022/10/13 07:50:02 192.168.1.103:50760 accepted tcp:149.154.175.54:443 [tproxy_tcp_inbound -> direct]
Papajoe, [13/10/2022 09:53]
Thu Oct 13 07:50:02 2022 daemon.info xray[23519]: 2022/10/13 07:50:02 192.168.1.103:50761 accepted tcp:149.154.175.50:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:02 2022 daemon.info xray[23519]: 2022/10/13 07:50:02 192.168.1.103:50763 accepted tcp:149.154.175.50:80 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:02 2022 daemon.info xray[23519]: 2022/10/13 07:50:02 192.168.1.103:50762 accepted tcp:149.154.175.54:80 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:03 2022 daemon.info xray[23519]: 2022/10/13 07:50:03 192.168.1.103:50764 accepted tcp:142.251.37.106:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:03 2022 daemon.info xray[23519]: 2022/10/13 07:50:03 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198]
Thu Oct 13 07:50:04 2022 daemon.info xray[23519]: 2022/10/13 07:50:04 192.168.1.103:50767 accepted tcp:149.154.175.50:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:04 2022 daemon.info xray[23519]: 2022/10/13 07:50:04 192.168.1.103:50766 accepted tcp:149.154.175.54:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:04 2022 daemon.info xray[23519]: 2022/10/13 07:50:04 192.168.1.103:50769 accepted tcp:149.154.175.50:80 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:04 2022 daemon.info xray[23519]: 2022/10/13 07:50:04 192.168.1.103:50768 accepted tcp:149.154.175.54:80 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:04 2022 daemon.info xray[23519]: 2022/10/13 07:50:04 192.168.1.103:50770 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:05 2022 daemon.info xray[23519]: 2022/10/13 07:50:05 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198]
Thu Oct 13 07:50:05 2022 daemon.info xray[23519]: 2022/10/13 07:50:05 192.168.1.103:50771 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:05 2022 daemon.info xray[23519]: 2022/10/13 07:50:05 127.0.0.1:51749 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound]
Thu Oct 13 07:50:05 2022 daemon.info xray[23519]: 2022/10/13 07:50:05 UDP:192.168.14.30:53 cache HIT: td.telegram.org -> []
Thu Oct 13 07:50:09 2022 daemon.info xray[23519]: 2022/10/13 07:50:09 192.168.1.103:50783 accepted tcp:149.154.167.41:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:09 2022 daemon.info xray[23519]: 2022/10/13 07:50:09 192.168.1.103:50781 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:09 2022 daemon.info xray[23519]: 2022/10/13 07:50:09 192.168.1.103:50784 accepted tcp:149.154.167.41:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:09 2022 daemon.info xray[23519]: 2022/10/13 07:50:09 192.168.1.103:50785 accepted tcp:149.154.167.50:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:10 2022 daemon.info xray[23519]: 2022/10/13 07:50:10 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:10 2022 daemon.info xray[23519]: 2022/10/13 07:50:10 192.168.1.103:50788 accepted tcp:149.154.167.41:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:10 2022 daemon.info xray[23519]: 2022/10/13 07:50:10 192.168.1.103:50787 accepted tcp:149.154.167.50:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:10 2022 daemon.info xray[23519]: 2022/10/13 07:50:10 192.168.1.103:50790 accepted tcp:149.154.167.41:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:10 2022 daemon.info xray[23519]: 2022/10/13 07:50:10 192.168.1.103:50789 accepted tcp:149.154.167.50:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:11 2022 daemon.info xray[23519]: 2022/10/13 07:50:11 192.168.1.103:50791 accepted tcp:142.251.37.106:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:11 2022 daemon.info xray[23519]: 2022/10/13 07:50:11 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:12 2022 daemon.info xray[23519]: 2022/10/13 07:50:12 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:12 2022 daemon.info xray[23519]: 2022/10/13 07:50:12 192.168.1.103:50793 accepted tcp:149.154.167.50:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:12 2022 daemon.info xray[23519]: 2022/10/13 07:50:12 192.168.1.103:50794 accepted tcp:149.154.167.41:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:12 2022 daemon.info xray[23519]: 2022/10/13 07:50:12 192.168.1.103:50796 accepted tcp:149.154.167.41:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:12 2022 daemon.info xray[23519]: 2022/10/13 07:50:12 192.168.1.103:50795 accepted tcp:149.154.167.50:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:12 2022 daemon.info xray[23519]: 2022/10/13 07:50:12 192.168.1.103:50797 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:13 2022 daemon.info xray[23519]: 2022/10/13 07:50:13 192.168.1.103:50798 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:13 2022 daemon.info xray[23519]: 2022/10/13 07:50:13 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:14 2022 daemon.info xray[23519]: 2022/10/13 07:50:14 192.168.1.103:50799 accepted tcp:149.154.167.91:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:14 2022 daemon.info xray[23519]: 2022/10/13 07:50:14 192.168.1.103:50800 accepted tcp:149.154.167.91:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:14 2022 daemon.info xray[23519]: 2022/10/13 07:50:14 192.168.1.103:50801 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:15 2022 daemon.info xray[23519]: 2022/10/13 07:50:15 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:15 2022 daemon.info xray[23519]: 2022/10/13 07:50:15 192.168.1.103:50802 accepted tcp:142.251.36.106:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:16 2022 daemon.info xray[23519]: 2022/10/13 07:50:16 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:16 2022 daemon.info xray[23519]: 2022/10/13 07:50:16 192.168.1.103:50804 accepted tcp:149.154.167.50:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:16 2022 daemon.info xray[23519]: 2022/10/13 07:50:16 192.168.1.103:50805 accepted tcp:149.154.167.41:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:16 2022 daemon.info xray[23519]: 2022/10/13 07:50:16 192.168.1.103:50807 accepted tcp:149.154.167.41:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:16 2022 daemon.info xray[23519]: 2022/10/13 07:50:16 192.168.1.103:50806 accepted tcp:149.154.167.50:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:17 2022 daemon.info xray[23519]: 2022/10/13 07:50:17 192.168.1.103:50809 accepted tcp:149.154.175.100:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:17 2022 daemon.info xray[23519]: 2022/10/13 07:50:17 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:17 2022 daemon.info xray[23519]: 2022/10/13 07:50:17 192.168.1.103:50808 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:17 2022 daemon.info xray[23519]: 2022/10/13 07:50:17 192.168.1.103:50810 accepted tcp:149.154.175.100:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 127.0.0.1:45527 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 127.0.0.1:45746 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 192.168.1.103:61370 accepted udp:8.8.8.8:53 [tproxy_udp_inbound -> direct] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 192.168.1.103:50813 accepted tcp:149.154.175.100:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 192.168.1.103:50814 accepted tcp:149.154.175.100:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 127.0.0.1:43174 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 192.168.1.103:50815 accepted tcp:130.158.6.123:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 192.168.1.103:51870 accepted udp:130.158.6.123:53 [tproxy_udp_inbound -> direct] Thu Oct 13 07:50:18 2022 daemon.info xray[23519]: 2022/10/13 07:50:18 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:19 2022 daemon.info xray[23519]: 2022/10/13 07:50:19 192.168.1.103:51869 accepted udp:8.8.8.8:53 [tproxy_udp_inbound -> direct] Thu Oct 13 07:50:19 2022 daemon.info xray[23519]: 2022/10/13 07:50:19 192.168.1.103:50816 accepted tcp:142.251.37.106:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:19 2022 daemon.info xray[23519]: 2022/10/13 07:50:19 192.168.1.103:51871 accepted udp:130.158.6.107:5004 [tproxy_udp_inbound -> direct] Thu Oct 13 07:50:19 2022 daemon.info xray[23519]: 2022/10/13 07:50:19 127.0.0.1:57588 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound] Thu Oct 13 07:50:19 2022 daemon.info xray[23519]: 2022/10/13 07:50:19 192.168.1.103:59509 accepted udp:8.8.8.8:53 [tproxy_udp_inbound -> direct] Thu Oct 13 07:50:20 2022 daemon.info xray[23519]: 2022/10/13 07:50:20 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198] Thu Oct 13 07:50:20 2022 daemon.info xray[23519]: 2022/10/13 07:50:20 192.168.1.103:50820 accepted tcp:149.154.175.100:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:20 2022 daemon.info xray[23519]: 2022/10/13 07:50:20 192.168.1.103:50821 accepted tcp:149.154.175.100:80 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:20 2022 daemon.info xray[23519]: 2022/10/13 07:50:20 192.168.1.103:50822 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct] Thu Oct 13 07:50:21 2022 daemon.info xray[23519]: 2022/10/13 07:50:21 127.0.0.1:60582 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound] Thu Oct 13 07:50:21 2022 daemon.info xray[23519]: 2022/10/13 07:50:21 192.168.1.103:57128 accepted udp:8.8.8.8:53 [tproxy_udp_inbound -> direct] Thu Oct 13 07:50:21 2022 daemon.info xray[23519]: 2022/10/13 07:50:21 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198]
Thu Oct 13 07:50:21 2022 daemon.info xray[23519]: 2022/10/13 07:50:21 192.168.1.103:50823 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:22 2022 daemon.info xray[23519]: 2022/10/13 07:50:22 192.168.1.103:50824 accepted tcp:149.154.167.91:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:22 2022 daemon.info xray[23519]: 2022/10/13 07:50:22 192.168.1.103:50825 accepted tcp:149.154.167.91:80 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:22 2022 daemon.info xray[23519]: 2022/10/13 07:50:22 192.168.1.103:50826 accepted tcp:216.239.38.120:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:22 2022 daemon.info xray[23519]: 2022/10/13 07:50:22 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198]
Thu Oct 13 07:50:23 2022 daemon.info xray[23519]: 2022/10/13 07:50:23 192.168.1.103:59510 accepted udp:94.177.241.136:40000 [tproxy_udp_inbound -> direct]
Thu Oct 13 07:50:23 2022 daemon.info xray[23519]: 2022/10/13 07:50:23 192.168.1.103:50828 accepted tcp:142.251.36.106:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:24 2022 daemon.info xray[23519]: 2022/10/13 07:50:24 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198]
Thu Oct 13 07:50:24 2022 daemon.info xray[23519]: 2022/10/13 07:50:24 192.168.1.103:50830 accepted tcp:130.158.6.123:443 [tproxy_tcp_inbound -> direct]
Thu Oct 13 07:50:25 2022 daemon.info xray[23519]: 2022/10/13 07:50:25 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198]
Thu Oct 13 07:50:25 2022 daemon.info xray[23519]: 2022/10/13 07:50:25 127.0.0.1:60726 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound]
Thu Oct 13 07:50:25 2022 daemon.info xray[23519]: 2022/10/13 07:50:25 UDP:192.168.14.30:53 cache HIT: td.telegram.org -> []
Thu Oct 13 07:50:29 2022 daemon.info xray[23519]: 2022/10/13 07:50:29 127.0.0.1:60746 accepted udp:8.8.8.8:53 [dns_server_inbound_5300 -> dns_server_outbound] Thu Oct 13 07:50:30 2022 daemon.info xray[23519]: 2022/10/13 07:50:30 UDP:192.168.14.30:53 cache HIT: www.apple.com -> [23.47.112.198]
my thought is that xray doesnt send anything in my vless server but why?
1, please ensure the xray server configured well and has no error. you can use https://github.com/wulabing/Xray_onekey to create the server. there are only 2 commands that need to be run, very simple.
$ apt install socat -y
$ wget -N --no-check-certificate -q -O install.sh "https://raw.githubusercontent.com/wulabing/Xray_onekey/main/install.sh" && chmod +x install.sh && bash install.sh
The correct server end installed well should be like this below:
address: cloudfree.com port: 443 UUID: d29e75af-e2b5-4ac6-bf5b-6839c9831770 flow: xtls-rprx-direct security: none network: tcp type: none transport protocol: xtls OR tls
2, Can you snapshot your xray server configuration and upload the picture here? Of course you can hide the private information on picture.
And, if you can, please scrible your situation details more. for example, where your server locate? and, where your openwrt router locate ?
sometimes, geoip will cause this issue too.
@padima2
also, you should check geodata installed well. many factors can affect the success on openwrt xray. you can reinstall the geodata on your openwrt by:
$ opkg update && opkg install --force-reinstall xray-geodata
my thought is that xray doesnt send anything in my vless server but why?
According to your log it seems like a problem about referencing configurations in uci. Try these steps:
Xray servers
(just copy from your existing server settings)Main Server
(TCP Server
in new versions) and Tproxy UDP Server
(UDP Server
in new versions)@yichya @yukeiyang i ve tried -reinstall geodata, adding servers ,removing etc nothing has improved ,things got only got worse as i was loosing internet and sometimes the app was not responding when i use cmd to do so (i had to reboot) to get control back i ve used this script to setup my servers https://privacymelon.com/how-to-install-vless-xtls-xray-core/ but my config doesnt use nor tls nor xtls and it s working fine on phone and on pc server is located in europe i m in central asia. i dont know what else i can do to solve this
@padima2
so, What type of router you have?
x86-64?
no it s a linksys wrt 3200 acm
so, If I have time later, I will try to compile one firmware for your router, and integrate luci-app-xray in the firmware, If you need.
Give me your exact router type, If you need the firmware.
Sometimes, the firmware that's not made correctly will cause this issue too.
@yukeiyang this is the exact model https://openwrt.org/toh/linksys/wrt3200acm i ve taken the firmware from the official link and same for the xray core ,the luci app was taking from one guy who is compiling it you can find it here https://github.com/WuTr3YZd/luci-app-xray_build
Did you install luci-app-xray by ipk OR just install with firmware that's already integrated with luci-app-xray?
things got only got worse as i was loosing internet
So can you paste some logs here when you lost internet
That means you installed it by ipk.
this is the exact model
https://openwrt.org/toh/linksys/wrt3200acm
i ve taken the firmware from the official link and same for the xray core ,the luci app was taking from one guy who is compiling it you can find it here
https://github.com/WuTr3YZd/luci-app-xray_build
Did you install luci-app-xray by ipk OR just install with firmware that's already integrated with luci-app-xray?
i didnt find the firmware with luci-app integretad so the install was done by ipk with this guy s ipk https://github.com/WuTr3YZd/luci-app-xray_build
things got only got worse as i was loosing internet
So can you paste some logs here when you lost internet
it was when i added the second server ,the config was not read correctly by the app and it was blocking the internet , i didnt copy the logs , i ve just removed the second server and internet came back
I remember the best installation method should be installing with firmware integrated luci-app-xray yet, seems @yichya recommanded this method.
so you have to compile it yourself?
I remember the best installation method should be installing with firmware integrated luci-app-xray yet, Seems @yichya recommand this method.
Yes.
so you have to compile it yourself?
Actually, I have the same issue in the last installation with ipk.
After compiling firmware integrated luci-app-xray, It works.
Yes.
so you have to compile it yourself?
ok i ve never done it for openwrt , if you find me the right guide i ll give it a try
Actually, I have the same issue in the last installation with ipk.
After compiling firmware integrated luci-app-xray, It works.
aha so the ipk itself is not working
boz of the xray is one sort of new, it's one branch of v2ray in these 2 years, seems no complete guide for compiling.
but if you familiar with compiling openwrt firmware, you can do it yourself.
it was when i added the second server ,the config was not read correctly by the app and it was blocking the internet , i didnt copy the logs , i ve just removed the second server and internet came back
That means that Xray is working and trying to intercept your network traffic and the logs are quite important for figuring out what was happening.
aha so the ipk itself is not working
That is not expected and logs are also needed for diagnostics
@padima2
I compiled the firmware for you, and upload the firmware here: https://github.com/yukeiyang/openwrt-22-03-1-x86-64-and-linksys-wrt3200acm-firmware-with-luci-app-xray-integrated
@padima2
I compiled the firmware for you, and upload the firmware here: https://github.com/yukeiyang/openwrt-22-03-1-x86-64-and-linksys-wrt3200acm-firmware-with-luci-app-xray-integrated
i ve tried them but it has bricked my router. i ll need to find an usb ttl cable to restore the boot loader your firmware is not correct
Weird. I compiled several different firmwares including netgear 8000 router & miwifi router with same logic before, All work fine.
And, yesterday I compiled one more firmware for my x86 router, It works fine yet.
first, no need with ttl cable I am sure.
1, try any other lan port with cable line one by one. the port of x86 router switches to lan1 port after write new firmware, I am not sure there's one same issue or not in linksys-wrt3200acm.
2, access the ip: 192.168.1.1 by default.
3, set your pc ip as 192.168.1.2, run ping 192.168.1.1 -t
, then, press and hold RESET for 10 seconds to restart the router, when ping successfully, upload your firmware to /tmp of router with winscp. next, with putty or any other ssh tool to rewrite your router. seem like:
$ mtd -r write /tmp/openwrt-ar71xx-generic-tl-wdr4310-v1-squashfs-factory.bin firmware
@padima2 Which firmare you selected in the firmware folder?
openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-rootfs.tar.gz openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-factory.img openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-sysupgrade.bin
you should select openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-factory.img or openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-sysupgrade.bin.
If you select openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-rootfs.tar.gz, maybe has issues. I have not used tar.gz and tested tar.gz, I have tested squashfs-factory.img only before in the previous installation of some other routers.
@padima2 Which firmare you selected in the firmware folder?
openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-rootfs.tar.gz openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-factory.img openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-sysupgrade.bin
you should select openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-factory.img or openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-squashfs-sysupgrade.bin.
If you select openwrt-22.03.1-mvebu-cortexa9-linksys_wrt3200acm-rootfs.tar.gz, maybe has issues. I have not used tar.gz and tested tar.gz, I have tested squashfs-factory.img only before in the previous installation of some other routers.
i ve selected the factory one but the size of your firmware is not correct i have 213ko instead of 11/17 mb of siz of normal firmware.
there is two partitions on the wrt3200 acm , now the bootloader is broken so i can t boot to the right partition ,i need to restore it
@yukeiyang i ve recovered the bootloader andhave upgrade it to 22.031 do you have any link where i can find some detailed instruction to build the firmwware with luci-app-xray? thanks
@padima2 I wrote this for you. this is for x86-64, you can replace some values for your situation.
luci-app-xray ipk file compilation practice @Ubuntu 22.04
-- $ apt update && apt upgrade -y -- $ sudo apt-get install git-core build-essential libssl-dev libncurses5-dev unzip gawk asciidoc binutils bzip2 gettext git libz-dev patch python3.5 unzip subversion mercurial ccache sudo rsync screen -y
-- $ sudo adduser plus -- $ adduser plus sudo -- $ chmod 0440 /etc/sudoers -- $ reboot
-- $ su - plus
-- $ wget https://downloads.openwrt.org/releases/22.03.1/targets/x86/64/openwrt-sdk-22.03.1-x86-64_gcc-11.2.0_musl.Linux-x86_64.tar.xz
-- $ tar -xf openwrt-sdk-22.03.1-x86-64_gcc-11.2.0_musl.Linux-x86_64.tar.xz -- $ sudo apt-get update
-- $ cd openwrt-sdk-22.03.1-x86-64_gcc-11.2.0_musl.Linux-x86_64 -- $ git clone https://github.com/yichya/luci-app-xray.git package/luci-app-xray -- $ ./scripts/feeds update -a && ./scripts/feeds install -a -- $ make menuconfig // Extra ->
-- $ make package/luci-app-xray/compile V=99
and, I wrote one guide for you how to compile firmware with luci-app-xray integrated. this is for x86-64, you can replace some values for your situation.
first, you should copy the package folder that last step compied, copy to openwrt-imagebuilder-22.03.1-x86-64.Linux-x86_64 folder. then,
OpenWRT x86-64 Firmware firmware compilation @Ubuntu 22.04
-- $ su - plus -- $ cd && sudo apt-get update -- $ wget https://downloads.openwrt.org/releases/22.03.1/targets/x86/64/openwrt-imagebuilder-22.03.1-x86-64.Linux-x86_64.tar.xz -- $ tar -xf openwrt-imagebuilder-22.03.1-x86-64.tar.xz -- $ cd openwrt-imagebuilder-22.03.1-x86-64
-- $ make info // get profile name, replace PROFILE name in the next step with your router name: linksys-wrt3200acm
-- $ make image PROFILE=generic PACKAGES="luci uhttpd irqbalance xray-core luci-app-xray v2ray-geosite v2ray-geoip"
@yukeiyang i ve tried this and there is lot of errors so i dodnt think i have succeeded in making the ipk or the img for now i dont have any solution left
1, first you should use narmal user,not root. 2, you should replace PROFILE name as your router name: linksys-wrt3200acm, same as PROFILE=linksys-wrt3200acm 3, should select right values in "make menuconfig" for compiling ipk.
or, you can use anydesk.com tool, I can guide you.
hi yichya after several attempts, i succeeded in installing both xray and luci-app-xray. i think i have put the right settings in the luci-app but unfortunately i m not able to get connected after starting xray i m having only google page opening correctly but when i m trying to open one of the links (from the results of google search) i have errors saying this page doesnt have https and it doesnt open also my ip is not the ip of the xray server. is there any detailed instruction on how to get xray configured correctly on openwrt? thanks in advance and continue this amazing work both u and the people behind v2ray,xray ....