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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170501.105736.157375316602250235.davem@davemloft.net>
Date:   Mon, 01 May 2017 10:57:36 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     heyen2000@...il.com
Cc:     andrew@...n.ch, netdev@...r.kernel.org
Subject: Re: How does vlan driver pass vlan info to the h/w ethernet driver

From: carl h <heyen2000@...il.com>
Date: Mon, 1 May 2017 10:52:17 -0400

> But i can't see how the vlan info propagates down to the switch driver.

Which "VLAN info" are you talking about?

The VLANs configured onto the device itself or the per-packet VLAN
info.

Per-device VLAN configuration is communicated to the netdev driver
via netdev_ops->ndo_vlan_{add,kill}_vid().

Per-packet VLAN information is stored in skb->vlan_{proto,tci}.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