On 29/03/13 15:37, Kevin Darbyshire-Bryant wrote:
Ahh, but there's the rub, the first instance of dhcp-option=br0,...
is generated automatically by the router software and cannot be changed,
it's why we need to be able to override it.
Ok. will have to think harder about this, in that case
>> Ahh, but there's the rub, the first instance of dhcp-option=br0,...
>> is generated automatically by the router software and cannot be changed,
>> it's why we need to be able to override it.
>
> Ok. will have to think harder about this, in that case.
>
Sorry!
>> But I'm now concerned about
On 28/03/13 16:02, Kevin Darbyshire-Bryant wrote:
On 28/03/2013 13:42, Simon Kelley wrote:
On 28/03/13 13:14, Kevin Darbyshire-Bryant wrote:
On 28/03/2013 12:58, Simon Kelley wrote:
On 28/03/13 12:26, Kevin Darbyshire-Bryant wrote:
I'm led to believe that v2.61 behaves as 'last instance stick
kelleys.org.uk [mailto:dnsmasq-
> discuss-boun...@lists.thekelleys.org.uk] On Behalf Of Kevin Darbyshire-
> Bryant
> Sent: Wednesday, March 27, 2013 11:41 PM
> To: dnsmasq-discuss@lists.thekelleys.org.uk
> Subject: [Dnsmasq-discuss] Config file behaviour - change/bug/feature -
> commen
On 27/03/13 20:10, Kevin Darbyshire-Bryant wrote:
On 27/03/2013 17:40, Kevin Darbyshire-Bryant wrote:
Hi Simon,
Right, now that I've had the problem further clarified to me, here's the
real issue.
In essence, dnsmasq when parsing options uses the values from the first
instance of a paramete
On 27/03/2013 17:40, Kevin Darbyshire-Bryant wrote:
> Hi Simon,
>
Right, now that I've had the problem further clarified to me, here's the
real issue.
In essence, dnsmasq when parsing options uses the values from the first
instance of a parameter and not (as before) the last.
Bug? Feature? Co
Hi Simon,
As previously mentioned I got 2.66test16 into a recent version of Tomato
router firmware which means it's now out in the wild and being used. An
obscure corner case change in behaviour has been observed, relating to
disabling and then re-enabling dhcp service on an interface, and
specif