11-23-2017 03:58 PM - edited 11-23-2017 04:02 PM
Tearing my hair out here so any help appreciated.
This is a VM firewall, VM-300 ver 8.0.3-h4.
I have created new subinterfaces for three VLANs, one of which is a guest VLAN (111) which has its own vSwitch, port group, sub-interface and zone. However, all traffic seems to be steering to the same interface (eth1/2.15). Since eth1/2 was the original interface before I created the new subinterfaces, I'm wondering if it's holding onto it for some reason.
The tagging all looks correct all the way through the chain, from the switch to the PA network adapters, so I'm at a loss as to why it's doing this.
11-24-2017 01:10 AM
These are all source interface 1/2.15 so it's on the ingress. It looks like your vswitch is tagging everything as vlan15
11-24-2017 01:15 AM
After extensive troubleshooting, the penny dropped and I have seen the error of my ways. I was pinging on a core switch & sourcings from the SVI. Since the switch uses its control plane routing table, all traffic was going to the default route .. which is on the 1/2.15 interface. By testing from the 'outside' and using the proper default gateway (on the firewall), everything works just as it should. Schoolboy error.
Thanks for taking the trouble to reply though.
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!
