netdev - IPVLAN on non-ethernet interfaces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <866009fe-e88a-4d4f-8ff3-34e0cbad3caf@scoopta.email>
Date: Fri, 29 Aug 2025 20:17:32 -0700
From: Scoopta <mlist@...opta.email>
To: netdev@...r.kernel.org
Subject: IPVLAN on non-ethernet interfaces

I'm trying to find documentation that explains why IPVLANs are 
restricted to ethernet only but can't seem to, so figured I'd ask here. 
Is there some technical reason why you couldn't for example attach an 
IPVLAN to a tun or other non-ethernet interface? I'm not familiar with 
the inner workings of this device but at least on the surface it looks 
like it should only care about the IP address of traffic and the L2 in 
use shouldn't matter.

Thanks