Edited with correction after I looked it up.
@Paul Mew
didn't reply cause I didn't want to edit out the graphics and such in my reply. Okay - the change in pfsense platform was good to know. apologies if I seemed overly harsh. but that does help me understand your original question.
Are you attempting to use the 6450 as just a L2 switch right now? If so you do not need to configure router interfaces in the 6450. typically you have a parent interface (bce1) and then you define the rest of your vlan interfaces, 1, 40 and so on. BUT - what about my gui? chicken and the egg
or you need to use the head on your pfsense box... chicken and the egg 'cause if you don't get it right you won't have internet to look for help on how to config what you want. the example I gave you above you would need to configure tagging for vlan 1 and vlan 40 on 1/1/1. question is when do you do that?
digression...
Unfortunately not. When I assign 1/1/1 in any form (tagged,untagged or Dual) to VLAN 40, it takes down my connection to pfsense although I can still communicate with the switch via the GUI.
assigning 1/1/1 untagged to VLAN 40 will absolutely take down your connection to pfsense and it will also kill your connection to at pfsense to VLAN40 - dead. tagging VLAN 40 will cause vlan 1 packets to get tagged (I believe) unless you use dual-mode (which is to say untagged traffic goes to this vlan and in your case - trying to use 1).
end digression...
at the beginning of course. my guess is you configured it as LAN during the pfsense setup see the link I referenced above.
also your labels may cause you some confusion though I think its a valid key/clue to where you are at. FWIW, that quad port NIC would be handy in a pfsense box.
However if you are going to only have 2 interfaces (which is fine) and want to use the 6450 as a core router/switch then I recommend to simply establish a "transit vlan" This will require you to use the 6450 as a L3 device (core router and it will need a default g/w configured going to the pfsense connected interface). The plus side is that inter vlan traffic routes at switch speed. there are some down-sides. no pfsense providing DHCP, must impelment any inter vlan restrictions via access lists in the 6450. Note to me these aren't really down sides but they may be to you.
so it may be truly better to understand your final desired state with all vlans to help you get there from here.
However
Without going into what you really want to build then if you want to start small and use the pfsense box for routing - you can but you'll need to reconfigure to use vlans (1, and 40) from the get go - though you can probably reconfigure and not need to re-install by using the head on the box.
your bce1 will need to be "physical" use vlans, configure vlan 1 (if that is what you are using for most of your trusted ports) and then vlan 40 both as tagged on bce 1.
1/1/1 will be tagged for 1 and 40 can't remember whether you will need to set up a dummy vlan or not. don't think so but vlan 1 is kinda funny about certain things...
I can see how you came out thinking about dual-mode (or pvid or native vlan)...
My recollection is that pfsense does not support that model.
last bit of advice. If possible also avoid using vlan 1 Or "The DEFAULT VLAN" there's some magic sometimes with that. that said sometimes you have to cause some devices (usually older that say they support vlans) don't really do well except using vlan 1...
I realize this rambled a little bit. sorry.
