See here:
https://www.suse.com/releasenotes/i386/openSUSE/12.3/RELEASE-NOTES.en.html#upgrade
I had the same problem with a 12.2 opensuse 64 bit install on a vmware esxi server, installed from a vmware 5.5 client.
the internet test failed within the installation wizard.
the yast gateway standard configuration did modify the …sysconfig/network/route file but network restart would not set the default gateway as expected
only the route add command would set the gateway, but did not set it permanently: gateway definition would be lost after reboot
then I added the 0.0.0.0 destination as suggested here, and miracle the permanent gateway definition was set and worked.
A general comment about the previous posts in this thread.
For some reason it seems to me each person has configured a Linux bridge device <in> the Guest (eg vmxnet).
This is entirely optional and useful for complex virtual networking, but is totally unnecessary for most people who only deal with single virtual networks for each type of connection (Bridging, NAT, Host Only).
For almost everyone, you should <not> create a network bridging device <in> the Guest, just a normal wired adapter should be perfectly fine and all that is required. So, when you look at the network interfaces, you should see <only> eth0 (or a suitable substitute name), no virtual interfaces. From a single generic “real” wired interface <in> the Guest, in the Host you can then configure a multitude of different types of connections.
On the Host, a Linux bridging device is highly recommended (although I’ve read posts from some who have apparently set up without). The idea is that unless it’s required, all complexity should be kept <outside> the Guest whch should see a very ordinary connection.
TSU
Can you post examples/steps of exactly what you think is the correct setup for the guest and host?
The following particularly applies to Virtualbox 4.3.4 and 4.3.6 (and possibly later unless/until VB changes something)
Well for 99% installs which just want to set up a Guest with access to the Internet and nothing special,
Guest - Nothing special in the Guest. From inside the Guest, it should be set up with a standard <wired> connection no matter what kind of physical network connection is configured on the Host. No Linux Bridge Device, the Guest should think it’s connecting to a very ordinary wired network. So, when you run the following, by default you should see only two interfaces, the loopback (lo) and the wired interface (can be eth0 but frequently is a name associated with a physical virtual NIC like enp0s1). I generally recommend the network connection should be configured for DHCP unless there is a special reason not to. Can be setup with NM or “Classic ifup/ifdown” should not make much difference… You just need to know the normal way to work with either.
ip addr
Host - Networking can be a little weird or it can be somewhat simple, as I explained earlier this is where you configure actual network connectivity for the Guest. The “wired” connection the Guest sees is now configured in the Host however is needed, eg Bridging/NAT/NAT network/HostOnly and possibly connecting to a specific Host NIC (Believe by default VirtualBox will generally connect to whatever physical NIC is active so specifying a Host NIC usually isn’t necessary).
By selecting “Bridging/NAT/NAT network/HostOnly” Virtualbox automatically creates an appropriate Linux Bridge Device configured for that type of connection. You are completely shielded from the housekeeping duties associated with setting up, and managing (in this way is somewhat similar to libvirt).
An important thing to understand with Virtualbox today is that NAT configurations are considered “beta” (in the documentation). But, it seems to be working reliably for me so far.
And, there is a <big> difference between NAT and “NAT network” – For anyone who intends to launch only one Guest, NAT seems to be fine, but NAT will configure <any and all Guest with the same MAC address> which of course makes it totally unsuitable for running more than one Guest which need to talk to each other (or the Host). Curiously configuring more than one Guest on NAT allows all Guests to connect to and operate with the Internet just fine, it’s networking locally any combination of Guests and Hosts which won’t work.
To setup a virtual network of multiple Guests which can communicate with each other, you need to set up “NAT network” – I won’t go into that here, it’s in the documentation. The GUI for setting up a NAT network is in a weird place and IMO not completely obvious, but it works. I setup using the instructions for setting up using the CLI and it also works fine.
Once you have the type of networking setup and available (particularly a NAT network if you want it which is not setup by default), like any other virtualization manager, you simply go into the Guest configuration properties (settings) and select what you want.
After double-checking your Guest settings the first time you setup, you then just click the “Run” icon (Green arrow) to start up your Guest for the first time.
TSU