-
Notifications
You must be signed in to change notification settings - Fork 757
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
Interfaces disconnected after reboot on Hyper-V #748
Comments
To clarify: 15.7.25 didn't have the problem, so it's probably a 10.2 kernel issue. Seems opnSense should switch to 10.3 ASAP. |
10.3 is not out until March. We'll try to pin this down and backport sooner. |
I've waded through the commits again, it may be this one... freebsd/freebsd-src@40f9a4207f94b185d I will try to upload another test kernel. :) |
I'll be back in a week, take your time to test this one. :) |
Seems you found the commit, works for me. |
Will be in 16.1.3 :) |
Thanks for report+test! |
With 16.1.2 (I think was present in 16.1.1 already), after a reboot a opnSense VM (generation 1) on Hyper-V has lost its network connectivity (pinging the upstream GW returns "down").
When testing with the 10.3-PRERELEASE (opnsense-update -bkr 791bdab10f3cfbed0b6a62d89d9168fb66d3eafe) which was meant to fix the NAT issue, reboot is performed ok.
The text was updated successfully, but these errors were encountered: