Reconfiguring networking

vilanye · May 16, 2016, 8:38am

Long story short, I was having boot issues having to do with the system not seeing my video card and while troubleshooting with EVGA support I had to reset CMOS. I ended up having to use a different slot for my video card but that is a different topic. If it matters, it is a z97 FTW board.

Resetting it caused all sorts of issues with Windows and Leap. I had to reinstall the Nvidia driver and the networking driver and run the sound troubleshooter to get all of those working correctly in Windows. On the open suse side I had to fiddle with the sound settings in the KDE panel to get sound back and I have been trying to get networking back. I have eth0 and it has a bunch of IPv6 addresses but no IPv4 so I can’t even ping my router. YAST can see my networking card and I have edited it and removed and re-added it with no luck.

Is there some magic incantation I need to do to get networking back?

hcvv · May 16, 2016, 9:48am

This is a bit vague. When you use YaST and try to configure eth0, what are you trying?

Using Wicked or NetworkManager?

When using Wicked: using DHCP or not?

Etc.

deano_ferrari · May 16, 2016, 9:54am

Are you using wicked or NetworkManager? I assume you’re using DHCP

To start with, open a terminal and do

sudo journalctl -f

then open another terminal and do

sudo systemctl restart network

Examine the output from journalctl. CTRL-C to terminate. You should see a dhcp lease obtained (assuming your hardware and/or configuration is ok). Copy the output to a text file and transfer via memory sitck to an internet-connected computer if necessary so that you can upload here for others to review. Perhaps also show us

/sbin/ifconfig

vilanye · May 16, 2016, 8:39pm

It seems to be using wicked. Whatever was installed by default is what is running.

Here is the output you asked for

-- Logs begin at Wed 2015-11-25 17:43:57 PST. --
May 16 11:28:05 linux-yyix wickedd-dhcp4[1298]: eth0: Request to acquire DHCPv4 lease with UUID 2b103a57-c581-0800-4505-000009000000
May 16 11:28:05 linux-yyix kernel: userif-3: sent link down event.
May 16 11:28:05 linux-yyix kernel: userif-3: sent link up event.
May 16 11:28:15 linux-yyix wickedd-dhcp4[1298]: unable to confirm lease
May 16 11:28:20 linux-yyix wickedd-dhcp4[1298]: eth0: defer timeout 15 reached (state INIT)
May 16 11:28:31 linux-yyix wicked[2346]: lo              up
May 16 11:28:31 linux-yyix wicked[2346]: eth0            setup-in-progress
May 16 11:28:40 linux-yyix sudo[2275]: pam_unix(sudo:session): session closed for user root
May 16 11:28:42 linux-yyix sudo[2477]: david : TTY=pts/0 ; PWD=/home/david ; USER=root ; COMMAND=/usr/bin/journalctl -f
May 16 11:28:42 linux-yyix sudo[2477]: pam_unix(sudo:session): session opened for user root by david(uid=0)
May 16 11:28:48 linux-yyix wickedd-dhcp4[1298]: eth0: no lease set
May 16 11:28:48 linux-yyix vmnetBridge[1783]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
May 16 11:28:48 linux-yyix vmnet-natd[1808]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
May 16 11:28:48 linux-yyix vmnetBridge[1783]: Removing interface eth0 index:2
May 16 11:28:48 linux-yyix kernel: e1000e: eth0 NIC Link is Down
May 16 11:28:48 linux-yyix kernel: bridge-eth0: disabling the bridge
May 16 11:28:48 linux-yyix wicked[2482]: eth0            device-ready
May 16 11:28:48 linux-yyix vmnetBridge[1783]: Stopped bridge eth0 to virtual network 0.
May 16 11:28:48 linux-yyix kernel: bridge-eth0: down
May 16 11:28:48 linux-yyix kernel: bridge-eth0: detached
May 16 11:28:48 linux-yyix kernel: userif-3: sent link down event.
May 16 11:28:48 linux-yyix kernel: userif-3: sent link up event.
May 16 11:28:48 linux-yyix vmnetBridge[1783]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001003
May 16 11:28:48 linux-yyix vmnet-natd[1808]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001003
May 16 11:28:52 linux-yyix vmnetBridge[1783]: RTM_NEWLINK: name:eth0 index:2 flags:0x00011043
May 16 11:28:52 linux-yyix vmnet-natd[1808]: RTM_NEWLINK: name:eth0 index:2 flags:0x00011043
May 16 11:28:52 linux-yyix vmnetBridge[1783]: Adding interface eth0 index:2
May 16 11:28:52 linux-yyix vmnetBridge[1783]: Started bridge eth0 to virtual network 0.
May 16 11:28:52 linux-yyix kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
May 16 11:28:52 linux-yyix kernel: /dev/vmnet: open called by PID 1783 (vmnet-bridge)
May 16 11:28:52 linux-yyix kernel: /dev/vmnet: hub 0 does not exist, allocating memory.
May 16 11:28:52 linux-yyix kernel: /dev/vmnet: port on hub 0 successfully opened
May 16 11:28:52 linux-yyix kernel: bridge-eth0: up
May 16 11:28:52 linux-yyix kernel: bridge-eth0: attached
May 16 11:28:52 linux-yyix wickedd-dhcp4[1298]: eth0: Request to acquire DHCPv4 lease with UUID 2b103a57-c581-0800-4505-00000e000000
May 16 11:28:52 linux-yyix kernel: userif-3: sent link down event.
May 16 11:28:52 linux-yyix kernel: userif-3: sent link up event.
May 16 11:29:02 linux-yyix wickedd-dhcp4[1298]: unable to confirm lease
May 16 11:29:07 linux-yyix wickedd-dhcp4[1298]: eth0: defer timeout 15 reached (state INIT)
May 16 11:29:18 linux-yyix wicked[2488]: lo              up
May 16 11:29:18 linux-yyix wicked[2488]: eth0            setup-in-progress
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:25 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:41 linux-yyix org.kde.kuiserver[1931]: kuiserver: adding job contact for address:  ":1.20"  objectPath:  "/DataEngine/applicationjobs/JobView_1"
May 16 11:29:41 linux-yyix org.kde.kuiserver[1931]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_1"
May 16 11:29:41 linux-yyix org.kde.kuiserver[1931]: kuiserver: removing jobview from list, it finished
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:29:43 linux-yyix org.kde.KScreen[1931]: kscreen: Primary output changed from KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 447 , Name: "DVI-I-1" ) ( "DVI-I-1" )
May 16 11:30:01 linux-yyix cron[2634]: pam_unix(crond:session): session opened for user root by (uid=0)
May 16 11:30:01 linux-yyix systemd[2635]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
May 16 11:30:05 linux-yyix dbus[1288]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
May 16 11:30:05 linux-yyix dbus[1288]: [system] Successfully activated service 'org.opensuse.Snapper'
May 16 11:30:12 linux-yyix CRON[2634]: pam_unix(crond:session): session closed for user root
May 16 11:30:12 linux-yyix systemd[2636]: pam_unix(systemd-user:session): session closed for user root

