Recent (20190207) changes to odhcpd makee it dependent on OpenWrt
logical interfaces. Boot time race conditions may make odhcpd binding
a challenge. Intermittent or inconsistent problems can occur with DHCP
requests until odhcpd is restarted. Change start up scripts to use
procd interface
> Op 23 feb. 2019, om 03:17 heeft Yousong Zhou het
> volgende geschreven:
>
> This makes it clear that localuse when explicitly specified in the
> config will have its final say on whether or not the initscript should
> touch /etc/resolv.conf, no matter whatever the result of previous
>
> Op 23 feb. 2019, om 03:17 heeft Yousong Zhou het
> volgende geschreven:
>
> 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
On 2/23/19 4:36 PM, Dave Taht wrote:
> Hauke Mehrtens writes:
>
>> On 2/13/19 11:51 PM, Felix Fietkau wrote:
>>> On 2019-02-13 23:15, Hauke Mehrtens wrote:
This will build all executable as Position Independent Executables (PIE)
by default. PIE executable can make full use of Address
Hauke Mehrtens writes:
> On 2/13/19 11:51 PM, Felix Fietkau wrote:
>> On 2019-02-13 23:15, Hauke Mehrtens wrote:
>>> This will build all executable as Position Independent Executables (PIE)
>>> by default. PIE executable can make full use of Address Space Layout
>>> Randomization (ASLR) because
On Sat, Feb 23, 2019 at 3:17 AM Yousong Zhou wrote:
>
> This makes it clear that localuse when explicitly specified in the
> config will have its final say on whether or not the initscript should
> touch /etc/resolv.conf, no matter whatever the result of previous
> guesswork would be
>
> (cherry
On Sat, Feb 23, 2019 at 3:17 AM 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
This adds the support-list entry the AVM FRITZ!Box 4020 expects in the
ar71xx target to allow non-forced sysupgrades from ar71xx to ath79.
Signed-off-by: David Bauer
---
target/linux/ath79/image/generic.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ath79/image/generic.mk
