Traffic Shaper Wizard not functioning in 2.2.4

smhick

The Traffic Shaper Wizard is not functioning in 2.2.4
Testing environment
1 - WAN connection
1 - LAN connection

When running the Wizard I select one WAN connection type and One LAN connection type
Then hit next and receive the following Error
You have less interfaces than number of connections!

I have an older install of pfSense 2.2.3 and this wizard works fine without any issues

I've confirmed this issue by installing a fresh copy of pfSense 2.2.3 the Wizard worked fine than ran the update to 2.2.4 and the Wizard fails

Testing on the following environment
VMware ESXi, 5.1.0, 1065491
Manufacturer: IBM
Model: IBM System x3550 M4 Server -[7914F2G]-
Processors: 6 CPU x 2.499 GHz
Processor Type: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz

I thought it was a bug and reported it but got the following reply

Please post on the forum for assistance or use another support method. There is no bug here, but perhaps something changed and you either don't have a NIC that support ALTQ now (driver change, perhaps) or the interfaces are not setup properly and it thinks you have too few WAN-type or LAN-type interfaces depending on how gateways are configured. The forum is the place to discuss it though.

any ideas welcomed

jimp

You need to provide a lot more detail, such as:

What type of NICs do you have? (from Interfaces > assign, e.g. emX, vmxY)
What type of interface is WAN (Static IP, DHCP, etc)?
If WAN is static, do you have a gateway selected on Interfaces > WAN? (you should)
What type of interface is LAN (Static IP)?
If LAN is static, do you have a gateway selected on Interfaces > LAN? (you should not)

The shaper error is telling you that the count of interfaces you gave does not match the type and number of interfaces capable of using shaping, so like the note on the ticket said, the two most common explanations are that it either doesn't think you have enough WANs (e.g. missing gateway on WAN), or you don't have enough LANs (gateway set on LAN when it shouldn't be), or perhaps the type of NIC you have no longer supports altq.