Set the tunnel device name rather than parsing it out of the log #21

New issue

Closed

opened 2026-08-17 16:57:01 -04:00 by mysticalsoap · 0 comments

mysticalsoap commented

2026-08-17 16:57:01 -04:00

Owner

aqomui writes the OpenVPN config itself (tunnel.py:write_config), and
the shipped templates already carry dev tun (e.g.
resources/ProtonVPN_config:2). Writing dev ovpn-aqomui instead means the
interface name is known rather than discovered -- no parsing, under DCO or
not.

This supersedes the regex added in #15. That fix is correct as a stopgap, but it
invests in parsing output we do not have to produce, and deletes the entire
"device detection" bug class for a few lines.

Check first whether a fixed name interacts badly with multiple concurrent
tunnels -- the bypass runs a second OpenVPN process, so the name needs a suffix
per tunnel rather than being a single constant.

aqomui writes the OpenVPN config itself (`tunnel.py:write_config`), and the shipped templates already carry `dev tun` (e.g. `resources/ProtonVPN_config:2`). Writing `dev ovpn-aqomui` instead means the interface name is **known** rather than discovered -- no parsing, under DCO or not. This supersedes the regex added in #15. That fix is correct as a stopgap, but it invests in parsing output we do not have to produce, and deletes the entire "device detection" bug class for a few lines. Check first whether a fixed name interacts badly with multiple concurrent tunnels -- the bypass runs a second OpenVPN process, so the name needs a suffix per tunnel rather than being a single constant.

mysticalsoap added the

architecture

label

2026-08-17 16:57:01 -04:00

mysticalsoap referenced this issue from a pull request that will close it,

2026-08-19 13:43:41 -04:00

change: set the tunnel device name in the config instead of parsing the log #64

mysticalsoap closed this issue

2026-08-19 14:23:33 -04:00