Win 10 home vbox running Endian 3.2.2 GUI failure
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Win 10 home vbox running Endian 3.2.2 GUI failure
Having a bone head issue with this EFW 3.2.2 installation.
Win 10 home with ALL current updates, current vbox ver, bells and whistles is fine.
Win Firewall turned OFF.
EFW 3.2.2 install goes in without issue.
WHAT is the issue is when efw 3.2.2 powers up, the default mgmt interface ex - 192.168.0.15:10443 is dead.. nothing. Port scan shows nothing too.
banging my head on this, any suggestions help would be appreciated.
Win 10 home with ALL current updates, current vbox ver, bells and whistles is fine.
Win Firewall turned OFF.
EFW 3.2.2 install goes in without issue.
WHAT is the issue is when efw 3.2.2 powers up, the default mgmt interface ex - 192.168.0.15:10443 is dead.. nothing. Port scan shows nothing too.
banging my head on this, any suggestions help would be appreciated.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
Let's take a look at the guest's Virtualbox settings: Please post the guest's .vbox 'recipe' file as a zip file, using the Upload Attachment tab under the textbox where you type new posts. You can find the guest's .vbox file by right-clicking the guest in the main Virtualbox window and choosing Show in Explorer. Be sure your host OS is set to show known extensions.
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
thanks... attached.
- Attachments
-
- efw.zip
- (1.53 KiB) Downloaded 10 times
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
OK, you have two networks in your guest, one NAT, which can get you to the internet in the guest in just about any condition where the host can get internet.
The other is set to Internal, which only connects with other guests. Set the Internal one to Host-Only. The host's IP address on the Host-Only network will be 192.168.56.1, and the guest's IP address will be in the 192.168.56.### range by default, unless you have tweaked things. See the main Virtualbox window, File menu, Preferences, Network, Host-Only Networks tab, double-click the Host-Only network shown to see the settings for DHCP on the Host-Only network. Note that if you have the DHCP server for this network turned on your guest will get a dynamic IP address. You can set the guest OS to static on the 192.168.56.### range, preferably outside the range the DHCP server wants to use.
The other is set to Internal, which only connects with other guests. Set the Internal one to Host-Only. The host's IP address on the Host-Only network will be 192.168.56.1, and the guest's IP address will be in the 192.168.56.### range by default, unless you have tweaked things. See the main Virtualbox window, File menu, Preferences, Network, Host-Only Networks tab, double-click the Host-Only network shown to see the settings for DHCP on the Host-Only network. Note that if you have the DHCP server for this network turned on your guest will get a dynamic IP address. You can set the guest OS to static on the 192.168.56.### range, preferably outside the range the DHCP server wants to use.
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
thanks, done.
reset endian 3.2.2 to factory default, done
endian boots with green mgmt interface set to 192.168.0.15:10443 - but nothing, not pingable, nadda...
reset endian 3.2.2 to factory default, done
endian boots with green mgmt interface set to 192.168.0.15:10443 - but nothing, not pingable, nadda...
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
Send us the guest's .vbox file, zipped, again please.
Also open a command window and copy/paste this command with the double quotes:
find the file "hostonlyifs.txt" on your desktop and throw it in the zip with the new .vbox file, please.
Also open a command window and copy/paste this command with the double quotes:
Code: Select all
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list hostonlyifs > %userprofile%/desktop/hostonlyifs.txt
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
thanks man, here they are.
- Attachments
-
- efw.zip
- (2.01 KiB) Downloaded 9 times
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
OK, thanks!
You now have three networks in your guest: NAT, Host-Only and Internal. That's fine. The Host-Only network is the one you will use to communicate between host and guest.
You have two Host-Only networks: "VirtualBox Host-Only Ethernet Adapter" and VirtualBox Host-Only Ethernet Adapter #2", which also is fine. Your guest is attached to "VirtualBox Host-Only Ethernet Adapter". This Host-Only adapter is running with an IP range of 192.168.32.###.
The guest OS may be getting an IP address in the 192.168.32.### range. Use the guest OS's utilities to see what IP address it is getting if it is getting one. Otherwise you may have to set a static IP address within the guest OS to a number in the 192.168.32.### range. Try a number less than 99 and greater than 2 for the ###, since Host-Only networks default to handing out DHCP-served IP addresses above 100, and the host's connection is at 192.168.32.1.
Set your guest OS's address and port settings where it is calling for "192.168.0.15:10443" to 192.168.32.###:10443, where ### is the address you found or set above. Be sure the guest OS's firewall, if there is one, is set to allow port 10443 to be accessed.
From the guest OS you can contact the host's services via 192.168.32.1. On the host, access your guest on 192.168.32.###:10443, and you should be good.
You now have three networks in your guest: NAT, Host-Only and Internal. That's fine. The Host-Only network is the one you will use to communicate between host and guest.
You have two Host-Only networks: "VirtualBox Host-Only Ethernet Adapter" and VirtualBox Host-Only Ethernet Adapter #2", which also is fine. Your guest is attached to "VirtualBox Host-Only Ethernet Adapter". This Host-Only adapter is running with an IP range of 192.168.32.###.
The guest OS may be getting an IP address in the 192.168.32.### range. Use the guest OS's utilities to see what IP address it is getting if it is getting one. Otherwise you may have to set a static IP address within the guest OS to a number in the 192.168.32.### range. Try a number less than 99 and greater than 2 for the ###, since Host-Only networks default to handing out DHCP-served IP addresses above 100, and the host's connection is at 192.168.32.1.
Set your guest OS's address and port settings where it is calling for "192.168.0.15:10443" to 192.168.32.###:10443, where ### is the address you found or set above. Be sure the guest OS's firewall, if there is one, is set to allow port 10443 to be accessed.
From the guest OS you can contact the host's services via 192.168.32.1. On the host, access your guest on 192.168.32.###:10443, and you should be good.
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
ty, will do and report back.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
I took a look again and see a couple of things more:
First it appears that you Host-Only network is not running a DHCP server. So in your guest OS you will have to set a static IP address in the 192.168.32.### range, ### preferably between 3 and 99, your choice.
Secondly, I find that Endian is a firewall of sorts. You will have to make sure that Endian is using the Host-Only network as "green" interface you mentioned. FWIW you can add other guests to the same Host-Only network that Endian and the host are in; you may not need that Internal network, depending on your project needs.
First it appears that you Host-Only network is not running a DHCP server. So in your guest OS you will have to set a static IP address in the 192.168.32.### range, ### preferably between 3 and 99, your choice.
Secondly, I find that Endian is a firewall of sorts. You will have to make sure that Endian is using the Host-Only network as "green" interface you mentioned. FWIW you can add other guests to the same Host-Only network that Endian and the host are in; you may not need that Internal network, depending on your project needs.
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
Nope, no cigar... This is something else... Still sitting at the drawing board.
Basically I need 4 interfaces - wan, lan, dmz, wifi
Basically I need 4 interfaces - wan, lan, dmz, wifi
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
I know nothing about Endian to be able to help troubleshoot. But as long as Virtualbox is connecting the hardware well, it's up to the guest OS and the user to know how to use the hardware. Do you have any way to report what the various network cards in the Endian guest are showing for IP addresses? Could be you have the wrong virtual network connected to your "green" connection.
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
yeah egg-zactly.
I'm gonna start from scratch for giggles.
TY again, I will report back....
I'm gonna start from scratch for giggles.
TY again, I will report back....
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
pfSense has a "plug in the network you want to use for the WAN side now let me autosense it now plug in the LAN side now let me autosense etc." Maybe Endian has something similar? You could have your four network cards but have none of the "cables" connected until you set up Endian, and maybe the OS will ask you to connect WAN, then LAN etc.
-
- Posts: 8
- Joined: 22. Jun 2017, 16:14
Re: Win 10 home vbox running Endian 3.2.2 GUI failure
hmmm interesting, I'll snoop around for such. good idea.