Skip to content

Network panel mistakes Clash TUN interface for Ethernet uplink #13525

Description

@LIghtJUNction

What happened

With Clash Verge TUN enabled, the Omarchy network panel identifies the TUN device (Meta) as the active Ethernet connection. It shows Ethernet (10gbit), the TUN IP 198.18.0.1, and TUN gateway 198.18.0.2, even though the physical uplink is Wi-Fi.

omarchy-network-status --verbose reports iface=Meta, type=ethernet, and speed=10000 in this situation.

Why it happens

bin/omarchy-network-status selects the device with ip route get 1.1.1.1. A TUN policy route sends that lookup through Meta (in my case, table 2022). The script then categorizes every device without /sys/class/net/<device>/wireless as Ethernet. Meanwhile, the main routing table has a default route via wlan0.

Expected behavior

The panel should describe the physical uplink (wlan0 and its Wi-Fi connection), while the internet ping can still measure the current routed path through the TUN device.

Reproduction evidence

$ ip -j route get 1.1.1.1
[{"gateway":"198.18.0.2","dev":"Meta","table":"2022","prefsrc":"198.18.0.1"}]

$ ip -j route show table main default
[{"dst":"default","gateway":"10.175.255.254","dev":"wlan0","metric":600}]

Omarchy 4.0.4, Clash Verge TUN, systemd-networkd/iwd uplink.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions