If a dead AvahiEntry cleanup is scheduled, and we try to schedule
another one, defer the existing callback by 1s. Also remove other calls
to avahi_cleanup_dead_entries.
This is done to ensure that an entry stays in the dead state for at
least 1 second, so that if we receive a copy of our own probe we don't
think it's a conflict.
This should resolve issues where on startup the server spuriously
conflicts with itself and renames to hostname-2, hostname-3, etc. This
typically happens as addresses are rapidly added and removed, e.g. when
IPv6 global addresses cause the link local address to be revoked.
Ideally to prevent excess memory usage we would track the age of the
entries and expire them sooner to prevent the schedule being deferred
forever on a busy server.
Fix from upstream: 0a536f6082
- sync IPv4/IPv6 infos in two steps (wl first, then wired devices)
- do not touch wds
- fix some visual problems showing wireless clients as a lan client
tested with DHCPv6 and IPv6 Tunnel, working correct now :)
Note: update for the following commit
455984a762
Note: FIX me / Workaround for SDK7: mac addr return value may be wrong (??) for 2nd vif after router (re-) boot --> no internet connection. After clicking save on basic-network page everything will work (again)!
--> catch that case and adjust mac to our wl configuration before we set bridge address
reported & tested by pedro :)
tested with R7000 and RT-N18U, working correct
Note: update from 2018/2019 to 2020/2021 (latest src). ctf update part 2 has been VERY stable but lets update once more :)
lancethepants
pedro
M_ars