Why would new span port all of a sudden stop traffic between zones from flowing (no logs at all) works after span is rule is disabled.
Are you attempting this to do this all on one vsys? I've never used SPAN ports in conjunction with actually routing traffic through the firewall unless I've seperated these via vsys so I'm not sure if you could be hitting a software bug or if this is expected behavior.
Obviously with SPAN/Tap deployments you wouldn't have security policies or zones since the firewall just sits on the wire essentially. It could be that creating that SPAN port the rest of your configuration shuts down as it isn't expected to be there, but I would have to assume that this would be a bug within whatever code version you are running.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!