Cloudflare WARP on Enigma2 python3-based images
-
- E2Script
- pepsik
- Thread is marked as Resolved.
-
-
warp ip address.
The IP address is given automatically by CloudFlare, and it is the IP of the closest “node” to you. You cannot select it.
-
Attached is a test version
Hi, I'm trying it on ATV 7.5.1...
Code
Display Moreroot@vuzero4k:~# wireguard start Starting all configured Wireguard interfaces [#] echo 1 | tee /proc/sys/net/ipv4/ip_forward /proc/sys/net/ipv6/conf/all/disable_ipv6 > /dev/null [#] /etc/wireguard/cloudflare.sh up cloudflare RTNETLINK answers: File exists [#] ip link add cloudflare type wireguard [#] wg setconf cloudflare /dev/fd/63 [#] ip -4 address add 172.16.0.2/32 dev cloudflare [#] ip link set mtu 1420 up dev cloudflare [#] resolvconf -a cloudflare -m 0 -x [#] ip -4 route add 128.0.0.0/1 dev cloudflare [#] ip -4 route add 0.0.0.0/1 dev cloudflare [#] wg set cloudflare private-key /etc/wireguard/cloudflare.key Invalid length key in key file [#] resolvconf -d cloudflare -f [#] ip link delete dev cloudflarerootAny ideas?
-
Any ideas?
Invalid length key in key file
The answer is in the log you provided. It's not about the image. You have some kind of problem with the key. Regenerate it.
-
The answer is in the log you provided. It's not about the image. You have some kind of problem with the key. Regenerate it.
I downloaded the package from post #68, installed it. I didn't do anything else.
key must be obtained in some way or is it automatically generated?
-
-
I installed the plugin and it's not working on ATV 7.6. Any help?
-
I installed the plugin and it's not working on ATV 7.6. Any help?
Any logs? Screenshots? How can I tell that it's not working for you? Maybe you need to replace the batteries in the remote control?
-
-
Could not resolve host: ip-api.com
This is a question for your internet service provider; its DNS servers cannot resolve this hostname.
-
-
Thanks for the help.
what am I doing wrong, how can I fix it?
Code
Display Moreroot@h9combo:~# /etc/init.d/wireguard.sh start Starting all configured Wireguard interfaces [#] echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 [#] /etc/wireguard/cloudflare.sh up cloudflare ip: RTNETLINK answers: File exists [#] ip link add cloudflare type wireguard [#] wg setconf cloudflare /dev/fd/63 [#] ip -4 address add 172.16.0.2/32 dev cloudflare [#] ip link set mtu 1420 up dev cloudflare [#] resolvconf -a cloudflare -m 0 -x [#] ip -4 route add 128.0.0.0/1 dev cloudflare [#] ip -4 route add 0.0.0.0/1 dev cloudflare [#] wg set cloudflare private-key /etc/wireguard/cloudflare.key fopen: No such file or directory [#] resolvconf -d cloudflare -f [#] ip link delete dev cloudflare root@h9combo:~#Code
Display Moreroot@h9combo:~# curl -4 ip-api.com { "status" : "success", "continent" : "Europe", "continentCode": "EU", "country" : "Russia", "countryCode" : "RU", "region" : "TA", "regionName" : "Tatarstan Republic", "city" : "Kazan'", "district" : "", "zip" : "422528", "lat" : 55.785, "lon" : 49.1178, "timezone" : "Europe/Moscow", "offset" : 10800, "currency" : "RUB", "isp" : "CJSC \"ER-Telecom Holding\" Kazan' branch", "org" : "JSC \"ER-Telecom Holding\" Kazan' Branch", "as" : "AS41668 JSC \"ER-Telecom Holding\"", "asname" : "ERTH-KAZAN-AS", "mobile" : false, "proxy" : false, "hosting" : false, "query" : "xxx.xxx.xxx.xxx" } root@h9combo:~#I accidentally deleted /etc/wireguard/wg0.conf and now I don't have a connection to cloudflare.
-
I accidentally deleted /etc/wireguard/wg0.conf and now I don't have a connection to cloudflare.
Reinstall the utility again using the --force-reinstall option; this will rewrite all files and dependencies.
-
reinstalled with the --force-reinstall option, but wg0.conf is not being created
Code
Display Moreroot@h9combo:~# wireguard start Starting all configured Wireguard interfaces [#] echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 [#] /etc/wireguard/cloudflare.sh up cloudflare [#] ip link add cloudflare type wireguard [#] wg setconf cloudflare /dev/fd/63 [#] ip -4 address add 172.16.0.2/32 dev cloudflare [#] ip link set mtu 1420 up dev cloudflare [#] resolvconf -a cloudflare -m 0 -x [#] ip -4 route add 128.0.0.0/1 dev cloudflare [#] ip -4 route add 0.0.0.0/1 dev cloudflare [#] wg set cloudflare private-key /etc/wireguard/cloudflare.key Invalid length key in key file [#] resolvconf -d cloudflare -f [#] ip link delete dev cloudflare root@h9combo:~# curl -4 ip-api.com { "status" : "success", "continent" : "Europe", "continentCode": "EU", "country" : "Russia", "countryCode" : "RU", "region" : "TA", "regionName" : "Tatarstan Republic", "city" : "Kazan'", "district" : "", "zip" : "422528", "lat" : 55.785, "lon" : 49.1178, "timezone" : "Europe/Moscow", "offset" : 10800, "currency" : "RUB", "isp" : "CJSC \"ER-Telecom Holding\" Kazan' branch", "org" : "JSC \"ER-Telecom Holding\" Kazan' Branch", "as" : "AS41668 JSC \"ER-Telecom Holding\"", "asname" : "ERTH-KAZAN-AS", "mobile" : false, "proxy" : false, "hosting" : false, "query" : "xxx.xxx.xxx.xxx" } root@h9combo:~# wg-quick up wg0 wg-quick: `/etc/wireguard/wg0.conf' does not exist root@h9combo:~# -
wg-quick: `/etc/wireguard/wg0.conf' does not exist
Check to see if this file has been created on your end
-
there are three files cloudflare.conf, cloudflare.key and cloudflare.sh
for some reason, wg0.conf does not want to be created
-
root@h9combo:~# wg-quick up wg0
wg0.conf does not want to be created
But you specify that configuration file yourself when you start WireGuard...
-
shouldn't all the necessary files be created automatically after starting wireguard start?
Or is there something I don't fully understand?
-
files be created automatically
Of course, these are created automatically, and you listed them above in the chat. If you're starting WireGuard directly (not via a script), then you should use the configuration file that was created automatically.... But you’re starting WireGuard (in the log you provided) with your own config, yet you don’t have that file... What do you expect?
-
Thanks for the clarifications, now I understand.
I have commented on the configuration of the wg, but it is not possible to get the IP Cloudflare
Code
Display Moreroot@h9combo:~# wireguard start Starting all configured Wireguard interfaces wg-quick: `#wg0' does not exist [#] echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 [#] /etc/wireguard/cloudflare.sh up cloudflare [#] ip link add cloudflare type wireguard [#] wg setconf cloudflare /dev/fd/63 [#] ip -4 address add 172.16.0.2/32 dev cloudflare [#] ip link set mtu 1420 up dev cloudflare [#] resolvconf -a cloudflare -m 0 -x [#] ip -4 route add 128.0.0.0/1 dev cloudflare [#] ip -4 route add 0.0.0.0/1 dev cloudflare [#] wg set cloudflare private-key /etc/wireguard/cloudflare.key Invalid length key in key file [#] resolvconf -d cloudflare -f [#] ip link delete dev cloudflare root@h9combo:~# curl -4 ip-api.com { "status" : "success", "continent" : "Europe", "continentCode": "EU", "country" : "Russia", "countryCode" : "RU", "region" : "TA", "regionName" : "Tatarstan Republic", "city" : "Kazan'", "district" : "", "zip" : "422528", "lat" : 55.785, "lon" : 49.1178, "timezone" : "Europe/Moscow", "offset" : 10800, "currency" : "RUB", "isp" : "CJSC \"ER-Telecom Holding\" Kazan' branch", "org" : "JSC \"ER-Telecom Holding\" Kazan' Branch", "as" : "AS41668 JSC \"ER-Telecom Holding\"", "asname" : "ERTH-KAZAN-AS", "mobile" : false, "proxy" : false, "hosting" : false, "query" : "xxx.xxx.xxx.xxx" } root@h9combo:~# -
[#] wg set cloudflare private-key /etc/wireguard/cloudflare.key Invalid length key in key file
It seems the configuration file has been edited, or the key generation algorithm has changed. I'll check this evening to see if there have been any changes to the key generation process.
-
Cloudflare WARP by use free vpn with WireGuard for some blocked countries