Use openvpn of Cyberghost on Openwrt

Ho guys,
I've installed, Orange Pi R1 Plus LTS, openwrt 23.05.2 and I whatched this video for configure my router with Cyberghost vpn

I upload my OVPN configuration, edit it and inser Username an pwd on file .auth but, when I click start on the connection, doesn't start. I upload the file

"ca ca.crt"

"cert client.crt"

"key client.key"

By FPT in the same folder of the file ".ovpn" and ".auth" and the service stars BUT I cant navigate, the system doesn't ping google for example.
What can I do?
Thanks

If you are having to upload .crt and .key files, you have to specify the path to where you placed the files too (eg. /etc/openvpn/ca.crt) within the uploaded .ovpn file too. This applies also to the .auth file.

ie. click the 'Edit' button for the VPN instance and look for ca.crt for example, and add the path in front of it.

eg.

ca /etc/openvpn/ca.crt

The instructions in the Youtube link you provided are too simplified and may not work with some VPN providers. Please refer to:
https://openwrt.org/docs/guide-user/services/vpn/openvpn/client-luci

my configurtion is

client
remote 87-1-it.cg-dialup.net 443
dev tun
proto udp
auth-user-pass /etc/openvpn/VPN.auth

resolv-retry infinite
redirect-gateway def1
persist-key
persist-tun
nobind
cipher AES-256-CBC
ncp-disable
auth SHA256
ping 5
ping-exit 60
ping-timer-rem
explicit-exit-notify 2
script-security 2
remote-cert-tls server
route-delay 5
verb 4

ca /etc/openvpn/ca.crt

cert /etc/openvpn/client.crt

key /etc/openvpn/client.key

But always the same thing, start but no navigation. WHY??? :cry:

If the VPN instance starts, then it may be a DNS and/or firewall issue.

Can you ping 8.8.8.8 and www.google.com, using LuCI > Network > Diagnostics? (assuming Cyberghost does not block ping)
https://openwrt.org/docs/guide-user/services/vpn/openvpn/client-luci#troubleshooting

Is the orange PI the same device you use as your ISP connected router?

add to the openvpn config:
verb 5

Restart the router and post output of:
logread | grep -i openvpn

Thanks,
when I'm following the guide but I've some problem, this is my firewall zone settings

This is the image of the guide

I haven't th "tun0", what I must do??

Add to the /etc/config/network:

config interface 'tun0'
  option proto 'none'
  option device 'tun0'

Reboot afterwards

But the fact that the device is not present point to the fact that the tunnel is not started

I add the 'tun0' and do all the guide, but whe I activate the VPN always the same thing, no ping and no navigation like the image

But change the IP from 64.226.122.113 to 192.168.1.1

WHY???

Is the orange PI the same device you use for internet access, or is Orange PI connected to LAN port of separate ISP connected router?

can you provide last 20 openvpn messages shown in System log from LuCI? (@egc has made a similar request)

1 Like

The Orange PI connected to LAN port on a router of the ISP.

What is the IP address on the WAN port of the Orange PI (connected to LAN port of ISP router)?
What is the LAN IP address of the Orange PI ?

The Ip lan of the Orange pi is "192.168.1.1", the ip of the wan is "192.168.112.75"

can you provide last 20 openvpn messages shown in System log from LuCI > Status > System Log ? (@egc has made a similar request)

