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
| ||
|
Message-ID: <20140814112858.35a0cc88@haswell.linuxnetplumber.net> Date: Thu, 14 Aug 2014 11:28:58 -0700 From: Stephen Hemminger <stephen@...workplumber.org> To: Stephane Chazelas <stephane.chazelas@...il.com> Cc: Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: network interfaces called "all", "default" or "config" On Thu, 14 Aug 2014 10:41:39 +0100 Stephane Chazelas <stephane.chazelas@...il.com> wrote: > $ ip link add link eth0 eth0:123 type vlan id 123 > $ ip link del link eth0 eth0:123 > RTNETLINK answers: Operation not supported eth0:123 is one of the old style interface names. Kernel and iproute treat these specially. Don't use them. They exist only for compatibility with the dark ages. You should use period (ie eth0.123) for VLAN's -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists