You are not logged in.
Today I experimented with Outline by installing the Outline manager app and the client from AUR. After realizing that the client was having major issues staying up, I decided to stop it. But that left a tunnel connection that is preventing applications from connecting to the WWW:
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether f8:bc:12:99:82:3b brd ff:ff:ff:ff:ff:ff
3: outline-tun0: <NO-CARRIER,POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 500
link/none
I traced this back to "outline_proxy_controller.service" in systemd that creates the tunnel. This persists even after uninstalling the Outline client:
$ systemctl | grep outline
sys-devices-virtual-net-outline\x2dtun0.device loaded active plugged /sys/devices/virtual/net/outline-tun0
sys-subsystem-net-devices-outline\x2dtun0.device loaded active plugged /sys/subsystem/net/devices/outline-tun0
outline_proxy_controller.service loaded active running Outline Proxy Routing Controller
Disabling the system and rebooting gets rid of the tun connection, but various applications are still giving me a "Proxy is rejecting requests" messages and other connection failures. In Firefox and Thunderbird, switching from "use system proxy settings" to "no proxy" option got the apps to work again, but of course this shouldn't be the right solution. Pinging 8.8.8.8 from the command line always works.
How could I get into this mess by just installing some apps without touching iptables or other manual configuration?
Thanks for any advice you may provide.
Offline