netdev - Re: Problem with VLANs and via-velocity driver

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 for Android: free password hash cracker in your pocket

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

Message-ID: <loom.20100210T171704-457@post.gmane.org>
Date:	Wed, 10 Feb 2010 16:43:37 +0000 (UTC)
From:	Tiago Pierezan Camargo <tcamargo@...il.com>
To:	netdev@...r.kernel.org
Subject: Re: Problem with VLANs and via-velocity driver

> Kevin Shanahan <kmshanah <at> disenchant.net> writes:

Hi
Sorry for resurrecting an old thread, but I'm having the same problem here.

> On Fri, Nov 13, 2009 at 07:40:39AM +0100, Patrick McHardy wrote:
> > Kevin Shanahan wrote:
> > > Hi,
> > > 
> > > I've had some problems with getting a fairly simple (I thought) VLAN
> > > configuration working with the on board Via NICs on my Via M700
> > > board. Looks like as soon as a tagged VLAN interface is added, the
> > > underlying "raw" (untagged) interface stops responding.

My setup is a bit different: I want to sniff all network activity, including
possible tagged traffic. No tagged interfaces are created.

> > > A bit of searching found a few references to similar problems going
> > > back a few years (2005, 2007). Sounded like there were some driver
> > > issues, but it wasn't clear from the messages I found whether they
> > > were believed to be fixed or not. I tried the same test using a
> > > differnt NIC with the tg3 driver and there were no problems, so it
> > > looks to me like it's still a via-velocity issue. Unfortunately I
> > > don't have room to add NICs to this machine and need to use the on
> > > board Via hardware.
> > 
> > There's some special-casing for VID 0 in velocity_init_cam_filter().
> > Does "ip link add link eth0 type vlan id 0" make any difference?
> 
> Thanks Patrick, this command got the untagged interface working again
> (eth1 in my case). I can use this as a work around.

Unfortunately, Patrick's workaround doesn't work for me. To see any tagged
packet I need to create a vlan that matches the packet vlan (same id).

Régis' promiscous mode patch (http://lists.openwall.net/netdev/2008/10/08/106)
does not work either. I tried to completely disable hw vlan filtering without
success. It seems my board uses a different register/offset to disable filtering.

06:0a.0 0200: 1106:3119 (rev 11)
        Subsystem: 1106:0110
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 16
        Region 0: I/O ports at e000 [size=256]
        Region 1: Memory at fbfff400 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D3 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: via-velocity
        Kernel modules: via-velocity

Any suggestions?

Thanks!

- Tiago

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html