sysntpd server becomes unavailable if the index of the bound
interface changes. So let's add an interface trigger to reload sysntpd.
This patch also adds the ability for the sysntpd script to handle
uci interface name from configuration.
Fixes: 4da60500ebd2 ("busybox: sysntpd: option to bind
I'm using a TP-Link Archer C7 v2 router. For every build, I do update my
sandbox with the current OpenWrt repository and the feeds. The first not
working build from 27.05. shows in Luci:
OpenWrt SNAPSHOT r16834-53b9cc442f / LuCI Master git-21.147.31971-74be304
Related to the changes to bridge
On 5/29/21 10:25 PM, e9hack wrote:
Hi,
it looks like that Luci->Network->Interfaces is broken. It shows a
NotFountError (Resource not found) message. My build from 22.05. forces
me to convert something related to network configuration. Afterwards,
this dialogue shows the interface
Hi,
it looks like that Luci->Network->Interfaces is broken. It shows a
NotFountError (Resource not found) message. My build from 22.05. forces me to convert
something related to network configuration. Afterwards, this dialogue shows the
interface configuration. Starting with build from 27.05.
On 5/29/21 5:25 PM, Rafał Miłecki wrote:
From: Rafał Miłecki
Problem with handling all migrations in 1 step is that uci.sections()
doesn't include changes queued using uci.callAdd() and uci.callSet().
That could result in unexpected behaviour and generating invalid
configs.
For the sake of
From: Rafał Miłecki
Problem with handling all migrations in 1 step is that uci.sections()
doesn't include changes queued using uci.callAdd() and uci.callSet().
That could result in unexpected behaviour and generating invalid
configs.
For the sake of simplicity and reliability use 2 steps
Without this patch we first migrate the configuration to the br-lan
device entry and change the device option of the network interface to
point to the newly created device. In the next step all device options
will be overwritten with the ifname entry, this partly reverted the
change from the
