Thanks - my post may have been a bit longer but I didn't want to exclude any important details.Usually what I have seen is it is related to the gateway and routing. In a layer 3 switch network you want the L3 switch to be the gateway for all clients. There will be a gateway for each network on the L3 switch. Then you want the default route on the switch pointing to the router. Then there should be routing statements on the router pointing to the L3 switch for all disconnected networks. More than likely, you need to open all disconnected networks in the firewall so they have internet access. I would check the gateway for each of the clients not able to ping. There should be a L3 path to the devices.
Adding multiple links between the router and the L3 switch can cause spanning tree problems. I only use 1 link but that will require the L3 switch to do DHCP or a device other than the router. The easy fix is to use 1 connection from pfsense to the L3 switch.
To my understanding, all of these points are satisified - including that I am using just a single transit link (not multiple transit networks). The only true problem is that B cannot ping its gateway on pfSense....which is the source of my frustration. I can ping the pfSense gateway from the switch (if I telnet to the switch).
I can also ping the switch end of the transit network from pfSense (i.e. the transit SVI or, routing interface in Dell parlance).
I can even ping the the Workstation B's SVI from pfSense (which I am using as the configured gateway for B).
All this tells me:
- the switch inter-VLAN routing is working
- the pfSense gateway is correctly configured
- the pfSense static route is correctly configured
By rights, it should work - but it doesn't and I can't really see a reason why it won't. I am also out of creative ideas what else to try.
EDIT: Correct me if I am wrong but you seem to note that I am defining more than 1 transit network? I don't see how I would be doing that - and that is certainly not my intention. Can you explain this a bit?