Fri Feb 2 13:53:43 2024 daemon.notice netifd: Interface 'OpenVPN' has link connectivity
Fri Feb 2 13:53:43 2024 daemon.notice netifd: Interface 'tun0' is now up
Fri Feb 2 13:53:48 2024 daemon.notice openvpn(VPN)[3126]: net_route_v4_add: 84.239.54.56/32 via 192.168.112.254 dev [NULL] table 0 metric -1
Fri Feb 2 13:53:48 2024 daemon.notice openvpn(VPN)[3126]: net_route_v4_add: 0.0.0.0/1 via 10.86.4.1 dev [NULL] table 0 metric -1
Fri Feb 2 13:53:48 2024 daemon.notice openvpn(VPN)[3126]: net_route_v4_add: 128.0.0.0/1 via 10.86.4.1 dev [NULL] table 0 metric -1
Fri Feb 2 13:53:48 2024 daemon.notice openvpn(VPN)[3126]: WARNING: OpenVPN was configured to add an IPv6 route. However, no IPv6 has been configured for tun0, therefore the route installation may fail or may not work as expected.
Fri Feb 2 13:53:48 2024 daemon.notice openvpn(VPN)[3126]: add_route_ipv6(2000::/3 -> :: metric -1) dev tun0
Fri Feb 2 13:53:48 2024 daemon.notice openvpn(VPN)[3126]: net_route_v6_add: 2000::/3 via :: dev tun0 table 0 metric -1
Fri Feb 2 13:53:48 2024 daemon.notice openvpn(VPN)[3126]: Initialization Sequence Completed
Fri Feb 2 13:55:21 2024 daemon.warn odhcpd[950]: No default route present, overriding ra_lifetime!
Fri Feb 2 13:56:12 2024 daemon.err openvpn(VPN)[3126]: event_wait : Interrupted system call (code=4)
Fri Feb 2 13:56:12 2024 daemon.notice openvpn(VPN)[3126]: SIGTERM received, sending exit notification to peer
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: TCP/UDP: Closing socket
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: /usr/libexec/openvpn-hotplug route-pre-down VPN tun0 1500 1624 10.86.4.191 255.255.255.0 init
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: net_route_v4_del: 84.239.54.56/32 via 192.168.112.254 dev [NULL] table 0 metric -1
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: net_route_v4_del: 0.0.0.0/1 via 10.86.4.1 dev [NULL] table 0 metric -1
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: net_route_v4_del: 128.0.0.0/1 via 10.86.4.1 dev [NULL] table 0 metric -1
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: delete_route_ipv6(2000::/3)
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: net_route_v6_del: 2000::/3 via :: dev tun0 table 0 metric -1
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: Closing TUN/TAP interface
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: net_addr_v4_del: 10.86.4.191 dev tun0
Fri Feb 2 13:56:14 2024 daemon.notice netifd: Network device 'tun0' link is down
Fri Feb 2 13:56:14 2024 daemon.notice netifd: Network alias 'tun0' link is down
Fri Feb 2 13:56:14 2024 daemon.notice netifd: Interface 'OpenVPN' has link connectivity loss
Fri Feb 2 13:56:14 2024 daemon.notice netifd: Interface 'tun0' has link connectivity loss
Fri Feb 2 13:56:14 2024 daemon.notice netifd: Interface 'tun0' is now down
Fri Feb 2 13:56:14 2024 daemon.notice netifd: Interface 'tun0' is disabled
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: /usr/libexec/openvpn-hotplug down VPN tun0 1500 1624 10.86.4.191 255.255.255.0 init
Fri Feb 2 13:56:14 2024 daemon.notice openvpn(VPN)[3126]: SIGTERM[soft,exit-with-notification] received, process exiting
Fri Feb 2 13:59:26 2024 daemon.warn odhcpd[950]: No default route present, overriding ra_lifetime!

Add the following to the OpenVPN config:

verb 5
# to block IPv6 traffic necessary on newer clients
pull-filter ignore "route-ipv6"
pull-filter ignore "ifconfig-ipv6"
block-ipv6

Save and Apply and reboot the router and then show again the openvpn log:
logread | grep -i openvpn

1 Like

Further to @egc suggestion, you may wish to delete the 'wan6' interface in Luci > Network > Interfaces menu.

