very strange as ip as i test on the morning is work successfully for stb ip
and now it work by router ip !!!
very strange as ip as i test on the morning is work successfully for stb ip
and now it work by router ip !!!
very strange as ip as i test on the morning is work successfully for stb ip
and now it work by router ip !!!
You still have real ip address, do you receive CloudFlare ip after executing the wireguard.sh script ?
and now it work by router ip
According to the screenshot you also have a connection error ... and that's why it doesn't work ....
I wrote above and gave the exact same log with the exact same error. Maybe it has something to do with using OSCAM... I don't have anything to test OSCAM I don't have a dish I only watch IPTV.
According to the screenshot you also have a connection error ... and that's why it doesn't work ....
I wrote above and gave the exact same log with the exact same error. Maybe it has something to do with using OSCAM... I don't have anything to test OSCAM I don't have a dish I only watch IPTV.
i don't understand the relation with oscam, i stopped all emus
as log give success as not connected to cloud flair server
You still have real ip address, do you receive CloudFlare ip after executing the wireguard.sh script ?
still have real ip address !
as log give success as not connected to cloud flair server
Look carefully at your log ... where do you see what you are writing about ? You have an "ip route" error in your log.
RTNETLINK answers: File exists
You still have real ip address, do you receive CloudFlare ip after executing the wireguard.sh script ?
still have real ip address !
So VPN service not started .
You have an "ip route" error in your log.
try
opkg install iproute2
root@vuzero4k:~# opkg install iproute2
Package iproute2 (6.7.0-r0) installed in root is up to date.
Quoteroot@novaler4kpro:~# opkg install iproute2
Package iproute2 (6.2.0-r0) installed in root is up to date.
root@vuzero4k:~# /etc/init.d/wireguard.sh start
Starting all configured Wireguard interfaces
[#] ip link add wgcf-profile type wireguard
[#] wg setconf wgcf-profile /dev/fd/63
[#] ip -4 address add 172.16.0.2/24 dev wgcf-profile
[#] ip link set mtu 1420 up dev wgcf-profile
[#] resolvconf -a wgcf-profile -m 0 -x
[#] ip -4 route add 128.0.0.0/1 dev wgcf-profile
[#] ip -4 route add 0.0.0.0/1 dev wgcf-profile
[#] ip route add 162.159.192.1 via 192.168.1.1
RTNETLINK answers: File exists
[#] resolvconf -d wgcf-profile -f
[#] ip link delete dev wgcf-profile
Display More
I don't have an answer
p.s. The last attempt ... try to change the domain name to its IP
[Interface]
PrivateKey = <PRIVATE KEY>
Address = 172.16.0.2/24
DNS = 1.1.1.1, 1.0.0.1
MTU = 1420
PostUp = ip route add 162.159.192.1 via 192.168.88.1
PostDown = ip route del 162.159.192.1 via 192.168.88.1
[Peer]
PublicKey = <PUBLIC KEY>
AllowedIps = 0.0.0.0/1, 128.0.0.0/1
Endpoint = 162.159.192.1:2408
PersistentKeepalive = 25
Display More
I don't have an answer
p.s. The last attempt ... try to change the domain name to its IP
CodeDisplay More[Interface] PrivateKey = <PRIVATE KEY> Address = 172.16.0.2/24 DNS = 1.1.1.1, 1.0.0.1 MTU = 1420 PostUp = ip route add 162.159.192.1 via 192.168.88.1 PostDown = ip route del 162.159.192.1 via 192.168.88.1 [Peer] PublicKey = <PUBLIC KEY> AllowedIps = 0.0.0.0/1, 128.0.0.0/1 Endpoint = 162.159.192.1:2408 PersistentKeepalive = 25
root@vuzero4k:~# /etc/init.d/wireguard.sh start
Starting all configured Wireguard interfaces
[#] ip link add wgcf-profile type wireguard
[#] wg setconf wgcf-profile /dev/fd/63
[#] ip -4 address add 172.16.0.2/24 dev wgcf-profile
[#] ip link set mtu 1420 up dev wgcf-profile
[#] resolvconf -a wgcf-profile -m 0 -x
[#] ip -4 route add 128.0.0.0/1 dev wgcf-profile
[#] ip -4 route add 0.0.0.0/1 dev wgcf-profile
[#] ip route add 162.159.192.1 via 192.168.1.1
RTNETLINK answers: File exists
[#] resolvconf -d wgcf-profile -f
[#] ip link delete dev wgcf-profile
root@vuzero4k:~#
Display More
QuoteDisplay More[Interface]
PrivateKey = XXXXX
Address = 172.16.0.2/24
DNS = 1.1.1.1
MTU = 1480
PostUp = ip route add 162.159.192.1 via 192.168.1.1
PostDown = ip route del 162.159.192.1 via 192.168.1.1
[Peer]
PublicKey = XXXXX
AllowedIps = 0.0.0.0/1, 128.0.0.0/1
Endpoint = engage.cloudflareclient.com:2408
#PersistentKeepalive = 25
QuoteDisplay Moreroot@novaler4kpro:~# /etc/init.d/wireguard.sh start
Starting all configured Wireguard interfaces
[#] ip link add wgcf-profile type wireguard
[#] wg setconf wgcf-profile /dev/fd/63
[#] ip -4 address add 172.16.0.2/24 dev wgcf-profile
[#] ip link set mtu 1480 up dev wgcf-profile
[#] resolvconf -a wgcf-profile -m 0 -x
[#] ip -4 route add 128.0.0.0/1 dev wgcf-profile
[#] ip -4 route add 0.0.0.0/1 dev wgcf-profile
[#] ip route add 162.159.192.1 via 192.168.1.1
Still stucking with this command
Quoteroot@novaler4kpro:~# curl -4 ip-api.com
I don't have an answer
p.s. The last attempt ... try to change the domain name to its IP
CodeDisplay More[Interface] PrivateKey = <PRIVATE KEY> Address = 172.16.0.2/24 DNS = 1.1.1.1, 1.0.0.1 MTU = 1420 PostUp = ip route add 162.159.192.1 via 192.168.88.1 PostDown = ip route del 162.159.192.1 via 192.168.88.1 [Peer] PublicKey = <PUBLIC KEY> AllowedIps = 0.0.0.0/1, 128.0.0.0/1 Endpoint = 162.159.192.1:2408 PersistentKeepalive = 25
QuoteDisplay More[Interface]
PrivateKey = 0BOVo/Hzj+bDrQqpp3UyeenR8a3RHLXBwd6mTe8/KFg=
Address = 172.16.0.2/24
DNS = 1.1.1.1
MTU = 1480
PostUp = ip route add 162.159.192.1 via 192.168.1.1
PostDown = ip route del 162.159.192.1 via 192.168.1.1
[Peer]
PublicKey = bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=
AllowedIps = 0.0.0.0/1, 128.0.0.0/1
Endpoint = 162.159.192.1:2408
#PersistentKeepalive = 25
QuoteDisplay Moreroot@novaler4kpro:~# /etc/init.d/wireguard.sh stop
Stopping all active Wireguard interfaces
[#] ip link delete dev wgcf-profile
[#] resolvconf -d wgcf-profile -f
[#] ip route del 162.159.192.1 via 192.168.1.1
root@novaler4kpro:~# /etc/init.d/wireguard.sh start
Starting all configured Wireguard interfaces
[#] ip link add wgcf-profile type wireguard
[#] wg setconf wgcf-profile /dev/fd/63
[#] ip -4 address add 172.16.0.2/24 dev wgcf-profile
[#] ip link set mtu 1480 up dev wgcf-profile
[#] resolvconf -a wgcf-profile -m 0 -x
[#] ip -4 route add 128.0.0.0/1 dev wgcf-profile
[#] ip -4 route add 0.0.0.0/1 dev wgcf-profile
[#] ip route add 162.159.192.1 via 192.168.1.1
root@novaler4kpro:~# curl -4 ip-api.com
curl: (28) Failed to connect to ip-api.com port 80 after 127272 ms: Couldn't connect to server
root@novaler4kpro:~#
Display More
root@novaler4kpro:~# /etc/init.d/wireguard.sh stop
Stopping all active Wireguard interfaces
[#] ip link delete dev wgcf-profile
[#] resolvconf -d wgcf-profile -f
[#] ip route del 162.159.192.1 via 192.168.1.1
root@novaler4kpro:~# /etc/init.d/wireguard.sh start
Starting all configured Wireguard interfaces
[#] ip link add wgcf-profile type wireguard
[#] wg setconf wgcf-profile /dev/fd/63
[#] ip -4 address add 172.16.0.2/24 dev wgcf-profile
[#] ip link set mtu 1480 up dev wgcf-profile
[#] resolvconf -a wgcf-profile -m 0 -x
[#] ip -4 route add 128.0.0.0/1 dev wgcf-profile
[#] ip -4 route add 0.0.0.0/1 dev wgcf-profile
[#] ip route add 162.159.192.1 via 192.168.1.1
root@novaler4kpro:~# curl -4 ip-api.com
curl: (28) Failed to connect to ip-api.com port 80 after 127272 ms: Couldn't connect to server
root@novaler4kpro:~#
Must change [#] ip link set mtu 1480 up dev wgcf-profile to 1420
UPDATE
1.0
The CloudflareWARP VPN installation package has been added to the first post and the installation instructions have been modified. Now it is enough to install the package and specify your private key. Scripts for VPN are written universally and will automatically work with any type of connection (wired or wifi) of your Enigma2 receiver. All necessary parameters of connection are formed automatically and do not require you any actions on editing any scripts
p.s. If you have previously created your configuration files manually, delete them from the /etc/wireguard folder before installing the ipk-package
Which one compitiable with VU Solo se
Mipsel stb?
Which one compitiable with VU Solo se
Mipsel stb?
Neither the architecture of the processor (arm, mipsle), nor the model of the receiver - does not matter ... The main thing is that the image has the necessary dependencies for wireguard
execute the command in the console and see the output
And you'll see if there are the right dependencies in your image
Don’t have an account yet? Register yourself now and be a part of our community!