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-next>] [day] [month] [year] [list]
Message-ID: <5caa9b870712180945o17c797f7rb00a1b0d3fc12fc6@mail.gmail.com>
Date:	Tue, 18 Dec 2007 17:45:45 +0000
From:	"Steve Davies" <davies147@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: VIA Velocity and 802.1q VLAN support

Hi,

After a significant amout of archive searching, and code tweaking, I
am giving up and asking the list :)

I have a number of EPIA boards which need to operate in a mixed
tagged-VLAN and untagged-interface environment using their onboard
VIA-Velocity NICs. I am running a Debian ETCH 2.6.18 kernel, but have
managed to backport the latest 2.6.24-rc5 via-velocity driver fairly
simply. Sadly this does not seem to fix the problem.

Having added some debug kprintf, it appears as if the hardware VLAN
support is never enabled in this driver (vptr->vlgrp == NULL at all
times). I added a velocity_vlan_rx_register method, and enabled the
NETIF_F_HW_VLAN_RX feature, which did start to cause the appropriate
NIC registers to be set, but this simply stopped the inbound data
working entirely if a tagged vlan was created.

It manages to send packets both on the correct (tagged) vlan, and on
the untagged interface. The stock driver also receives packets on the
untagged interface okay, but inbound tagged packets never seem to make
it into the net subsystem.

I assume that the NIC is not allowing tagged packets into the driver
due to its built-in hardware acceleration/filtering :(

Is it inappropriate to beg for help and suggestions?

Thanks,
Steve
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