eth0      Link encap:Ethernet  HWaddr 00:1F:BC:0F:0E:23  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1232 (1.2 Kb)  TX bytes:12486 (12.1 Kb)
          Interrupt:20 Memory:f5300000-f5320000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2117 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:196013 (191.4 Kb)  TX bytes:196013 (191.4 Kb)

vmnet1    Link encap:Ethernet  HWaddr 00:50:56:C0:00:01  
          inet addr:172.16.235.1  Bcast:172.16.235.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 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.254.1  Bcast:192.168.254.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                                                                    
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0                                                                    
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0                                                                 
          collisions:0 txqueuelen:1000                                                                                          
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

I did change the network settings in YAST to only include ipv4 addresses.

deano_ferrari · May 16, 2016, 9:15pm

Okay, the output does show that there are attempts to obtain a DHCPv4 lease, but it doesn’t come. I note that your have vmnet interfaces. Do you have a guest running as well? Do you have the guest network interface bridged to eth0? Maybe the router won’t issue more than one DHCPv4 address per physical interface for some reason. When you restart the machine wihtout a guest running, does eth0 then get a valid IPv4 address assigned?

vilanye · May 16, 2016, 9:29pm

I don’t have a guest running.

How would I go about deleting those to see if that fixes the issue?

vilanye · May 16, 2016, 9:58pm

Okay, I figured out how to shut down the vmware networks. ran ifconfig vmnetX down. Tried systemctl restart network and still no luck.

I had the vmnet set as bridged and there was no problem before I reset the cmos.

tsu2 · May 17, 2016, 5:59am

First,
I doubt that resetting the cmos likely affected your problems directly, but if you moved any hardware from one slot to another could have significant consequences for whatever was moved.

Next,
If you end up having a <multitude> of issues, the more expedient approach might be to simply re-install using a DVD (since your networking is affected. If your networking is working fine, then you can save effort by doing an online re-install (zypper dup). If you re-install using a DVD, you will be installing very old packages, so you should immediately update before doing anything else.

Before proceeding,
The question is, What is working or not working?
Is it only your Host that isn’t working (or working?)
What about your Guests, are any attached to your bridging network (vmnet1) working or not?
What about Guests connecting using NAT (vmnet8), is networking working or not?

If your HostOS is using Wicked, do you have your routing tab configured configured correctly?
If you don’t know, then post what your existing configuration looks like (or post a screenshot)

TSU

vilanye · May 20, 2016, 12:46am

I did a clean reinstall on Leap and networking is still not working. The VM networks never worked after I reset the CMOS and is moot since the reinstall as I don’t have vmware installed at the moment.

What isn’t working is eth0. Looking in network settings I have it set to DHCP IPv4 only, yet there is only an IPv6 address assigned to eth0.

I guess I am using wicked. As I said before whatever got installed by default. I am pretty sure it is wicked.

The routing tab is completely blank. Shouldn’t DHCP handle that? There is nothing set up in ip4 gateway and an empty routing table. The LAN address is 192.168.0.0

It is not the network card on my mobo as networking works fine in Windows(set up as dual boot).

Any advice is greatly appreciated!

vilanye · May 20, 2016, 8:16am

It seems to be solved.

I switched network setup method to network manager and back to wicked and I have networking again!