Bug #1802
closed
Interface not showing in traffic shaper
Added by Jonathan Frank over 14 years ago.
Updated over 14 years ago.
Category:
Traffic Shaper (ALTQ)
Description
Hi,
I recently installed pfSense 2.0 and am using an USB network card for testing purpose. I noticed that the interface is not recognised by the traffic shaper.
Step to reproduce the issue:
- Connect the USB Card
- Assign it as LAN or WAN (Does not matter which interface it is assigned, it will not appear in TS section)
- Go into Traffic Shaper section
- Only the internal nic of the computer will show up, not the USB one.
After doing more research, it seem like not all drivers/network cards are supporting ALTQ, so that must be the issue.
I believe this can be closed.
Thanks
What driver does the network card use? It would be something like aue0, etc. We can double check the driver to see if it does support altq.
It use the "ue", which is not listed in the ALTQ supported driver list.
- Status changed from New to Closed
They all call themselves ue0 now I see. If you look in dmesg there would be a line saying what driver it actually is. If it's aue, that one does support altq, but some others do not. So listing ue on its own could be problematic. But if your specific card does work, you could edit ue into the list.
From the dmesg output I get, the NIC is using the Axe driver. So, no ALTQ support.
axe0: <vendor 0x0b95 product 0x1780, rev 2.00/0.01, addr 2> on usbus4
Root mount waiting for: usbus4
ugen4.3: <Generic> at usbus4
umass0: <Bulk-In, Bulk-Out, Interface> on usbus4
umass0: SCSI over Bulk-Only; quirks = 0x0000
Root mount waiting for: usbus4
miibus1: <MII bus> on axe0
rgephy1: <RTL8169S/8110S/8211B media interface> PHY 2 on miibus1
rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ue0: <USB Ethernet> on axe0
Yeah, unfortunately that is the case, axe(4) doesn't support altq. Was worth double checking though.
Also available in: Atom
PDF
Updated by 
Updated by