FlatDHCP mode responds to DHCP requests from public network

Asked by Andrey

Running all the components on a single machine on a public network with many other computers and servers that I cannot interfere with (64.32.x.x addresses). I'm creating VMs on the private subnet 192.168.2.0/24 with FlatDHCP networking mode. VMs are booting fine but because of complaints from other on the network, and after checking the syslog file, turns out that the DHCP server that is running provding addresses to the VMs is also responding to other DHCP requests on the public (BAD!) network. How can a fix this so it only responds to the VM instances?

root@cgs04:/var/log# cat /etc/nova/nova.conf
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--sql_connection=mysql://nova:n0va@127.0.0.1/nova
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--network_manager=nova.network.manager.FlatDHCPManager
--flat_interface=eth0
--flat_injected=false
--flat_network_dhcp_start=192.168.2.2
--fixed_range=192.168.2.0/24
--network_size=256

root@cgs04:~# nova-manage network list
network netmask start address DNS
192.168.2.0/24 255.255.255.0 192.168.2.2 8.8.4.4

root@cgs04:~# ps aux | grep dnsmasq
nobody 1413 0.0 0.0 21688 1072 ? S 13:35 0:00 dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-lease-max=253 --dhcp-no-override
nobody 1697 0.0 0.0 24388 1132 ? S 13:37 0:00 dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-br100.pid --listen-address=192.168.2.1 --except-interface=lo --dhcp-range=192.168.2.2,static,120s --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
root 1698 0.0 0.0 24256 412 ? S 13:37 0:00 dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-br100.pid --listen-address=192.168.2.1 --except-interface=lo --dhcp-range=192.168.2.2,static,120s --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
root 2446 0.0 0.0 9136 1064 pts/0 S+ 13:49 0:00 grep --color=auto dnsmasq

root@cgs04:~# euca-describe-instances
RESERVATION r-20b0ydpj adminProject default
INSTANCE i-00000001 ami-691e370f 64.32.63.36 192.168.2.2 running mykey (adminProject, cgs04) 0 m1.small 2011-09-22T20:37:42Z nova

root@cgs04:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet 169.254.169.254/32 scope link lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:22:19:59:f3:0c brd ff:ff:ff:ff:ff:ff
    inet 64.32.63.36/32 scope global eth0
    inet6 fe80::222:19ff:fe59:f30c/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:22:19:59:f3:0a brd ff:ff:ff:ff:ff:ff
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 2a:60:95:62:4f:3b brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
6: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:22:19:59:f3:0c brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.1/24 brd 192.168.2.255 scope global br100
    inet 64.32.63.4/24 brd 64.32.63.255 scope global br100
    inet6 fe80::cbd:73ff:fe7a:bb19/64 scope link
       valid_lft forever preferred_lft forever
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether fe:16:3e:79:f2:df brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fe79:f2df/64 scope link
       valid_lft forever preferred_lft forever

root@cgs04:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# Main Interface
auto eth0
iface eth0 inet static
  address 64.32.63.4
  netmask 255.255.255.0
  gateway 64.32.63.254
  post-up /sbin/ifconfig eth0 promisc

Thanks!!!
Andrey

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Andrey (andpol28325) said :
#2

Anyone?
On Oct 8, 2011 2:28 AM, "Launchpad Janitor" <
<email address hidden>> wrote:

> Your question #172061 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/172061
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>
> --
> If you're still having this problem, you can reopen your question either
> by replying to this email or by going to the following page and
> entering more information about your problem:
> https://answers.launchpad.net/nova/+question/172061
>
> You received this question notification because you asked the question.
>

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Andrey (andpol28325) said :
#4

Reopen
On Oct 25, 2011 2:11 AM, "Launchpad Janitor" <
<email address hidden>> wrote:

> Your question #172061 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/172061
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>
> --
> If you're still having this problem, you can reopen your question either
> by replying to this email or by going to the following page and
> entering more information about your problem:
> https://answers.launchpad.net/nova/+question/172061
>
> You received this question notification because you asked the question.
>

Revision history for this message
Launchpad Janitor (janitor) said :
#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Andrey (andpol28325) said :
#6

Open again.
On Oct 8, 2011 2:28 AM, "Launchpad Janitor" <
<email address hidden>> wrote:

> Your question #172061 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/172061
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>
> --
> If you're still having this problem, you can reopen your question either
> by replying to this email or by going to the following page and
> entering more information about your problem:
> https://answers.launchpad.net/nova/+question/172061
>
> You received this question notification because you asked the question.
>

Revision history for this message
Vish Ishaya (vishvananda) said :
#7

Nova's dnsmasq will only respond to requests in its conf file. It is the default libvirt network that is responding to other machines. You can destroy the default network like so:

virsh net-destroy default
virsh net-autostart default --disable

Can you help with this problem?

Provide an answer of your own, or ask Andrey for more information if necessary.

To post a message you must log in.