Bug 270927 - emulators/virtualbox-ose: bridged network adapter - Guest OS Windows the default gateway is not available
Summary: emulators/virtualbox-ose: bridged network adapter - Guest OS Windows the defa...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL: https://www.freshports.org/emulators/...
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2023-04-19 05:19 UTC by andleb
Modified: 2023-07-28 07:28 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (vbox)
andleb231175: maintainer-feedback? (vbox)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description andleb 2023-04-19 05:19:39 UTC 
Hi all

Recently I upgraded my FreeBSD 11.4 with VirtualBox 5.2.44 (legacy port) to FreeBSD 12.4 with Virtual 6.1.36. For many years Freebsd 11.4 + VirtualBox 5.2.44 (Host OS - FreeBSD, Guest OS - Windows 7/10 with bridged networking) worked perfect.
Now I faced with following thing. Sometimes Guest OS Windows become unavailable due to error "the default gateway is not available" in bridged networking. I can fix it by Windows troubleshooter, resetting adapter or just switch on/off network adapter, but after a while I get the same result "the default gateway is not available". 
I tried to use "clean" Windows 7/10 installation and also got "the default gateway is not available". Sure I tried all the fixing methods (reset networking settings, turn off power management for adapter and etc).
I tried to use NAT adapter and it works perfectly, but I need Guest OS to be in same localnet as Host OS.
Any idea?
Comment 1 andleb 2023-07-28 07:28:10 UTC 
Some updates.

I back again to virtualbox legacy port and faced with same behaivour.