First of all, thanks for the one-click script, it's really handy!
As the question when the cloud server is using cloud flare's warp-cli command line program, the openvpn client connects to the server at this time, which will lead to no Internet access, warp-svc component prompts as follows:
WARN warp::warp: Dropping martian, tun should not have seen this src_addr=172.17.48.191
The same warp-cli configuration, I uninstalled the script using openvpnas from the official website, and when warp-cli's warp mode is turned on, it is possible to access the internet, and based on experience, I suspect that the problem lies here:
/etc/systemd/system/openvpn-iptables.service
default via 172.17.63.253 dev eth0 proto dhcp metric 100
10.8.0.0/24 dev tun0 proto kernel scope link src 10.8.0.1
172.17.0.0/18 dev eth0 proto kernel scope link src 172.17.48.191 metric 100
But I don't know the iptables setup rules, if you can give me a modified rule, I can verify it,thanks
First of all, thanks for the one-click script, it's really handy! As the question when the cloud server is using cloud flare's warp-cli command line program, the openvpn client connects to the server at this time, which will lead to no Internet access, warp-svc component prompts as follows:
WARN warp::warp: Dropping martian, tun should not have seen this src_addr=172.17.48.191
The same warp-cli configuration, I uninstalled the script using openvpnas from the official website, and when warp-cli's warp mode is turned on, it is possible to access the internet, and based on experience, I suspect that the problem lies here:
/etc/systemd/system/openvpn-iptables.service
route
But I don't know the iptables setup rules, if you can give me a modified rule, I can verify it,thanks