|I'd love to help you but I have no experience with that router.|
I do have to wonder why you're using a block of routable IP's internally though:
This doesn't make a lot of sense to me. Most everybody uses NAT and Private IP's internally on the LAN.
To be honest, I'm not sure why you need the block of external IP's either. You only have one device (the WAN interface) that you mention. I suppose if you're planning on having a lot of outward facing servers (like web servers) I understand. But you don't mention that. So perhaps you could explain your need for the aforementioned blocks of IP's (both internal and external).
I have IPCop firewall behind this router which will be the gateway for my workstations and I have VLAN configured for our servers
I have no experience with IPCop either so can't help you with that. You mention a VLAN for servers....what about clients? If you're going to use VLAN's, I would use them in all cases not just for servers. I would have a client VLAN, a server VLAN, a printer VLAN. You may actually have need for multiple client VLAN's. You might for instance want to keep the finance department separated from everyone else for example.
Perhaps if you start at the begining and give us an overview of your setup, how it connects physically as well as logically, and explain what it is you're trying to achieve we can find a way to help you make this work.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.