Network works in Guest VM but not in Host Opensuse 13.2 Machine

English Network/Internet
1

Hi I have an opensuse 13.2 host machine running vmware player with a windows 7 guest all working fine.

I decided to give the machine more physical RAM since it was a bit slow. After inserting the card and restarting the computer, NetworkManager does not connect to network or internet, however the VM machine connects to the internet and network without a problem,

I have tried DHCP, and static IP, disabeling NetworkManager and using wicked again with DHCP and Static IP with no luck

Any help would be great. Thanks

2

I would start debugging the issue by looking at your network settings and name resolution.

First;
Can you ping your router from a terminal?

Second;
What do you have in your /etc/resolv.conf and can you nslookup sites? For example nslookup www.google.com

3

hi Miuku

Ping network from opensuse results in…

amy@linux-bhpe:~> ping 192.168.254.9
connect: Network is unreachable
amy@linux-bhpe:~>/

nslookup results in …

amy@linux-bhpe:~> nslookup www.google.com
;; connection timed out; no servers could be reached

amy@linux-bhpe:~>

resolv.conf looks like this…

/etc/resolv.conf file autogenerated by netconfig!

Before you change this file manually, consider to define the

static DNS configuration using the following variables in the

/etc/sysconfig/network/config file:

NETCONFIG_DNS_STATIC_SEARCHLIST

NETCONFIG_DNS_STATIC_SERVERS

NETCONFIG_DNS_FORWARDER

or disable DNS configuration updates via netconfig by setting:

NETCONFIG_DNS_POLICY=‘’

See also the netconfig(8) manual page and other documentation.

Note: Manual change of this file disables netconfig too, but

may get lost when this file contains comments or empty lines

only, the netconfig settings are same with settings in this

file and in case of a “netconfig update -f” call.

Please remove (at least) this line when you modify the file!

nameserver 192.168.254.1

ifconfig returns…

enp2s0 Link encap:Ethernet HWaddr D0:50:99:38:9B:C4
inet6 addr: fe80::d250:99ff:fe38:9bc4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17748 errors:0 dropped:0 overruns:0 frame:0
TX packets:13750 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12948494 (12.3 Mb) TX bytes:2829049 (2.6 Mb)

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:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 b) TX bytes:240 (240.0 b)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.1.1 Bcast:172.16.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.11.1 Bcast:192.168.11.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

linux-bhpe:/home/amy #

it seems that the network cannot set an IP address.

4

When you ran the command, did you have Wicked controlling the interface?

<runs off to install 13.2 in a VM, so many people with 13.2 issues…> :stuck_out_tongue:

5

here is some more info

systemctl status NetworkManager returns…

linux-bhpe:/home/amy # systemctl status NetworkManager
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Tue 2015-01-13 13:21:38 SAST; 1h 57min ago
Main PID: 766 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─766 /usr/sbin/NetworkManager --no-daemon

Jan 13 13:22:11 linux-bhpe NetworkManager[766]: <info> Activation (vmnet8) successful, device…d.
Jan 13 13:22:14 linux-bhpe dhclient[1026]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67…e8)
Jan 13 13:22:14 linux-bhpe NetworkManager[766]: DHCPDISCOVER on enp2s0 to 255.255.255.255 por…8)
Jan 13 13:22:25 linux-bhpe NetworkManager[766]: <warn> (enp2s0): DHCPv4 request timed out.
Jan 13 13:22:25 linux-bhpe dhclient[1026]: Received signal 15, initiating shutdown.
Jan 13 13:22:25 linux-bhpe NetworkManager[766]: Received signal 15, initiating shutdown.
Jan 13 13:22:25 linux-bhpe NetworkManager[766]: <info> (enp2s0): canceled DHCP transaction, D…26
Jan 13 13:22:25 linux-bhpe NetworkManager[766]: <info> Activation (enp2s0) Stage 4 of 5 (IPv4…
Jan 13 13:22:25 linux-bhpe NetworkManager[766]: <info> Activation (enp2s0) Stage 4 of 5 (IPv4…
Jan 13 13:22:25 linux-bhpe NetworkManager[766]: <info> Activation (enp2s0) Stage 4 of 5 (IPv4…e.
Hint: Some lines were ellipsized, use -l to show in full.
linux-bhpe:/home/amy #

systemctl status wicked returns…

linux-bhpe:/home/amy # systemctl status wicked
wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; disabled)
Active: inactive (dead)

linux-bhpe:/home/amy #

ip address return…

linux-bhpe:/home/amy # ip address
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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether d0:50:99:38:9b:c4 brd ff:ff:ff:ff:ff:ff
inet6 fe80::d250:99ff:fe38:9bc4/64 scope link
valid_lft forever preferred_lft forever
3: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
inet 172.16.1.1/24 brd 172.16.1.255 scope global vmnet1
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fec0:1/64 scope link
valid_lft forever preferred_lft forever
4: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
inet 192.168.11.1/24 brd 192.168.11.255 scope global vmnet8
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fec0:8/64 scope link
valid_lft forever preferred_lft forever
linux-bhpe:/home/amy #

netstat -r returns…

linux-bhpe:/home/amy # netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
172.16.1.0 * 255.255.255.0 U 0 0 0 vmnet1
192.168.11.0 * 255.255.255.0 U 0 0 0 vmnet8
linux-bhpe:/home/amy #

cat /etc/resolv.conf |grep name…

linux-bhpe:/home/amy # cat /etc/resolv.conf |grep name
nameserver 192.168.254.1
linux-bhpe:/home/amy #

6

no the networkManager is the interface

7

When you tried Wicked with the static IP, did you remember to set the gateway in the Routing section in the YAST2 Network Settings as well as the Name Servers?

8

Gateway,gateway,gateway. I must remember the gateway. Thanks for that, it now connects.

Still does not connect with DHCP but I am fine with static IP’s since this is a desk-top that does not move.