I no longer have a connection to my network. I cannot ping other devices on the same subnet.
Since this computer used to work I have a problem. I have tried both static ip and dhcp using wicked and NM and am stuck.
I have reverted to wicked with static IP and copied the details from my working Leap 15.4 configuration which is on the same network with ip addr giving me:- eth0 UP and the address which I put in wicked.
I cannot ping any other address on the subnet or the route address but if I reboot this computer to windoze the connection works so I assume the copper and switches are all OK.
I am sure there will be an obvious error but cannot think where to look and not having the connection running makes it difficult to communicate here.
I have tried turning off the firewall but this made no difference but I see there are more interfaces defined than are now required, I assume from when I was working with virtual machine. No idea how to remove them and eth0 is still present.
What tool should I try for troubleshooting now?
If it’s a static IP and you can use wicked, why not configure it with YaST? Choose your device, delete all the others, click through the tabs for the settings (esp. default gateway, hostname, DNS,…). If you know a little bit, it’s quite self explaining. The YaST modules used to also take care of the firewall settings.
For any further advice, I assume more details need to be provided.
No offence intended. Between the group of colleagues and family on our network there are several versions of Windows being used and windoze has been my shorthand when referring to a version has not been critical.
Hi and thanks for reminding me. I had been through these again last night. I had no luck with static IPs or DHCP using wicked and similarly the same result with NM. It is now clear that DHCP is not getting an address and a static IP is not even seeing other devices on my subnet. I am looking into the route now.
Will do more work before posting more info. Using USB is a pain because I have to go to the machine location as my ancient KVM switch doesn’t handle USB connections.
Strange but after a brief respite the problem machine has reverted to 1024 x 768 but my workstation is working fine.
Many thanks for your patience.
Budge
Hi,
I am trying to make my network connection using NM with dhcp providing the address. I get almost nothing.
No ip address and no route. Here is what I have:-
alastair@HP-Z640-1:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname eno1
altname enp0s25
inet6 fe80::c28d:55b6:65bd:f16e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
alastair@HP-Z640-1:~> ip addr
and for the route nothing:-
alastair@HP-Z640-1:/etc/sysconfig/network> ip route
alastair@HP-Z640-1:/etc/sysconfig/network>
I have tried stopping the firewall but still no joy.
It has occurred to me that there might be a network conflict using the static IP so this is why I used dhcp which is what the machine uses when booted to Windows10.
I am also wondering whether there may have been some previous confusion by me over names for this machine but am not sure where an older name would be lingering.
Finally I have checked the UTM IPv4 lease table and see that the problem machine has the IP confirmed by netstat -r on the windows10 machine and has the MAC address as expected.
I am wondering whether this is causing a problem although it never has before.
I am going round in circles here.
Finally please forgive my OT chat. Just a BTW last night.
As a last resort I connected the usb/rj45 dongle I had to give me a second NIC as there is only one in the Z640.
In the end I unplugged the on-board NIC connection and still using NM but with static and different address from the one I have used for the original connection, rebooted.
I now have a network connection an (OT & BTW, can now select the higher resolution display).
My initial thought is that the on board NIC MAC address is bound to the original static address and name have been retained somewhere even after I had shut down window10 and started Leap 15.4.
As I stated at the outset I have never had this problem previously even after I moved the machine and didn’t use the dongle an virtual machine so something has changed. I hope those more knowledgeable than me can shine more light on the root of the problem.
Another thought. A while ago I had a problem getting a Z640 to wake on line and was given detailed advice on how to create and use a button on my desktop which shuts down the windows10 system. It has occurred to me that in the shut down condition described, the computer is holding the MAC address information and possibly this is preventing my Leap 15.4 system from accessing the NIC.
Hope I can get to the bottom of this whatever the problem and meanwhile am running with USB network dongle when running Leap 15.4 and the NIC when running windows10.
Good question but…
I did try ifdown ethe0 && ifup eth0 this morning when using wicked but no success then.
I am at present connecting using the USB dongle network adaptor with NM and a static IP. here are my addresses.
alastair@HP-Z640-1:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname eno1
altname enp0s25
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 7c:c2:c6:33:10:d0 brd ff:ff:ff:ff:ff:ff
altname enp0s20u3
inet 192.168.169.159/25 brd 192.168.169.255 scope global noprefixroute eth1
valid_lft forever preferred_lft forever
inet6 fe80::f37e:276e:9090:b20e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
alastair@HP-Z640-1:~>
I can try it all again but I have no idea about the lease as the UTM will keep the lease for a long time and usually only release the address if not in use and no other port available within the subnet.
I can look into the UTM controls but didn’t find a button to enable me to kick off a lease. There must be one but not found it yet.
If I wish to continue now I must shut down, disconnect the USB dongle and then boot into Leap 15.4 which may mean I cannot easily communicate on this machine. If I press on, and re-boot should I first boot into windows10 and shut down absolutely, ie not use the new red button. It will mean of course that I cannot wake the machine remotely unless somehow the Leap15.4 is woken up.
What is your best advice before I lose contact on this machine?
OK, I have moved HP_Z640_1 to my room and connected to network using only the built-in NIC.
I was able to boot leap15.4 and connect but this had been left with NM running so your ifcfg commands were refused as wicked was not enabled.
I was able to restart and boot to windows10 and all good.
I restarted again and selected Leap15.4 and had no difficulty until I found there was internet connection.
I changed the network configuration from NM to wicked and re-booted. Still no internet connection. I then tried your suggested command line as root:-
IBMW530:~ # ifdown eth0 && ifup eth0
<13>Jan 25 21:29:02 root: Network is managed by 'NetworkManager.service' -> skipping
IBMW530:~ #
Even after a reboot I cannot shift this. I can however restart and select windows10 so what do I do to unstick this. I suspect the problem is related to your help with stopping windows10 in a way that allows me to use wol.
As I recall the “red button” created from the hint I had included the windows command
shutdown /s /t3
So this put the windows machine into the t3 state. I am sure this has worked until recently but now the windows machine seems to be in a different state which locks my network card.
I appreciate this is now an OT windows question and will start googleing.
Budge
OK the red button shutdown still turns off the computer and can still be woken by wol but when booting and defaulting to Leap15.4 there is definitely no network connection although the command to shut down and up appears to be working as I now get:-
I have tried changing the windows10 configuration power management to turn off wol and enable shutdown and used the shutdown button. I then restarted the machine and allowed it to boot into Leap15.4. Still no internet connection but I then had a route and could ping the subnet gateway connection IP.
Since all the booting didn’t sort the problem I unplugged the lan cable and plugged it back in and now I have a connection to the internet but when I run the down up command as root I get:-
Here are the results of the three basic test when I have booted from system being off after shutting down from Leap 15.4 but not having unplugged the power. At this stage there is no internet connection and I cannot ping 8.8.8.8:-
alastair@HP-Z640-1:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname eno1
altname enp0s25
inet 192.168.169.249/25 brd 192.168.169.255 scope global eth0
valid_lft forever preferred_lft forever
alastair@HP-Z640-1:~> ip route
192.168.169.128/25 dev eth0 proto kernel scope link src 192.168.169.249
alastair@HP-Z640-1:~> ping 192.168.169.129
PING 192.168.169.129 (192.168.169.129) 56(84) bytes of data.
64 bytes from 192.168.169.129: icmp_seq=1 ttl=64 time=0.348 ms
64 bytes from 192.168.169.129: icmp_seq=2 ttl=64 time=0.293 ms
64 bytes from 192.168.169.129: icmp_seq=3 ttl=64 time=0.325 ms
64 bytes from 192.168.169.129: icmp_seq=4 ttl=64 time=0.296 ms
^C
--- 192.168.169.129 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3057ms
rtt min/avg/max/mdev = 0.293/0.315/0.348/0.022 ms
alastair@HP-Z640-1:~> sudo ls -l /etc/sysconfig/network/ifcfg*
[sudo] password for root:
-rw-r--r-- 1 root root 132 Apr 25 2022 /etc/sysconfig/network/ifcfg-br0.bak
-rw-r--r-- 1 root root 50 Jan 23 22:03 /etc/sysconfig/network/ifcfg-eth0
-rw------- 1 root root 81 Apr 21 2022 /etc/sysconfig/network/ifcfg-eth0.bak
-rw-r--r-- 1 root root 54 Apr 24 2022 /etc/sysconfig/network/ifcfg-eth1.bak
-rw------- 1 root root 147 Oct 28 05:26 /etc/sysconfig/network/ifcfg-lo
-rw-r--r-- 1 root root 21738 Aug 1 14:28 /etc/sysconfig/network/ifcfg.template
alastair@HP-Z640-1:~>
After unplugging the lan cable and re-plugging I get an internet connection immediately and can then ping 8.8.8.8. The other tests remain the same as far as I can see:-
alastair@HP-Z640-1:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname eno1
altname enp0s25
inet 192.168.169.249/25 brd 192.168.169.255 scope global eth0
valid_lft forever preferred_lft forever
alastair@HP-Z640-1:~> ip route
default via 192.168.169.129 dev eth0
192.168.169.128/25 dev eth0 proto kernel scope link src 192.168.169.249
alastair@HP-Z640-1:~> ping 192.168.169.129
PING 192.168.169.129 (192.168.169.129) 56(84) bytes of data.
64 bytes from 192.168.169.129: icmp_seq=1 ttl=64 time=0.325 ms
64 bytes from 192.168.169.129: icmp_seq=2 ttl=64 time=0.315 ms
64 bytes from 192.168.169.129: icmp_seq=3 ttl=64 time=0.325 ms
64 bytes from 192.168.169.129: icmp_seq=4 ttl=64 time=0.262 ms
^C
--- 192.168.169.129 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3077ms
rtt min/avg/max/mdev = 0.262/0.306/0.325/0.026 ms
alastair@HP-Z640-1:~> sudo ls -l /etc/sysconfig/network/ifcfg*
[sudo] password for root:
-rw-r--r-- 1 root root 132 Apr 25 2022 /etc/sysconfig/network/ifcfg-br0.bak
-rw-r--r-- 1 root root 50 Jan 23 22:03 /etc/sysconfig/network/ifcfg-eth0
-rw------- 1 root root 81 Apr 21 2022 /etc/sysconfig/network/ifcfg-eth0.bak
-rw-r--r-- 1 root root 54 Apr 24 2022 /etc/sysconfig/network/ifcfg-eth1.bak
-rw------- 1 root root 147 Oct 28 05:26 /etc/sysconfig/network/ifcfg-lo
-rw-r--r-- 1 root root 21738 Aug 1 14:28 /etc/sysconfig/network/ifcfg.template
alastair@HP-Z640-1:~>
I am working at machine with no KVM or switches in between so much easier to try different options.
Hope this helps