There are internal decisions being made using several bridge attributes
like for example in bridge_reload(), but those attributes are not
available for the outside inspection, thus hard to follow.
So lets make inspection easier and simply just add dumping of those
bridge attributes as well.
In some cases we see, that the bridge configuration was applied, but its
not exactly clear why it was done, so lets add a simple debugging output
which should provide currently missing clue.
Signed-off-by: Petr Štetiar
---
bridge.c | 14 ++
1 file changed, 10 insertions(+), 4
Hi,
while debugging some bridge configuration issue I wasnt able to get a complete
picture of the bridge configuration handling inside netifd out of the box, so
I would like to propose following two relatively small changes which helped me
better understand netifd internals by using just a
On Fri, Mar 10, 2023 at 2:21 AM Petr Štetiar wrote:
>
> Tim Harvey [2023-03-09 12:19:24]:
>
> Hi,
>
> > Is there any reason to move them into target/linux/generic/backport-5.15?
>
> sorry for confusing you, but I've just meant to rename the patch files itself,
> so they contain bacported kernel
Hi Vladimir,
Thank you for having a look at this!
On 06.03.2023 14:46, Vladimir Oltean wrote:
On Sat, Mar 04, 2023 at 01:52:32PM +0300, Arınç ÜNAL wrote:
On 4.03.2023 00:48, Jan Hoffmann wrote:
This series fixes multiple issues related to the L2 table and multicast
table. That includes an
Hi,
it looks like there is a bug in ddns-scripts. In dynamic_dns_updater.sh:
70 case "$1" in
71 start)
72 if [ -n "$NETWORK" ]; then
73 start_daemon_for_all_ddns_sections "$NETWORK"
74 exit 0
75
Tim Harvey [2023-03-09 12:19:24]:
Hi,
> Is there any reason to move them into target/linux/generic/backport-5.15?
sorry for confusing you, but I've just meant to rename the patch files itself,
so they contain bacported kernel version in their filename, making the patch
origin explicit as it
