Project

General

Profile

Actions

Bug #8061

closed

LAN WAN Interfaces missing in Traffichshaper

Added by W FM about 7 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Traffic Shaper (ALTQ)
Target version:
-
Start date:
11/06/2017
Due date:
% Done:

0%

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

Description

In 2.3.5 LAN and WAN interface(s) are missing from the list.

see picture attached

If queues are deleted only way to get them back is via the wizard.


Files

pfs.JPG (89.2 KB) pfs.JPG W FM, 11/06/2017 06:35 PM
Actions #1

Updated by W FM about 7 years ago

firewall_shaper.php
Firewall / Traffic Shaper / By Interface

(sorry for the typo)

Actions #2

Updated by Jim Pingle about 7 years ago

What type of interfaces are those (driver name)?

Perhaps they were supported by the shaper on older versions but they are not supported now.

Actions #3

Updated by W FM about 7 years ago

em0@pci0:0:3:0: class=0x020000 card=0x10128086 chip=0x10108086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = '82546EB Gigabit Ethernet Controller (Copper)'
class = network
subclass = ethernet

Actions #4

Updated by W FM about 7 years ago

on irc someone else had the same issue.

Also worth noting this is i386

Actions #5

Updated by W FM about 7 years ago

Bridges and VLAN interfaces on LAN show up.
a spare interface on the same card shows up
It is just WAN interfaces and LAN that have no label / not listed.

Actions #6

Updated by Corey Boyle about 7 years ago

I have the same issue. WAN is nfe0. LAN is em0.

Actions #7

Updated by Josh Chilcott about 7 years ago

I am also confirming this issue on 2.3.5 and now 2.3.5_p1.

We have 22 affected units and they are all using the igb driver. All are Supermicro SYS-5018A-FTN4 systems and we purchased multiple units through the pfSense® store in late 2015 and early 2016 as C2758 models.

Actions #8

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Resolved

These all appear to be old driver-specific instances of ALTQ support not being present for specific drivers at the time.

Actions

Also available in: Atom PDF