The testing is on a single device, where MAC address is the same for both vlan9 and vlan19. Hence, the release packet is reaching to server." ?
On Thu, Aug 10, 2023 at 2:05 AM <wkitt...@gmail.com> wrote: > On 8/9/23 10:58 AM, shashikumar Shashi wrote: > > 2) Put the client on vlan9. Client gets IP from vlan9 pool (e.g. > 192.168.9.10) > > by executing “dhclient -4 eth1”. > > > > 3) Put the same client on vlan19. Client releases previously acquired IP > (e.g. > > 192.168.9.10) by executing “dhclient -4 eth1 -r”. > > > > 4) The same client tries to get the IP by executing “dhclient -4 eth1”. > > > my question is if step 3's release is done before the client is actually > moved > to the new network... > > if no, does the client actually transmit the release to the server? if it > does, > how does that release packet get to the original server if the client is > now on > a different network? > > admittedly, these questions may not matter due to the apparent nature of > the > possible bug being discussed... i may also be being too simplistic and > somewhat > ignorant of how a DHCP address release really works... > > -- > NOTE: No off-list assistance is given without prior approval. > *Please keep mailing list traffic on the list unless* > *a signed and pre-paid contract is in effect with us.* > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
