With this patch the dnsmasq init script manages resolv.conf if and only if
when dnsmasq will listen on 127.0.0.1#53 (is main resolver instance).
Also adds ::1 to the resolver file.
For unbound a likewise patch exists (PR#4454).
Fixes (combined with the unbound PR) FS#785
Signed-off-by: Paul Oranj
On Sat, Jun 17, 2017 at 7:35 AM, Felix Fietkau wrote:
> On 2017-06-16 20:58, Matthew McClintock wrote:
>> This will output when a job starts and stops:
>>
>> $ make -j24 V=e
>> [ snip ]
>> make[3] -C package/network/config/firewall compile
>> make -r -C package/network/config/firewall
>> BUILD_
When an external kernel tree is used the version should not get
modified by the LEDE build scripts. This was added by Florian some time
ago.
The commit 0aed054becb21439 ("build: add KERNEL_MAKE and
KERNEL_MAKE_FLAGS variables and move to kernel.mk") breaks this feature
introduced in b6746a6ffb73 ("
Not completely related, but it came to my mind a couple of days ago
and maybe you can share your opinion:
Shouldn't we also be setting CONFIG_LOCALVERSION if *not* using an
external kernel, to indicate that this is *not* a vanilla kernel.org
codebase but actually got tons of OpenWrt/LEDE patches on
Le 06/18/17 à 14:27, Hauke Mehrtens a écrit :
> When an external kernel tree is used the version should not get
> modified by the LEDE build scripts. This was added by Florian some time
> ago.
> The commit 0aed054becb21439 ("build: add KERNEL_MAKE and
> KERNEL_MAKE_FLAGS variables and move to kerne
Le 06/18/17 à 14:44, Daniel Golle a écrit :
> Not completely related, but it came to my mind a couple of days ago
> and maybe you can share your opinion:
> Shouldn't we also be setting CONFIG_LOCALVERSION if *not* using an
> external kernel, to indicate that this is *not* a vanilla kernel.org
> cod
Hello,
Upgrade process with LEDE/OpenWrt installations aren't as smooth as a
user would expect. I know that PC have a lot more resources but their
upgrade process is normally very straightforward. They can upgrade
thousands of packages with little to no intervention.
On LEDE, it is normally not f
Hei folks,
I've some issues setting up a tagged vlan on a TP-Link 841n v9 router.
The vlan (tag 23) should spawn all ports (lan, wan) having a dedictated
interface.
For doing so in luci I add a new vlan, name it 23 and enable all
drop-down boxes (incl. cpu) as checked.
After applying, the system