Kind of, but not really.
The external side of our FW is all L2. We have multiple L2/L3 segments on our WAN/INet beyond the FW. There are 2 Border routers beyond the firewall own the L2/L3, which the firewall sees as the WAN. The BRs are EIGRP neighbors with HSRP for the multiple L2/L3. So in the NAT policy we just "picked" a "random" L2 network as the egress interface, because for us it really doesn't matter if it's the "right" or matching ingress interface because the BRs own all of them.
So the BRs have: WAN-1 (WAN-Zone)
WAN-2 (WAN-Zone)
WAN-3 (WAN-Zone)
The FW participates in WAN-1, WAN-2, WAN-3 from a L2 perspective. The ingress might have come in on WAN-1, but the NAT might have said egress = WAN-2, and it worked because the next hop was the BR which has/knows about all those L2 segments.
But with palo "fixing the bug" the egress NAT interface needed to match the specific interface even though they are all a part of the same zone..
... View more