root@OpenWrt:~# logread | grep -i openvpn
Fri Feb 2 14:22:21 2024 daemon.warn openvpn(VPN)[1509]: DEPRECATED OPTION: ncp- disable. Disabling cipher negotiation is a deprecated debug feature that will be removed in OpenVPN 2.6
Fri Feb 2 14:22:21 2024 daemon.warn openvpn(VPN)[1509]: DEPRECATED OPTION: --ci pher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM ). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES -256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-f allback 'AES-256-CBC' to silence this warning.
Fri Feb 2 14:22:21 2024 daemon.notice openvpn(VPN)[1509]: OpenVPN 2.5.8 aarch64 -openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
Fri Feb 2 14:22:21 2024 daemon.notice openvpn(VPN)[1509]: library versions: Ope nSSL 3.0.12 24 Oct 2023, LZO 2.10
Fri Feb 2 14:22:21 2024 daemon.warn openvpn(VPN)[1509]: NOTE: the current --scr ipt-security setting may allow this configuration to call user-defined scripts
Fri Feb 2 14:22:21 2024 daemon.notice openvpn(VPN)[1509]: Control Channel MTU p arms [ L:1621 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Fri Feb 2 14:22:26 2024 daemon.err openvpn(VPN)[1509]: RESOLVE: Cannot resolve host address: 87-1-it.cg-dialup.net:443 (Try again)
Fri Feb 2 14:22:26 2024 daemon.notice openvpn(VPN)[1509]: Data Channel MTU parm s [ L:1621 D:1450 EF:121 EB:406 ET:0 EL:3 ]
Fri Feb 2 14:22:26 2024 daemon.notice openvpn(VPN)[1509]: Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,cipher AES-256 -CBC,auth SHA256,keysize 256,key-method 2,tls-client'
Fri Feb 2 14:22:26 2024 daemon.notice openvpn(VPN)[1509]: Expected Remote Optio ns String (VER=V4): 'V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,ciph er AES-256-CBC,auth SHA256,keysize 256,key-method 2,tls-server'
Fri Feb 2 14:22:31 2024 daemon.err openvpn(VPN)[1509]: RESOLVE: Cannot resolve host address: 87-1-it.cg-dialup.net:443 (Try again)
Fri Feb 2 14:22:31 2024 daemon.warn openvpn(VPN)[1509]: Could not determine IPv 4/IPv6 protocol
Fri Feb 2 14:22:31 2024 daemon.notice openvpn(VPN)[1509]: SIGUSR1[soft,init_ins tance] received, process restarting
Fri Feb 2 14:22:31 2024 daemon.notice openvpn(VPN)[1509]: Restart pause, 5 seco nd(s)
Fri Feb 2 14:22:37 2024 daemon.warn openvpn(VPN)[1509]: NOTE: the current --scr ipt-security setting may allow this configuration to call user-defined scripts
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Re-using SSL/TLS cont ext
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Control Channel MTU p arms [ L:1621 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Data Channel MTU parm s [ L:1621 D:1450 EF:121 EB:406 ET:0 EL:3 ]
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,cipher AES-256 -CBC,auth SHA256,keysize 256,key-method 2,tls-client'
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Expected Remote Optio ns String (VER=V4): 'V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,ciph er AES-256-CBC,auth SHA256,keysize 256,key-method 2,tls-server'
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: TCP/UDP: Preserving r ecently used remote address: [AF_INET]185.217.71.142:443
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Socket Buffers: R=[21 2992->212992] S=[212992->212992]
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: UDP link local: (not bound)
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: UDP link remote: [AF_ INET]185.217.71.142:443
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: TLS: Initial packet f rom [AF_INET]185.217.71.142:443, sid=e883e9af 478529be
Fri Feb 2 14:22:37 2024 daemon.warn openvpn(VPN)[1509]: WARNING: this configura tion may cache passwords in memory -- use the auth-nocache option to prevent thi s
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: VERIFY OK: depth=1, C =RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, emailAddress=info@cy berghost.ro
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: VERIFY KU OK
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Validating certificat e extended key usage
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: ++ Certificate has EK U (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: VERIFY EKU OK
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: VERIFY OK: depth=0, C N=rome-rack401.nodes.gen4.ninja
Fri Feb 2 14:22:37 2024 daemon.warn openvpn(VPN)[1509]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1569', remote='link-mtu 1553'
Fri Feb 2 14:22:37 2024 daemon.warn openvpn(VPN)[1509]: WARNING: 'keysize' is u sed inconsistently, local='keysize 256', remote='keysize 128'
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Control Channel: TLSv 1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, sign ature: RSA-SHA256
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: [rome-rack401.nodes.g en4.ninja] Peer Connection Initiated with [AF_INET]185.217.71.142:443
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: PUSH: Received contro l message: 'PUSH_REPLY,redirect-gateway def1,route-ipv6 2000::/3,dhcp-option DNS 10.0.0.243,route-gateway 10.12.4.1,topology subnet,ping 10,ping-restart 60,ifco nfig 10.12.4.42 255.255.255.0,peer-id 12'
Fri Feb 2 14:22:37 2024 daemon.warn openvpn(VPN)[1509]: WARNING: You have speci fied redirect-gateway and redirect-private at the same time (or the same option multiple times). This is not well supported and may lead to unexpected results
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Pushed option removed by filter: 'route-ipv6 2000::/3'
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: OPTIONS IMPORT: timer s and/or timeouts modified
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: OPTIONS IMPORT: --ifc onfig/up options modified
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: OPTIONS IMPORT: route options modified
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: OPTIONS IMPORT: route -related options modified
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: OPTIONS IMPORT: --ip- win32 and/or --dhcp-option options modified
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: OPTIONS IMPORT: peer- id set
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: OPTIONS IMPORT: adjus ting link_mtu to 1624
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Outgoing Data Channel : Cipher 'AES-256-CBC' initialized with 256 bit key
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Outgoing Data Channel : Using 256 bit message hash 'SHA256' for HMAC authentication
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Incoming Data Channel : Cipher 'AES-256-CBC' initialized with 256 bit key
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: Incoming Data Channel : Using 256 bit message hash 'SHA256' for HMAC authentication
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: net_route_v4_best_gw query: dst 0.0.0.0
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: net_route_v4_best_gw result: via 192.168.112.254 dev eth0
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: TUN/TAP device tun0 o pened
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: do_ifconfig, ipv4=1, ipv6=0
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: net_iface_mtu_set: mt u 1500 for tun0
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: net_iface_up: set tun 0 up
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: net_addr_v4_add: 10.1 2.4.42/24 dev tun0
Fri Feb 2 14:22:37 2024 daemon.notice openvpn(VPN)[1509]: /usr/libexec/openvpn- hotplug up VPN tun0 1500 1624 10.12.4.42 255.255.255.0 init
Fri Feb 2 14:22:37 2024 daemon.notice netifd: Interface 'OpenVPN' is enabled
Fri Feb 2 14:22:37 2024 daemon.notice netifd: Interface 'OpenVPN' has link conn ectivity
Fri Feb 2 14:22:42 2024 daemon.notice openvpn(VPN)[1509]: net_route_v4_add: 185 .217.71.142/32 via 192.168.112.254 dev [NULL] table 0 metric -1
Fri Feb 2 14:22:42 2024 daemon.notice openvpn(VPN)[1509]: net_route_v4_add: 0.0 .0.0/1 via 10.12.4.1 dev [NULL] table 0 metric -1
Fri Feb 2 14:22:42 2024 daemon.notice openvpn(VPN)[1509]: net_route_v4_add: 128 .0.0.0/1 via 10.12.4.1 dev [NULL] table 0 metric -1
Fri Feb 2 14:22:42 2024 daemon.notice openvpn(VPN)[1509]: Initialization Sequen ce Completed

A lot of warnings because there is garbage and outdated settings in your config but you seem to have a connection:

So lets see:

ifconfig
ip route show
ip route show table all
ip rule show

Edit:
with traceroute 8.8.8.8 and curl ipinfo.io you can see if you are connected and routed accordingly

But then 3 minutes later, this happens:

which is followed by a teardown of OpenVPN. So OpenVPN does connect but then it crashes. This is evident from pings through the tunnel being successful for a time, then stopping.

"interrupted system call" doesn't say much but clearly it is some sort of internal fault. The certificates, routes, firewall, etc. are all OK.

ifconfig

root@OpenWrt:~# ifconfig
br-lan Link encap:Ethernet HWaddr C0:74:2B:FF:54:F5
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::c274:2bff:feff:54f5/64 Scope:Link
inet6 addr: fd59:8ba8:52ff::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9048 errors:0 dropped:0 overruns:0 frame:0
TX packets:9132 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1654705 (1.5 MiB) TX bytes:4408720 (4.2 MiB)

eth0 Link encap:Ethernet HWaddr C0:74:2B:FF:54:F4
inet addr:192.168.112.75 Bcast:192.168.112.255 Mask:255.255.255.0
inet6 addr: fe80::c274:2bff:feff:54f4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6119 errors:0 dropped:0 overruns:0 frame:0
TX packets:3597 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4285914 (4.0 MiB) TX bytes:862218 (842.0 KiB)
Interrupt:35

eth1 Link encap:Ethernet HWaddr C0:74:2B:FF:54:F5
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9270 errors:0 dropped:4 overruns:0 frame:0
TX packets:9570 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1663625 (1.5 MiB) TX bytes:4408500 (4.2 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:102 errors:0 dropped:0 overruns:0 frame:0
TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9602 (9.3 KiB) TX bytes:9602 (9.3 KiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 -00
inet addr:10.84.4.182 P-t-P:10.84.4.182 Mask:255.255.255.0
inet6 addr: fe80::dca9:8c88:db72:ccbc/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:217 errors:0 dropped:0 overruns:0 frame:0
TX packets:635 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:36460 (35.6 KiB) TX bytes:37691 (36.8 KiB)

ip route show

root@OpenWrt:~# ip route show
0.0.0.0/1 via 10.84.4.1 dev tun0
default via 192.168.112.254 dev eth0 src 192.168.112.75
10.84.4.0/24 dev tun0 scope link src 10.84.4.182
84.239.54.54 via 192.168.112.254 dev eth0
128.0.0.0/1 via 10.84.4.1 dev tun0
192.168.1.0/24 dev br-lan scope link src 192.168.1.1
192.168.112.0/24 dev eth0 scope link src 192.168.112.75
root@OpenWrt:~#

root@OpenWrt:~# ip route show
0.0.0.0/1 via 10.84.4.1 dev tun0
default via 192.168.112.254 dev eth0 src 192.168.112.75
10.84.4.0/24 dev tun0 scope link src 10.84.4.182
84.239.54.54 via 192.168.112.254 dev eth0
128.0.0.0/1 via 10.84.4.1 dev tun0
192.168.1.0/24 dev br-lan scope link src 192.168.1.1
192.168.112.0/24 dev eth0 scope link src 192.168.112.75
root@OpenWrt:~# ^C

ip route show table all

root@OpenWrt:~# ip route show table all
0.0.0.0/1 via 10.84.4.1 dev tun0
default via 192.168.112.254 dev eth0 src 192.168.112.75
10.84.4.0/24 dev tun0 scope link src 10.84.4.182
84.239.54.54 via 192.168.112.254 dev eth0
128.0.0.0/1 via 10.84.4.1 dev tun0
192.168.1.0/24 dev br-lan scope link src 192.168.1.1
192.168.112.0/24 dev eth0 scope link src 192.168.112.75
local 10.84.4.182 dev tun0 table local scope host src 10.84.4.182
broadcast 10.84.4.255 dev tun0 table local scope link src 10.84.4.182
local 127.0.0.0/8 dev lo table local scope host src 127.0.0.1
local 127.0.0.1 dev lo table local scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local scope link src 127.0.0.1
local 192.168.1.1 dev br-lan table local scope host src 192.168.1.1
broadcast 192.168.1.255 dev br-lan table local scope link src 192.168.1.1
local 192.168.112.75 dev eth0 table local scope host src 192.168.112.75
broadcast 192.168.112.255 dev eth0 table local scope link src 192.168.112.75
fd59:8ba8:52ff::/64 dev br-lan metric 1024
unreachable fd59:8ba8:52ff::/48 dev lo metric 2147483647
fe80::/64 dev eth0 metric 256
fe80::/64 dev br-lan metric 256
fe80::/64 dev tun0 metric 256
local ::1 dev lo table local metric 0
anycast fd59:8ba8:52ff:: dev br-lan table local metric 0
local fd59:8ba8:52ff::1 dev br-lan table local metric 0
anycast fe80:: dev eth0 table local metric 0
anycast fe80:: dev br-lan table local metric 0
anycast fe80:: dev tun0 table local metric 0
local fe80::c274:2bff:feff:54f4 dev eth0 table local metric 0
local fe80::c274:2bff:feff:54f5 dev br-lan table local metric 0
local fe80::dca9:8c88:db72:ccbc dev tun0 table local metric 0
multicast ff00::/8 dev br-lan table local metric 256
multicast ff00::/8 dev eth0 table local metric 256
multicast ff00::/8 dev tun0 table local metric 256
root@OpenWrt:~#

traceroute 8.8.8.8

root@OpenWrt:~# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 46 byte packets
1 10.105.4.1 (10.105.4.1) 120.616 ms 128.840 ms 152.693 ms
2 84.239.54.124 (84.239.54.124) 136.384 ms 32.631 ms 84.239.54.125 (84.239.54.125) 39.805 ms
3 vl201.mil-swb-core-1.cdn77.com (185.229.188.42) 67.094 ms vl203.mil-swb-core-1.cdn77.com (185.229.188.44) 81.875 ms vl201.mil-swb-core-1.cdn77.com (185.229.188.42) 86.533 ms
4 google.minap.it (185.1.114.26) 87.219 ms 90.807 ms 105.896 ms
5 108.170.255.201 (108.170.255.201) 134.992 ms 187.568 ms 192.178.104.189 (192.178.104.189) 202.247 ms
6 192.178.82.63 (192.178.82.63) 173.724 ms 192.178.44.135 (192.178.44.135) 136.664 ms 142.251.235.173 (142.251.235.173) 127.970 ms
7 dns.google (8.8.8.8) 139.704 ms 146.170 ms 156.484 ms

traceroute curl ipinfo.io

root@OpenWrt:~# traceroute ipinfo.io
traceroute to ipinfo.io (34.117.186.192), 30 hops max, 46 byte packets
1 10.105.4.1 (10.105.4.1) 114.691 ms 131.247 ms 140.792 ms
2 84.239.54.124 (84.239.54.124) 155.998 ms 84.239.54.125 (84.239.54.125) 185.673 ms 190.850 ms
3 vl203.mil-swb-core-1.cdn77.com (185.229.188.44) 218.929 ms 233.026 ms 241.309 ms
4 google.minap.it (185.1.114.26) 251.645 ms 232.565 ms google.mix-it.net (217.29.66.96) 213.888 ms
5 192.178.99.213 (192.178.99.213) 166.801 ms 192.178.104.189 (192.178.104.189) 175.883 ms 192.178.104.101 (192.178.104.101) 181.620 ms
6 142.250.211.21 (142.250.211.21) 188.370 ms 192.178.44.135 (192.178.44.135) 170.467 ms 142.250.211.29 (142.250.211.29) 170.768 ms
7 192.186.117.34.bc.googleusercontent.com (34.117.186.192) 167.139 ms 143.103 ms 143.868 ms

EDIT:

If I do the ping to 8.8.8.8 from OrangePi the ping go, If I do that from the PC connect bu Ethernet cable the ping is in error.