Found my own answer, you can not run the EERO in bridge mode and allow another device (modem/router) to be your DHCP server.  It only works the other way around, you must put the modem/router in bridge mode so EERO can control you leases.  This should be easily correctable and makes more sense, your access points sit behind your router/modem, not the other way around.

Many reasons...

1. I have a well established network with many devices using static IP addresses, why when I'm trying to expand my wireless coverage should I change the topography and addressing?

2. Verizon Fios relies on the Modem and routing for control of the cable interface.  They will not support trouble shooting internet and cable issues issues if the Router/Modem is a bridge mode.

3. I have to deal with Verizon on setting up the Bridge, I can't control it through the interface, have you tried dealing with their support?

4. My access for my infrastructure is in a room that cancels the wi-fi signal, so I'm loosing a node.  Since it's a very large site, I have to use wired connections for the EERO as they tend to be out of range from each other.  They are not supposed to be access points, but a mesh network that takes advantage of routing wirelessly if necessary, this required adding a switch to support the EERO's behind the Gateway node.

5. My wired infrastructure now has to change, separating my network in 2 segments limiting access of devices across each network.

What's most upsetting is I had the discussion with EERO before buying them to make sure it would work the way I wanted it to and they confirmed that.  I simply wanted to replace my dumb access points with a Mesh network for controlling my wireless devices as an extension of my existing network.  I did not plan on reworking my entire network to do this.  Had the EERO worked in bridge mode, I would have just been able to add the improved wireless onto my network.