Skip to contentSkip to conversation

vlan JMicron Technologies, Inc. JMC250 PCI Express Gigabit Ethernet

DISCUSSION Vito Mattera 2 participants 2 messages Mar 11, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

I'm trying to add vlan using the network adapter JMC250 in CentOS 5.3 with the driver: kmod-jme-1.0.5-1.el5.elrepo.i686.rpm

when I type the command:
vconfig add eth0 3

I have the following message:

802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
register_vlan_device: Device eth0 has buggy VLAN hw accel

and no vlan is created.

what is my mistake ?

TIA

Best regards

vito mattera

Signature · 10 lines
CoST - Computers Services and Technologies s.r.l.
20137 via Longhi 13 - Milano - Italy
phone : +39 0245446.1 ext. 253
mobile: +39 335275451
fax   : +39 0245446.333

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione. Grazie.

This e-mail and any attachment are confidential and may contain privileged information intended for the addressee(s) only.
Dissemination, copying, printing or use by anybody else is unauthorized. If you are not the intended recipient, please delete this message and any attachment and advise the sender by return e-mail. Thank you
#1 lore raw
Quoted 10 lines · On Thu, 11 Mar 2010 17:04:57 +0100 Vito Mattera <[email protected]> wrote:

I'm trying to add vlan using the network adapter JMC250 in CentOS 5.3 with the driver: kmod-jme-1.0.5-1.el5.elrepo.i686.rpm

when I type the command:
vconfig add eth0 3

I have the following message:

Quoted 6 lines

802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
register_vlan_device: Device eth0 has buggy VLAN hw accel

and no vlan is created.

what is my mistake ?

Message happens if driver sets hardware vlan filtering but provides no callback.
The driver appears okay in upstream kernel, most likely something got lost in backport process in redhat or the copying of redhat done by centos.