> Op 22 feb. 2019, om 03:05 heeft Yousong Zhou het
> volgende geschreven:
>
> On Tue, 19 Feb 2019 at 23:02, Paul Oranje wrote:
>>
>> Op 18 feb. 2019, om 21:50 heeft Hans Dedecker het
>> volgende geschreven:
>>>
>>> On Mon, Feb 18, 2019 at 3:18 PM Yousong Zhou wrote:
Currently
On Tue, 19 Feb 2019 at 23:02, Paul Oranje wrote:
>
> Op 18 feb. 2019, om 21:50 heeft Hans Dedecker het
> volgende geschreven:
> >
> > On Mon, Feb 18, 2019 at 3:18 PM Yousong Zhou wrote:
> >>
> >> Currently it seems impossible to configure /etc/config/dhcp to achieve
> >> the following use case
Op 18 feb. 2019, om 21:50 heeft Hans Dedecker het volgende
geschreven:
>
> On Mon, Feb 18, 2019 at 3:18 PM Yousong Zhou wrote:
>>
>> Currently it seems impossible to configure /etc/config/dhcp to achieve
>> the following use case
>>
>> - run dnsmasq with no-resolv
>> - re-generate /etc/resolv
On Mon, Feb 18, 2019 at 3:18 PM Yousong Zhou wrote:
>
> Currently it seems impossible to configure /etc/config/dhcp to achieve
> the following use case
>
> - run dnsmasq with no-resolv
> - re-generate /etc/resolv.conf with "nameserver 127.0.0.1"
>
> Before this change, we have to set resolvfile
Currently it seems impossible to configure /etc/config/dhcp to achieve
the following use case
- run dnsmasq with no-resolv
- re-generate /etc/resolv.conf with "nameserver 127.0.0.1"
Before this change, we have to set resolvfile to /tmp/resolv.conf.auto
to achive the 2nd effect above, but settin
