OS 13.1 guest in virtualbox, windows host - no network

I can’t seem to get the network going with VirtualBox under Windows 7. Is anyone able to do this? It’s a vanilla install of 13.1.

Thank You!!
Patti

On 2015-08-02 04:26, PattiMichelle wrote:
>
> I can’t seem to get the network going with VirtualBox under Windows 7.
> Is anyone able to do this?

I guess too many to count them :slight_smile:

You will rather have to explain more. And probably ask first a moderator
to move your post to the virtualization forum.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Agreed,
This post and this question which has been asked before belongs in the Virtualization forum.

But, I’d also ask whether this is your first attempt at setting up a Virtualbox Guest or if you have other Guests running without problems.

TSU

On 2015-08-03 02:36, tsu2 wrote:

> But, I’d also ask whether this is your first attempt at setting up a
> Virtualbox Guest or if you have other Guests running without problems.

Yes, good question. At this point, we don’t know if the problem is with
virtual box, with the guest, or the host.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Will be moved to Virtualization and is CLOSED for the moment.

Moved from Applications and open again.

Thank you, Robin - I didn’t realize there was a virtualization forum - moderator can you please move this?

Thank You!!!

Sorry - install latest virtualbox and extpak on Win7x64 host, installed OS13.1 and Linux MINT in two VMs (same win7 laptop). Both went fine. (I’ve done this a lot of times, but not in the last couple of years - before that it seems like NAT setup just worked OOB for virtualbox by accepting the default adapter chipsets for NAT or Bridged.) Installed extension packs in each linux distro. MINT finds internet just fine, but OS (NetworkManager) has problems.

The wired connections (13.1 guest) default to DHCP. It is trying to connect (progress bar on top of RJ45 NetworkManager icon in taskbar) but quickly flashes back to the red circle/diagonal. Connect Automatically and System Connection and IPv4 are checked in properties for network connection.

I thought it might be Virtualbox/Win7 thing, but MINT automatically connects OK (can surf the web). I set them up both the same with default Intel PRO/1000.

You want to connect with Virtualbox-bridged-Network to the Internet, right.

And in openSUSE-Guest you want to connect with Network-Manager (Applett in the right corner)?

In Yast----Network switch back to wicked, delete all Konfiguration from your Networkcards and switch back from wicked to Network-Manager.

Does it work?

Also post:

ip addr
ip route

I was just leaving it a vanilla install, so yes to Network-Manager applet is used in OS-Guest. I thought the default in VBox-Host was NAT? (That’s what MINT used which worked.) I can try the bridged setup, I recall that has worked in years gone-by. What is “wicked?” I’ve never seen that before. You mean ifconfig? Where is “Konfiguration” and “Networkcards”?

patti@linux-537z:~> su
Password: 
linux-537z:/home/patti # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 08:00:27:ce:9f:cb brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a00:27ff:fece:9fcb/64 scope link 
       valid_lft forever preferred_lft forever
linux-537z:/home/patti # ip route
linux-537z:/home/patti # 

Same result when I declare a Bridged adapter in the host VBox - when I start openSUSE the NetworkManager toggled back and forth between connecting and the red circle/slash, then finally gives up.

Oh wicked is the new Network Service Name? for opensuse 13.2. My mistake.

Try it with NAT in the global Options of Virtualbox.

Goto:
Yast------Network-Device-----Network Settings.

Global Options and switch the Network Setup Method to ifup.
Goto Overview, klick on the Card and klick delete.
Goto Global Options and switch back to Network Manger.

Set it up in Networkmanager in the right Corner.

OK. Switched to ifup, deleted existing “card” (adapter) in ifup and rebooted. Switched back to NetworkManager. Same behavior (toggling between connecting and red circle/slash). Tried deleting card in NetworkManager, and creating a new one, but same behavior.

In VirtualBox host, network is set to default NAT, with cable connected.

If, while in the openSUSE guest, I disconnect the cable (from within VirtualBox Network Settings) then the NetworkManager icon changes to an “x” - when I reconnect the cable (in VirtualBox Network Settings), then the “x” is replaced by the above behavior (toggling between trying-to-connect progress bar and the red circle/slash) in the NetworkManager icon.

I don’t know if this is useful, but this is what MINT yields to the ip * commands…

patti@VBMint:~ > su
Password: 
VBMint patti # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff
    inet **.**.**.**/** brd **.**.**.** scope global eth0
       valid_lft forever preferred_lft forever
    inet6 **:**:**:**:**:**/** scope link                                                         
       valid_lft forever preferred_lft forever                                                            
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000   
    link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff                                                       
