Vlan1 On Primary LAN Interface

Peter I know this already and if you knew all this why didn’t you make it apart of your process instead of throwing things at the wall to see what sticks. I like complete processes and not parts of it. Hence the reason why I asked if this was documented anywhere and worn out with proving your process on the fly. I wasted an hour and half when doing the first part of your process to find out it did not work and I had to rollback. Put yourself in the other persons shoes for once and provide complete clarity and transparency.

The issue lays within the routing of the Interface Vlan10 profile. It clearly worked within my internal network along with connecting all my vlans together for passing traffic internally only and did not let me get past the internal Vlan10 to get out to the internet so my switches work fine as they are doing what they have programmed into them, but now all the routing is missing in the Vlan10 profile and I do not want to go through another “testing” phase with something you think will work. That is why hooking up a laptop is a waste of time and causes me unnessary work.

Again I am not challenging your knowledge and I do appreciate the help, but your approach is little much and well needs to be better so I do not waste anymore time in trying to see what works especially when rule sets are already there in place.

So now we know vlans do not do routing and all they do is seperate networks / traffic. So what does the LAN1 default zone profile have for routing that the Vlan10 profile is missing. That is the question.

Thank you.

I was planning on it anyway as you can not tell me why. Thank you.

Hello…..Thank you for the information, but I just want to make sure this is for sure the correct information as I want the newly created Vlan10 interface to be the primary interface to route all traffic for all my VLANS that LAN1 used to handle. Thank you.