Bastian Bittorf

This is reproducible on x86_64 OpenWRT, with a snapshot from https://downloads.openwrt.org/snapshots/targets/x86/64/ bringup the system, e.g. "OpenWrt SNAPSHOT, r20337-a66f843971" ``` qemu-system-x86_64 \ -net nic -enable-kvm \ -hda openwrt-x86-64-generic-squashfs-rootfs.img \ -kernel openwrt-x86-64-generic-kernel.bin...

here it works with e.g.: host=pp0* version is: Icinga Web 2 Version | 2.10.1

This it *not* an oops, but a WARNING.

I can confirm that. Archer C6U v1, OpenWRT trunk r20332 and r20519 ``` [ 56.852678] mt7615e 0000:02:00.0: Message 000026ed (seq 7) timeout [ 77.332674] mt7615e 0000:02:00.0: Message 000025ed (seq 8)...

``` # tested with snapshot r20539...r20813 (and earlier): $ echo 1 >/sys/kernel/debug/ieee80211/phy1/mt76/fw_debug $ wifi up # next command hangs for ~16 sec: $ echo 1 >/sys/kernel/debug/ieee80211/phy1/mt76/fw_debug $ dmesg [47859.318557] ieee80211...

i'am against it. it's easier for me to follow in this special field and i dont want to read all the messages from packages.

so does this mean, that instead of using the uniq ID i can reference with any of the 'local_addresses'?

"A node might be referenced one time with an id and another time with one of its aliases. In such a case netdiff would consider the topology changed." Is this...

I also think referencing only IDs is the way to go. Thanks a lot for your work!

this can be a command line option with e.g. ``` --checkstyle default|lazy|agressive ``` with different settings. Ofcourse the coding style differs from project to project, but we can at least...