On Sun, Aug 06, 2023 at 01:24:02AM +0300, 0zl wrote: > On 8/4/23 09:24, shashikumar Shashi wrote: > > Hi, > > > > Observing that dnsmasq is offering DHCP IP to the client } } Observing that dnsmasq is offering DHCP IP-address to the client > > from a vlan pool which is in DOWN state. > > > > E.g. If there are 3 dhcp pools > > > > vlan9 (State UP) : Range: 192.168.9.1-192.168.9.254 > > vlan19 (State UP): Range: 192.168.19.1-192.168.19.254 > > vlan99 (State DOWN): Range: 192.168.99.1-192.168.99.254 > > > > 1) Client on vlan9 gets IP from vlan9 pool > > 2) Client moves to vlan19, releases IP
Acknowledge on "Client moves". The 'releases IP' is probably something like "I'm unaware that IP stands for Internet Protocol and want to try how far I can get by being vague how the release of the DHCP lease was done" > > 3) Client on vlan19 requests IP --> dnsmasq offers IP 192.168.99.xx from > > vlan99 pool (incorrect pool), instead of vlan19 pool. > > > > If the vlan99 is in UP state, then dnsmasq offers the IP from the vlan19 > > pool (the correct pool). > > > > Has anyone come across such an issue? > > > I've encountered this issue as well, The issue of moving clients, the issue of interfaces go down and come up, the issue of moving clients AND flipping interfaces? > I ended up working around it by creating bridges that have those vlans > as their bridge port. This way the bridge stays up to dnsmasq even > when I take one of these vlans down. That deals only with keeping interfaces present to dnsmasq. Nothing about a moving client. Thing is that poor problem descriptions do not contribute to improvement. Not your mom _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
