VLAN parent interface / altq interface wrong assumptions about int_family name format
I ran into an issue with vmxnet3 NICs on current pfsene-2.1 developement release.
VMware stupidly choose vmx3f as interface family name which causes pfsense to not show the interfaces of that type int the selection for parent interfaces for vlan and altq.
The problem is that pfsense uses a suboptimal regex that splits the interface index and the interface family in is_jumbo_capable and is_altq_capable. The ifindex is matched anywhere in the ifname instead of just at the end of it.
The attached patch fixes the issue. Maybe switching to preg_match as done in checking for wireless interfaces is a better way to go.