-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IP addresses change does not trigger update in browser #235
Comments
I narrowed this down to #228, cc @mattsaxon, I'll try to see if there's something obvious that I can fix quickly. |
I think this is because |
It’s is sort of by design that it doesn’t change with a changed IP address. We do need to change it so it triggers on SRV update though so I do appreciate this is both a regression and needs fixing, but I’d rather forward fix it to trigger on the SRV change as you suggest. |
Just so I understand – is it by design in relation to any part of RFC 6762 or 6763? |
Sorry, no I meant that the code was never designed to deal with an IP address change. The older code just got ‘lucky’, presumably |
Assign this and the other regression to |
I should have forward fix available by end of today |
There is a possibility that my fix here is a breaking change as UpdateService used to get called on service addition. I feel this is wrong and was a mistake. |
Yeah I noticed that too, I agree this seems wrong and I'd say let's fix this. |
Fix released in version 0.26.0. |
Steps to reproduce
exp: An update message is printed.
act: Nothing is printed
Notes:
zeroconf version: 0.24.5
python version: 3.6.7
The text was updated successfully, but these errors were encountered: