Second, stop using the bridge to do the serving, and assign
address, pool, dhcp server and dhcp-server network PER VLAN.
The vlans interface is the bridge.
DONE
now you are in charge and not the bridge!!
I actually had it split up first but I got stuck because I had to create individual public IP addresses per VLAN as well as its own IP pool with each gateway being the public IP. This was ineffective because I was using too many public IPs and had to create too many different pools. Am I doing something wrong here?
I now have 3 interfaces.
Interface 1 - this has 20 VLANS in
Interface 2 - this has 3 VLANS
Interface 3 - This has 2 VLANS
How can I make it so that all the above VLANS use the same IP Pool and Gateway without using a bridge?
The purpose of vlans is to separate traffic between subnets.
If you dont need separate subnets dont create so many vlans. Lump groups together for example.
Yes, you need to have all the pools addresses etc. but tis a one time setup.
If youre trying to stop broadcast traffic between client bridged vlans, I think you could to add the clients ports to the same horizon, and leave your internet port out of it.