<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Thanks for the reply, Simon.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">
How would I do that?</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I already use the --dhcp-host option to allocate IP addresses by MAC address for certain clients but these are all machines with just one IP address on one VLAN. How would I allocate static IP addresses to these access points when they require a different IP address per VLAN but all with the same MAC address? Each VLAN is associated with a LAN bridge on the machine running dnsmasq and I allocate DHCP addresses to the different VLANs using the tag option in the --dhcp-range statements - for example: <span style="color:rgb(0,0,0);font-size:12px;font-family:arial">dhcp-range=tag:br3,10.10.70.101,10.10.70.200,255.255.255.0,1440m. This works fine. But I can't see how to allocate static IP addresses based on VLAN membership.</span></div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="color:rgb(0,0,0);font-size:12px;font-family:arial"><br></span></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="color:rgb(0,0,0);font-size:12px;font-family:arial">Am I missing something obvious?</span></div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="color:rgb(0,0,0);font-size:12px;font-family:arial"><br></span></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="color:rgb(0,0,0);font-size:12px;font-family:arial">Cheers</span></div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="color:rgb(0,0,0);font-size:12px;font-family:arial"><br></span></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="color:rgb(0,0,0);font-size:12px;font-family:arial">David</span></div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 24 June 2014 22:30, Simon Kelley <span dir="ltr"><<a href="mailto:simon@thekelleys.org.uk" target="_blank">simon@thekelleys.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">On 24/06/14 10:08, David Joslin wrote:<br>
> I have a wireless network split into several vlans, each with its own<br>
> subnet, with dnsmasq serving all vlans. The wireless network is a Ubiquti<br>
> Unifi system and the access points all have static IP addresses on the<br>
> management vlan. Additionally, the access points each request IP addresses<br>
> via DHCP for the other vlans and dnsmasq correctly allocates the IP<br>
> addresses for the relevant vlans.<br>
><br>
> I noticed in dnsmasq's logs recently a bunch of 'lease not found' messages<br>
> whenever the access points attempted to renew the leases for these<br>
> addresses. The cause seems to be this: an access point's IP addresses are<br>
> all used on the same interface on the access point so when it renews these<br>
> addresses, the requests all come from the same mac address. Dnsmasq<br>
> services these requests but only the last address allocated is stored in<br>
> the lease file (I'm assuming the other addresses allocated are briefly<br>
> stored but then overwritten by subsequent allocations). So the access<br>
> points are happy enough - they have the addresses they need correctly<br>
> allocated by dnsmasq - but dnsmasq's lease file only records the last<br>
> address allocated. When the access points renew the leases, dnsmasq<br>
> generates the 'lease not found' error because there's no record of the<br>
> allocation in the lease file.<br>
><br>
> The error messages themselves are no big deal and the access points do get<br>
> the correct addresses. The problem I can foresee is that dnsmasq might<br>
> allocate addresses to other clients that it has already allocated to the<br>
> access points because it has no record of those allocations in its lease<br>
> file.<br>
><br>
> Is there any way dnsmasq can record more than 1 IP address against a mac<br>
> address? Or is there any other way round this problem? The access points<br>
> don't give any options for IP configuration apart from the address on the<br>
> management vlan; there aren't any configuration options for these DHCP<br>
> requested addresses.<br>
<br>
</div></div>The obvious way to fix this would be to have the access points supply a<br>
different client-id for each VLAN. Client-ids trump MAC addresses as<br>
unique identifiers for leases. The lack of configuration options would<br>
seem to preclude that, however.<br>
<br>
You could at least solve the worry about having access point addresses<br>
re-allocated by giving them static addresses on each VLAN, associated<br>
with the MAC address.<br>
<br>
Cheers,<br>
<br>
<br>
Simon.<br>
<div class=""><br>
<br>
<br>
<br>
><br>
> Any help would be greatly appreciated.<br>
><br>
> David<br>
><br>
><br>
><br>
</div>> _______________________________________________<br>
> Dnsmasq-discuss mailing list<br>
> <a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
> <a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" target="_blank">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br>
><br>
<br>
<br>
_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" target="_blank">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br>
</blockquote></div><br></div></div>