-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
HAOS 14.0 wiped out network #3717
Comments
Restored a VM backup and worked, so going to close this and assume it was something unrelated to HAOS |
I have the same issue, any other way to repair without restoring VM backup? |
I couldn't find a way =( Ended up restoring from a backup
…On Thu, Dec 5, 2024 at 9:37 PM matvit92 ***@***.***> wrote:
I have the same issue, any other way to repair without restoring VM backup?
—
Reply to this email directly, view it on GitHub
<#3717 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5OBT4QDOLJJZJNCUZRYXNL2EEEWZAVCNFSM6AAAAABTAP4752VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRRHE3DCNJTGA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
I solved it now after 4 hours. It was reset complete network settings, which i tried to configure using nmcli (set ipv4, disable ipv6), but nothing worked, HA was dead on router, when i found it changed my MAC adress. So i changed every settings everywhere on new MAC adress and its working. So maybe if someone read this, i gave you some time :) and @jonlove234 anyway, thanks for your response :) |
Well done on solving!
…On Thu, Dec 5, 2024 at 10:23 PM matvit92 ***@***.***> wrote:
I solved it now after 4 hours. It was reset complete network settings,
which i tried to configure using nmcli (nastavit ipv4, vypnout ipv6), but
nothing worked, HA was dead on router, when i found it changed my MAC
adress. So i changed every settings everywhere on new MAC adress and its
working. So maybe if someone read this, i gave you some time :) and
@jonlove234 <https://github.com/jonlove234> anyway, thanks for your
response :)
—
Reply to this email directly, view it on GitHub
<#3717 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5OBT4VWDZO3LJD56P3NMPL2EEKELAVCNFSM6AAAAABTAP4752VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGA2DANRYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Describe the issue you are experiencing
Via the GUI, updated to HAOS 14
Rebooted and no connectivity. Same when reverting back to 13.X
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
14.0
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
HAOS x86 running in Unraid VM
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
No response
Additional information
The text was updated successfully, but these errors were encountered: