@GruensFroeschli:
I dont think it's related, but:
Are your VLANs all on the same switch?
I see that you mix tagged and untagged traffic on the same interface.
This "could" be a problem.
Yes, they are. The interfaces on the pfsense box are in a vlan which is native on the trunk port on the switch.
I dont think you can do with the current setup what you describe.
Traffic would have to leave via one interface ( the /28), get NATed, reenter on the same interface and get routed to the WAN.
Well, can I get "around" this by using another physical interface on the pfsense box for the PublicInternet, instead of using a vlan interface, and "moving" the rules to that interface ? If that would work, I'd (not really happily) do it.
How does you ISP handle traffic on his side?
Will traffic from your IPs be routed to your main WAN IP no matter where it comes from?
My ISP routes all traffic to the /28 subnet via my public wan interface IP. I assume that in their upstream router they have something like this:
ip route A.B.C.192/28 0.0.0.15 D.E.F.21
and are exporting this route to BGP/OSPF/MPLS or whatever they speak upstream
You could scrap the /28 VLAN and add the additional public IPs on the WAN directly with PARP type VIPs (CARP wont work since it's a different subnet).
You then can use these VIPs in outbound NAT rules.
I NEED the /28 VLAN; this is essentially where I can do "internet" testing directly, without having to make ruleset changes on the firewall. There's at least a half dozen boxes on that subnet now, and I do not really want to to make VIPS and manage a constantly changing ruleset for each one of those boxes, some of which might be "foreign" machines with DHCP assigned addresses.
If I can make this work by using a separate physical interface for the PublicInternet, I'd be happy, but have to forgo using CARP which I was "saving" the last interface for (its an ALIX)….