That does, indeed, appear to be a solution to the problem. Albeit, not an
ideal solution. I really hope that this will be resolved in Neutron
eventually.
On Wed, Jan 10, 2018 at 5:00 PM, Jonathan Mills wrote:
> Thanks, Flint WALRUS. I will certainly try that.
>
> On Wed, Jan 10, 2018 at 4:57
Thanks, Flint WALRUS. I will certainly try that.
On Wed, Jan 10, 2018 at 4:57 PM, Flint WALRUS
wrote:
> As you’re using a L2 network topology and until all of your project use a
> different network you can do:
>
> domain=domain1,10.10.10.0/24
> domain=domain2,20.20.20.0/24
>
> Within the dnsmas
As you’re using a L2 network topology and until all of your project use a
different network you can do:
domain=domain1,10.10.10.0/24
domain=domain2,20.20.20.0/24
Within the dnsmasq-neutron.conf file.
Of course, restart the neutron-server service once done.
Le mer. 10 janv. 2018 à 22:40, Jonathan
