Last days I install 2 servers, one with Centos7 and other with Debian8,
without Openstack/Neutron. Both with the same DNSMASQ config I originally
posted.
On both I was using version 2.76 and upgraded to 2.78, using the same
ethernet interface changing the IP address between 100.97.97.1/24 and
100.9
El 2018-12-05 12:59, john doe escribió:
On 12/5/2018 1:58 PM, Geert Stappers wrote:
On Wed, Dec 05, 2018 at 09:09:25AM -0300, jmperrote wrote:
El 2018-12-04 12:26, john doe escribió:
On 12/4/2018 12:02 PM, jmperrote wrote:
John Doe, sorry for my mistake, my actual configuration of dnsmasq
a
On 12/6/2018 3:50 PM, jmperrote wrote:
> El 2018-12-05 12:59, john doe escribió:
>> On 12/5/2018 1:58 PM, Geert Stappers wrote:
>>> On Wed, Dec 05, 2018 at 09:09:25AM -0300, jmperrote wrote:
El 2018-12-04 12:26, john doe escribió:
> On 12/4/2018 12:02 PM, jmperrote wrote:
>>
>> Jo
On Thu, Dec 06, 2018 at 06:52:11PM +0100, john doe wrote:
> On 12/6/2018 3:50 PM, jmperrote wrote:
> dhcp-option=eth0,6,10.11.37.15 #dns primario
> dhcp-option=eth0,1,255.255.255.0 # mascara de red
> dhcp-option=eth0,option:router,10.11.37.1 # gateway
>
> dhcp-range=interfa
Luis,
You should probably file a bug against neutron
(https://bugs.launchpad.net/neutron/) with the relevant info, along with
the neutron commands you're running and debug from the dhcp-agent and
/var/lib/neutron/dhcp/xxx/ files as necessary. I don't exactly
understand what you mean by "LAN
Hi Brian,
Ok, I'll file a bug there. Until today, it was not clear to happen only
with Neutron.
To explain, "LAN change" is connect a specific DHCP client from "namespace
A" to "namespace B". Each namespace with a different
provider:segmentation_id (VLAN) and Subnet, and the same gateway network.
