[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: avahi-daemon allow/deny interfaces question



On 7/15/22 00:31, Ram Ramesh wrote:
On 7/14/22 09:15, Ram Ramesh wrote:
Hi Ramesh,

There are numerous reports (mostly old, afaics) of the issue you describe, but with various suggested reasons.

I suspect the avahi related part is a consequence rather than a cause - I didn't think avahi was capable of disabling interfaces, the message looks like it's updating a table/list (etc) and "...no longer relevant..." messages appear in my syslog if I deliberately disconnect from wifi.

Please can you provide syslog extracts from just before and during a time when this has happened, using:

$ sudo cat /var/log/syslog | grep -i -E "avahi|network"
(must be capital -E and no spaces around the | inside the speech marks)

Is there anything that seems relevant in

$ sudo dmesg -T

?

Out of interest, did you try running for a while with just the power management tweak?

Thanks,
Gareth
Yes, I believe I did. I did not use /sys/... power/control method. Instead, I kept the network alive by "ping -i 60 <ext-gateway>". However, I am not 100% sure of this. So, I will revert some of my changes and get you the relevant logs.

Thanks for your continued interested in this matter.

Regards
Ramesh

Mmm... It has been about 10 hours since my reboot after removing "deny-interfaces=$extif," and I have not had the earlier issue of interface disappearing. I will let it run overnight to see. However, I think I wont be able to reproduce the problem.

Earlier, I was trying to keep the interface alive with "ping -i 60 xxx"  instead of setting "/sys/usb/.... power/control" to "on". Not sure if that was not enough and $extif actually powered off in between pings and avahi-daemon was simply reporting this in daemon.log. However, kernel reset the interface status and (may be) dhclient was not written to handle this sort of issue. So, it simply could not work with the interface anymore as it was not initialized to perform DHCP. I wonder why this did not affect ping as it was chugging along without any issues. That is too many wild guesses and I am not sure why the problem does not exists now.

I will update again later tomorrow when it has run another 12+ hours.

Regards
Ramesh


No issues still. So, I will call this done for now and report again, if this shows up after a few days.

Regards
Ramesh


Reply to: