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: <CABM+yxnbLPjoq4E2Z3d2Jc5qUvN_TWUb6rQpjDWCTs=9j0ce3A@mail.gmail.com>
Date:   Mon, 1 May 2017 14:26:52 -0400
From:   carl h <heyen2000@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org
Subject: Re: How does vlan driver pass vlan info to the h/w ethernet driver

It appears that the switchdev driver model was introduced after 2.6.39
which is the
kernel version that I'm using unfortunately.

So considering this, and the fact that the switch hardware I'm using has support
for vlan tag insertion, how would it have been accomplished for my version
of the kernel?

Also is it possible to get the vlan driver to insert the vlan tags for
each packet? If so
how can that be accomplished?

Thanks
/carl


On Mon, May 1, 2017 at 10:57 AM, David Miller <davem@...emloft.net> wrote:
> 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