Before coming to your problem, I would like to introduce to you the way to post computer text in a post. It is best to copy/paste from the terminal window the prompt. the command, the output and the next prompt between so called CODE tags. You get the CODE tags by clicking on the # button in the tool bar of the post editor. E.g.:
This explains all to us and relieves your from typing things like “when I do” and “then I get”.
Then to your problem. You tell what you think you did (but you did not show us in the way explanied above, so we can not check if there were any messages coming back), but you did not check what he results of those command were. Checkin if eth0 is realy up with the wanted IP address with
I follow you.
(Sorry copy/paste doesnt work from hyperv)
eth0 Link encap:Ethernet HWaddr 00:15:5D:F1:BF:05
inet adr:192.168.1.254 Bcast:192.168.1.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:0 (0.0 b) TX bytes:10872 (10.6 Kb)
lo Link encap:boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:304 errors:0 dropped:0 overruns:0 frame:0
TX packets:304 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:23064 (22.5 Kb) TX bytes:23064 (22.5 Kb)
table de routage Ip du noyau
Destination Passerelle Genmask Indic Metric Ref use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
As you see, not being able to copy/paste distorts the text. But in this case we have too live with it
Both outputs seem to be OK.
But I belately) read that you use someting on Windows called hyperv. Now I know next to nothing about Windows, but this maybe some sort of virtualisation. When that is correct, did you notive we have a Virtualisation forum? It is more likely that knowing people are there then.
When this is about virtualisation, I can move this thread there when you want (and please do not starta double post there, we do not like double posts).
My initial thought is that you setup your openSUSE network settings manually from the command line.
That may or may not work correctly.
In openSUSE, the preferred method is to use YAST which will generally make configurations fool-proof
Or at least ensure the methods used to configure are standardized.
I recommend you <remove> any settings you used and re-do using YAST.
Or, if this is brand new, just create a new VM.
Hyper-V should not be much different than any other virtualiztion technology,
Make sure your Host is set up properly and working (any other VMs already working?)
Create your VM by pointing to install media.
Run, usually accepting defaults.
In the case of openSUSE, if you’re running a Desktop Environment (eg Gnome or KDE), then Network Manager likely will be setup automatically and running which you would use to do “all things networking.”
I also recommend you explore what YAST can do, it will be the center of most things you do at first, and only later use alternate command line.
openSUSE 12.3 has a well known install bug, networking is setup out of order so is non-functional at first.
Easily resolvable by either re-starting Networking Service or rebooting the Guest.
The result should be a Guest that connects using eth0 (regardless how the Host connects) and should “just work” using a NAT.
No further further networking connection configuration should be needed unless you want to setup a secondary connection.
From within any Guest, networking should work as a wired ethernet connection, openSUSE would be no diff from most Linux in most cases that would be eth0. This almost never changes. The magic of modifying types of network connections and more is configured outside the Guest.
NAT or any other type of virtual network(typically other types are Bridged and Local Host only) are configurable on the Host management app.
The first time you create a VM Guest, it’s not a good idea to just rush ahead and fire it up assuming the VM Creation wizard set everything up properly. I find that’s not the case almost every time nowadays.
You should open the VM’s properties and inspect each and every configuration carefully.
A starting point might be to see if your Guest can even communicate with the host.
From within the Guest, run the following two commands to see if you have an IP address
And what your Default Gateway is
If you don’t know how to read the above, post in
blocks or images.
Then if you have PING installed, try pinging your DG.
If that works, then there is nothing wrong in your Guest, whatever your problem is <must> be in your Hyper-V Management.