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. > >
