Please see :
root@r-6143-VMAMS:~# grep -v '^#\|^$' /etc/dnsmasq.conf
domain-needed
bogus-priv
resolv-file=/etc/dnsmasq-resolv.conf
local=/shape.host/
except-interface=eth1
except-interface=eth2
except-interface=lo
no-dhcp-interface=eth1
no-dhcp-interface=eth2
expand-hosts
domain=shape.host
domain=shape.host
domain=shape.host
dhcp-range=217.79.xxx.129,static
dhcp-hostsfile=/etc/dhcphosts.txt
dhcp-ignore=tag:!known
dhcp-option=15,"shape.host"
dhcp-option=vendor:MSFT,2,1i
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/opt/tftpboot
dhcp-lease-max=2100
domain=shape.host
log-facility=/var/log/dnsmasq.log
conf-dir=/etc/dnsmasq.d
dhcp-optsfile=/etc/dhcpopts.txt
localise-queries
dhcp-option=option:router,217.79.xxx.129
dhcp-option=6,217.79.xxx.130,8.8.8.8
dhcp-client-update
root@r-6143-VMAMS:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 1e:00:e4:00:00:64 brd ff:ff:ff:ff:ff:ff
altname enp3s0
altname ens160
inet 217.79.xxx.130/25 brd 217.79.xxx.255 scope global eth0
valid_lft forever preferred_lft forever
inet 23.227.xxx.35/27 brd 23.227.xxx.63 scope global eth0
valid_lft forever preferred_lft forever
inet 217.79.xxx.12/28 brd 217.79.xxx.15 scope global eth0
valid_lft forever preferred_lft forever
inet 66.165.xxx.92/29 brd 66.165.xxx.95 scope global eth0
valid_lft forever preferred_lft forever
inet 217.79.xxx.28/29 brd 217.79.xxx.31 scope global eth0
valid_lft forever preferred_lft forever
inet 190.102.xxx.116/29 brd 190.102.xxx.119 scope global eth0
valid_lft forever preferred_lft forever
inet 66.206.xxx.179/29 brd 66.206.xxx.183 scope global eth0
valid_lft forever preferred_lft forever
inet 23.29.xxx.130/27 brd 23.29.xxx.159 scope global eth0
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 02:07:00:ef:01:23 brd ff:ff:ff:ff:ff:ff
altname enp11s0
altname ens192
inet 10.102.0.152/24 brd 10.102.0.255 scope global eth1
valid_lft forever preferred_lft forever
root@r-6143-VMAMS:/etc/dnsmasq.d# ls
cloud.conf README
root@r-6143-VMAMS:/etc/dnsmasq.d# cat cloud.conf
listen-address=127.0.0.1,23.29.xxx.130
dhcp-range=set:interface-eth0-0,23.29.xxx.130,static
dhcp-option=tag:interface-eth0-0,15,shape.host
dhcp-option=tag:interface-eth0-0,6,23.29.xxx.130,8.8.8.8
dhcp-option=tag:interface-eth0-0,3,23.29.xxx.129
dhcp-option=eth0,26,1500
dhcp-option=tag:interface-eth0-0,1,255.255.255.224
root@r-6143-VMAMS:/etc/dnsmasq.d#
Regards,
Cristian
-----Original Message-----
From: Wei ZHOU <ustcweiz...@gmail.com>
Sent: Thursday, October 19, 2023 11:24 PM
To: users@cloudstack.apache.org
Subject: Re: dnsmasq-dhcp - ignored
Can you share /etc/dnsmasq.conf and /etc/dnsmasq.d/*?
AND the output of "ip a"?
-Wei
在 2023年10月19日星期四，Cristian Ciobanu <cristian.c@istream.today> 写道：
> Hi Wei,
>
>
>
> I use shared network without security groups. I did a cleanup and same
> issue after. I have shared network and advanced in multiple different
> zones, but only in one zone I have this issue. I think it started
> suddenly after a deploy.
>
> Here is a tcpdump from router, looks how ignore still. I turn off and
> change to a different IP, and then I turn on and the IP is allocated.
>
> Request with ignored request for IPs from this range 23.227.xxx.32/27:
>
> 19:44:20.453093 1e:00:d5:00:00:79 > ff:ff:ff:ff:ff:ff, ethertype IPv4
> (0x0800), length 334: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP,
> Request from 1e:00:d5:00:00:79, length 292
>
> 19:44:24.319207 1e:00:d5:00:00:79 > ff:ff:ff:ff:ff:ff, ethertype IPv4
> (0x0800), length 334: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP,
> Request from 1e:00:d5:00:00:79, length 292
>
> 19:44:28.051571 1e:00:d5:00:00:79 > ff:ff:ff:ff:ff:ff, ethertype IPv4
> (0x0800), length 334: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP,
> Request from 1e:00:d5:00:00:79, length 292
>
> 19:44:35.599400 1e:00:d5:00:00:79 > ff:ff:ff:ff:ff:ff, ethertype IPv4
> (0x0800), length 334: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP,
> Request from 1e:00:d5:00:00:79, length 292
>
> 19:44:52.334213 1e:00:d5:00:00:79 > ff:ff:ff:ff:ff:ff, ethertype IPv4
> (0x0800), length 334: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP,
> Request from 1e:00:d5:00:00:79, length 292
>
>
>
>
>
> And same instance after I turn off and change again the IP/ turn on.
> Here
> works:
>
>
>
> 19:48:38.224138 1e:00:d5:00:00:79 > ff:ff:ff:ff:ff:ff, ethertype IPv4
> (0x0800), length 334: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP,
> Request from 1e:00:d5:00:00:79, length 292
>
> 19:48:38.224432 1e:00:19:00:00:64 > 1e:00:d5:00:00:79, ethertype IPv4
> (0x0800), length 352: 23.29.xxx.130.67 > 23.29.xxx.131.68: BOOTP/DHCP,
> Reply, length 310
>
> 19:48:38.235802 1e:00:d5:00:00:79 > ff:ff:ff:ff:ff:ff, ethertype IPv4
> (0x0800), length 346: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP,
> Request from 1e:00:d5:00:00:79, length 304
>
> 19:48:38.237614 1e:00:19:00:00:64 > 1e:00:d5:00:00:79, ethertype IPv4
> (0x0800), length 352: 23.29.xxx.130.67 > 23.29.xxx.131.68: BOOTP/DHCP,
> Reply, length 310
>
>
> So, it is quite strange because I am ignoring multiple IPs. Now, if I
> restart VMs which have IPs from this range 23.227.xxx.32/27, they are
> going to be ignored at boot to get the IP. I have already tested this with a
> few.
> I also have this issue with a different class.
>
>
> Thank you,
>
> Cristian
>
>
>
>
>
> On Thu, Oct 19, 2023, 20:45 Wei ZHOU <ustcweiz...@gmail.com <mailto:
> ustcweiz...@gmail.com> > wrote:
>
> Hi,
>
> Do you use shared network with security groups? Can you restart
> network with cleanup and retry?
>
> -Wei
>
> 在 2023年10月19日星期四， <cristian.c@istream.today> 写道：
>
> > Hello,
> >
> >
> >
> > I'm experiencing strange issue, the Guest router started today to
> ignore
> > the requests for specific IP class.
> >
> > Oct 19 16:22:49 dnsmasq-dhcp[24437]: 49204406 available DHCP subnet:
> > 217.79.xxx.129/255.255.255.128 <http://255.255.255.128>
> >
> > Oct 19 16:22:49 dnsmasq-dhcp[24437]: 49204406 available DHCP subnet:
> > 66.206.xxx.179/255.255.255.248 <http://255.255.255.248>
> >
> > Oct 19 16:22:49 dnsmasq-dhcp[24437]: 49204406 client provides name:
> ubuntu
> >
> > Oct 19 16:22:49 dnsmasq-dhcp[24437]: 49204406 DHCPDISCOVER(eth0)
> > 1e:00:30:00:04:67 ignored
> >
> > Oct 19 16:23:53 dnsmasq-dhcp[24437]: 49204406 available DHCP subnet:
> > 217.79.xxx.129/255.255.255.128 <http://255.255.255.128>
> >
> > Oct 19 16:23:53 dnsmasq-dhcp[24437]: 49204406 available DHCP subnet:
> > 66.206.xxx.179/255.255.255.248 <http://255.255.255.248>
> >
> > Oct 19 16:23:53 dnsmasq-dhcp[24437]: 49204406 client provides name:
> ubuntu
> >
> > Oct 19 16:23:53 dnsmasq-dhcp[24437]: 49204406 DHCPDISCOVER(eth0)
> > 1e:00:30:00:04:67 ignored
> >
> >
> >
> >
> >
> > root@r-6137-VMAMS:~# cat /etc/dhcphosts.txt | grep "1e:00:30:00:04:67"
> >
> > 1e:00:30:00:04:67,23.227.xxx.54,testignore001,infinite
> >
> >
> >
> > root@r-6137-VMAMS:~# cat /etc/dhcphosts.txt | wc -l
> >
> > 144
> >
> >
> >
> > If I reboot any VM with an IP from this class 23.227.xxx.129, which
> > was allocated without any issue before, after reboot is I'm going to
> > see ignored and is going to be left without IP assigned.
> >
> > Setup: ACS 4.18.1 upgrade from previous version with VMware.
> >
> > Any suggestions?
> >
> > Thank you.
> >
> >
>
>