VBMint patti # ip route                                                                                         
default via **.**.**.** dev eth0  proto static                                                                     
**.**.**.**/** dev eth0  proto kernel  scope link  src **.**.**.**  metric 1                                           
VBMint patti #

On 2015-08-04 17:56, PattiMichelle wrote:
>
> I don’t know if this is useful, but this is what MINT yields to the ip *
> commands…

Eum… A comment.
IPv4 addresses in a local network are safe for publishing in Internet,
no need to obfuscate them. They are probably 192.* or 10.*, they can’t
be routed over Internet, nor accessed from outside.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

  • First, use the default openSUSE wicked setup typical of an ordinary install. Don’t use NM, there is no need. NM has some advantages creating and managing various types of network connections (particularly WiFi) which is entirely unnecessary in a Guest. A Guest only needs a wired connection (whatever real physical connection is provided by the Host and passed to the Guest as a wired connection only). The only network device changes you might make are as a DHCP client or configured with static or custom addresses.

  • If you see a red X on a network device in the taskbar tray (rt end of the panel/bar/whatever depending on the Desktop), don’t pay any attention to it. It’s typically the result of an unaddressed openSUSE 13.2 anomaly, NM is installed but not active by default. The applet represents a NM connection which isn’t active so is a dead artifact.

  • A fundamental process which should become your SOP (Standard Operating Procedure) is to not use and rely on any configuration tool to display your actual configuration. The configuration tool should be used only to make settings, you then use other tools to verify and view the actual running config. So, in this case you can use NM or Wicked to configure your network settings, but don’t rely on what they say for how your system is actually operating… Instead you should use various command line network tools.

In particular, you should often use the IP tools, which are the current standard and successor to various older network tools including ifconfig. Although you will still see ifconfig from time to time and might display some information in a better way, for about 3 years now (as of this writing) ifconfig has been in the process of being transitioned out. Use “ip addr” and the other “ip *something *” tools.

After viewing and verifying settings using the “ip” commands, test your connectivity with ping and traceroute.

  • Use the default NAT network connection unless you have a special reason to do something different because with that configuration your Guest is more portable with fewer possible complications (especially if you use a Laptop which might change networks). With NAT, the Guest is entirely self-contained relying on the Host to provide all network connectivity and services including routing and name resolution. If you set up Bridging for instance, then we’d have to consider additional issues like whether DHCP is provided, IPv4 or IPv6, DNS, routing, firewall filtering, etc. In other words everything you <must> consider when installing a new machine directly on the physical network.

I think you started configuring a Bridged network connection which is why your “ip addr” only returned an IPv6 “link ether” address.

Re: any Private Network Address, they may not be routable on the Internet, but it may still be worth at least a moment’s thought how they might be routable in your Intranet and if they’re directly exposed to a physical network (eg on your network’s Edge) they can still be potentially hacked by anyone in that adjacent network even if not using the same networkid.

TSU

Your Mint results suggest
It’s likely configured with a Bridged network connection because it doesn’t have an IPv4 address.
BTW - If you’re configuring VBox network connections, there is a difference betwee NAT and NAT network.
NAT- The default, A single, isolated NAT connection
NAT network- A shared NAT connection.

I’m trying to remember correctly what I found to be the unique characteristics of the NAT connection besides a single, unique and unshared connection. I can’t remember for sure whether you can run multiple Guests at once using this connection and what the consequences are.

Since you didn’t seem to follow my suggested “SOP” I described in my previous post, I can’t be certain but your problem might have been because you used the NAT instead of the “NAT network” connection.

The “NAT network” connection is probably more useful since it enables each Guest to communicate with the HostOS and all other Guests configured this way as well.

TSU

Heh. Well… :shame:

This is 13.1x64 and I think NM is the way it installs default - I’m sort of stuck, at least for the time being, with 13.1.

I thought I posted the results of the two suggested ip commands on 13.1 and another distro. I was just providing information I thought would be helpful. Usually there’s a known problem and I don’t know why I am having this network issue, especially since MINT (in the same host) doesn’t seem to have any problems.

I’ve usually just accepted the default NAT in the past (OS 11.x and 12.x), although sometimes I select Bridged. I see there’s “NAT Network” now available and I thought I saw that was still sort of experimental. I tried selecting NAT Network but it won’t let me set a name, so I haven’t really tried it.

I created two network interfaces in the VBox guest - NAT and Bridged (I can’t create NAT Network) in promiscuous mode. I switched the 13.1 guest to ifup and configured the two interfaces DHCP, ip4 and 6. The cables are ‘connected’ (according to VirtualBox). The 13.1 guest claims the cables aren’t connected, I think. More information. Sorry I’m a bonehead.

patti@linux-537z:~> su
Password: 
linux-537z:/home/patti # ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:74 errors:0 dropped:0 overruns:0 frame:0
          TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4972 (4.8 Kb)  TX bytes:4972 (4.8 Kb)

linux-537z:/home/patti # ip route
127.0.0.0/8 dev lo  scope link 
linux-537z:/home/patti # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 08:00:27:ce:9f:cb brd ff:ff:ff:ff:ff:ff
3: enp0s8: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 08:00:27:0e:0d:4f brd ff:ff:ff:ff:ff:ff
linux-537z:/home/patti #