[
https://issues.apache.org/jira/browse/CLOUDSTACK-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland updated CLOUDSTACK-9887:
--------------------------------------
Description:
If a VM is created in an isolated network and then gets assigned a secondary
nic in a shared network, dnsmasq will be configured with 0.0.0.0 as gateway.
dnsmasq then does the right thing and replaces it with its primary network
interface. This is not useful for us so we should ignore it.
Creating a new shared network the default gateway is correct:
{code}
root@r-22-VM:~# cat /etc/dnsmasq.d/cloud.conf
dhcp-range=interface:eth0,set:interface-eth0-0,192.168.1.11,static
dhcp-option=tag:interface-eth0-0,15,cs1cloud.internal
dhcp-option=tag:interface-eth0-0,6,192.168.1.11,8.8.8.8,8.8.4.4
dhcp-option=tag:interface-eth0-0,3,192.168.1.1
dhcp-option=tag:interface-eth0-0,1,255.255.255.0
{code}
then when creating a VM with an isloated nic the dnsmasq on the shared
network VR becomes
{code}
root@r-23-VM:~# cat /etc/dnsmasq.d/cloud.conf
dhcp-range=interface:eth0,set:interface-eth0-0,192.168.2.11,static
dhcp-option=tag:interface-eth0-0,15,cs1cloud.internal
dhcp-option=tag:interface-eth0-0,6,192.168.2.11,8.8.8.8,8.8.4.4
dhcp-option=tag:interface-eth0-0,3,0.0.0.0
dhcp-option=tag:interface-eth0-0,1,255.255.255.0
{code}
was:If a VM is created in an isolated network and then gets assigned a
secondary nic in a shared network, dnsmasq will be configured with 0.0.0.0 as
gateway. dnsmasq then does the right thing and replaces it with its primary
network interface. This is not useful for us so we should ignore it.
> A VM with dual shared/isolated network gets bogus GW assignment
> ---------------------------------------------------------------
>
> Key: CLOUDSTACK-9887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9887
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Reporter: Daan Hoogland
>
> If a VM is created in an isolated network and then gets assigned a secondary
> nic in a shared network, dnsmasq will be configured with 0.0.0.0 as gateway.
> dnsmasq then does the right thing and replaces it with its primary network
> interface. This is not useful for us so we should ignore it.
> Creating a new shared network the default gateway is correct:
> {code}
> root@r-22-VM:~# cat /etc/dnsmasq.d/cloud.conf
> dhcp-range=interface:eth0,set:interface-eth0-0,192.168.1.11,static
> dhcp-option=tag:interface-eth0-0,15,cs1cloud.internal
> dhcp-option=tag:interface-eth0-0,6,192.168.1.11,8.8.8.8,8.8.4.4
> dhcp-option=tag:interface-eth0-0,3,192.168.1.1
> dhcp-option=tag:interface-eth0-0,1,255.255.255.0
> {code}
> then when creating a VM with an isloated nic the dnsmasq on the shared
> network VR becomes
> {code}
> root@r-23-VM:~# cat /etc/dnsmasq.d/cloud.conf
> dhcp-range=interface:eth0,set:interface-eth0-0,192.168.2.11,static
> dhcp-option=tag:interface-eth0-0,15,cs1cloud.internal
> dhcp-option=tag:interface-eth0-0,6,192.168.2.11,8.8.8.8,8.8.4.4
> dhcp-option=tag:interface-eth0-0,3,0.0.0.0
> dhcp-option=tag:interface-eth0-0,1,255.255.255.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
