netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* VIA Velocity VLAN vexation
@ 2007-03-22 13:48 linux
  2007-03-22 23:16 ` Francois Romieu
  0 siblings, 1 reply; 4+ messages in thread
From: linux @ 2007-03-22 13:48 UTC (permalink / raw)
  To: netdev; +Cc: linux

I have a machine (x86-32, 2.6.20.3) with two ethernet interfaces:
a 100M Tulip and a 1G VIA Velocity.  Both are connected to a common
VLAN-capable switch.  The eventually desired configuration is VLAN
support on the Gbit interface.

If I set the Tulip's switch port to tagged, and configure a VLAN on the
Tulip interface appropriately, packets flow as expected.

But if I try the same configuration on the Velocity interface, things
don't work.
I can see tagged ICMP pings go out, but no responses come back.
I can see ARP requests and responses on the target machine.
If I manually configure the ARP caches, I can see the pings and responses
on the target machine.
If I kludge the target's ARP cache to point back to the source's Tulip
interface, I can see the ping responses on the Tulip interface.

But I don't see the ping responses on the Velocity interface.

The vlan interface name and address is the same, so it can't be
firewall rules distinguishing.

I have tried various ping sizes from 0 to 1472.


Is this likely to be a problem with the via-velocity driver?
Is anyone working on it?  Or should I just get a different gigabit card?

Thanks for any advice!

00:09.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet Adapter [1106:3119] (rev 11)
00:0d.0 PCI bridge [0604]: Digital Equipment Corporation DECchip 21152 [1011:0024] (rev 03)
02:04.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21142/43 [1011:0019] (rev 41)
02:05.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21142/43 [1011:0019] (rev 41)
02:06.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21142/43 [1011:0019] (rev 41)
02:07.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21142/43 [1011:0019] (rev 41)

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: VIA Velocity VLAN vexation
  2007-03-22 13:48 VIA Velocity VLAN vexation linux
@ 2007-03-22 23:16 ` Francois Romieu
  2007-03-23 18:51   ` linux
  0 siblings, 1 reply; 4+ messages in thread
From: Francois Romieu @ 2007-03-22 23:16 UTC (permalink / raw)
  To: linux; +Cc: netdev

linux@horizon.com <linux@horizon.com> :
[...]
> Is this likely to be a problem with the via-velocity driver?

Yes.

> Is anyone working on it ?

Not as much as I'd like to.

> Or should I just get a different gigabit card ?

This one probably got answered the 2005/11/29. :o)

I'll got to bed in a few minutes but I'll happily resurrect the
velocity vlan patches.

-- 
Ueimor

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: VIA Velocity VLAN vexation
  2007-03-22 23:16 ` Francois Romieu
@ 2007-03-23 18:51   ` linux
  2007-03-23 21:43     ` Francois Romieu
  0 siblings, 1 reply; 4+ messages in thread
From: linux @ 2007-03-23 18:51 UTC (permalink / raw)
  To: linux, romieu; +Cc: netdev

>> Or should I just get a different gigabit card ?
>
> This one probably got answered the 2005/11/29. :o)

Ah, that's where I asked before.  I misplaced the e-mail.
I hope you don't mind my asking every year or two.

But I don't see any suggestions for an alternative gigabit
card anywhere.  I had assumed they all mostly worked, but
now it appears I need to know details.

> I'll got to bed in a few minutes but I'll happily resurrect the
> velocity vlan patches.

Haven't they been merged upstream already?


Anyway, thanks for the reply!

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: VIA Velocity VLAN vexation
  2007-03-23 18:51   ` linux
@ 2007-03-23 21:43     ` Francois Romieu
  0 siblings, 0 replies; 4+ messages in thread
From: Francois Romieu @ 2007-03-23 21:43 UTC (permalink / raw)
  To: linux; +Cc: netdev

linux@horizon.com <linux@horizon.com> :
[...]
> But I don't see any suggestions for an alternative gigabit
> card anywhere.  I had assumed they all mostly worked, but
> now it appears I need to know details.

Mostly.

Assuming you won't play with huge jumbo frames, I'd suggest
a plain old pci 8169 (not a PCIe 8168) for VLAN. 

[...]
> Haven't they been merged upstream already?

No.

-- 
Ueimor

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-03-23 21:44 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-22 13:48 VIA Velocity VLAN vexation linux
2007-03-22 23:16 ` Francois Romieu
2007-03-23 18:51   ` linux
2007-03-23 21:43     ` Francois Romieu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).