Project

General

Profile

Actions

Bug #2577

closed

On Intel D2500CC vlans don't work until I turn off vlan hardware tagging

Added by frater fenantius over 11 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/07/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

Vlans don't work on this board.
If I turn of vlan hardware tagging they start working.

Using a config.xml from another machine (changing the interface name) I am able to get this machine working by adding this cronjob

  • * * * * root ifconfig em0 | grep -q VLAN_HWTAG && ifconfig em0 -vlanhwtag
  • * * * * root ifconfig em1 | grep -q VLAN_HWTAG && ifconfig em1 -vlanhwtag

As a quick fix I propose a network setting to turn off hardware vlan tagging just like there's an option to turn off checksum offloading.

AFAIK this is a normal Intel NIC.
I don't know if this happens on other Intel NICs

The VLANs are working until a short moment before the menu appears.
In my case I have to wait until the cronjob does its work and gets it going....

Actions #1

Updated by Chris Buechler over 11 years ago

  • Status changed from New to Rejected

Not true in general (and I've never seen that with em) though seems there are always a few NICs that don't work with their hardware features. that's rare enough a <shellcmd> suffices

Actions #2

Updated by frater fenantius over 11 years ago

If there's an option for turning off checksum offloading and those other NIC features there's no valid reason to reject this. The Intel D2500CC is on paper an ideal pfsense machine.
Alas only on paper.

I'm not comfortable with BSD.
On a Debian based system I would create a script in/etc/network/ifup.d and it ensures me the command is always executed. Maybe it only has to be executed only once after booting,hence the cronjob I made.

Actions

Also available in: Atom PDF