I have spent some more time on this problem which is that if I re-boot from running windows, closing windows and starting Leap 15.4 I have no network connection unless I unplug the machine and then restart it in Leap 15.4.
When I ran ip neigh the first time I had a message INCOMPLETE. It seems my problem might have been caused by the two L2/3 switches that are between my workstation and the DNS and DHCP servers set up in the UTM and the way in which ARP works.
I have my Leap 15.4 machine on a static IP but had not set the static address on the windows 10 machine so thought this might have been confusing the arp tables being used. I therefore set the windows machine to the same static IP that I have configured on the Leap 15.4 machine.
Sadly this has not solved my problem but I am showing the output of the various tests I have used to date in trying to diagnose the problem.
First the results from Leap 15.4 having just re-started from a windows which had dhcp when last booted:-
alastair@HP-Z640-1:~> ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname eno1
altname enp0s25
alastair@HP-Z640-1:~> ip neigh
192.168.169.129 dev eth0 INCOMPLETE
alastair@HP-Z640-1:~>
alastair@HP-Z640-1:~> ping 192.168.169.129
PING 192.168.169.129 (192.168.169.129) 56(84) bytes of data.
^C
--- 192.168.169.129 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12268ms
I then changed the windows machine to the same static IP and did ran the same tests on Leap 15.4:-
alastair@HP-Z640-1:~> ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname eno1
altname enp0s25
alastair@HP-Z640-1:~> ip neigh
192.168.169.129 dev eth0 lladdr 7c:5a:1c:82:f1:43 REACHABLE
alastair@HP-Z640-1:~>
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.287 ms
64 bytes from 192.168.169.129: icmp_seq=2 ttl=64 time=0.274 ms
64 bytes from 192.168.169.129: icmp_seq=3 ttl=64 time=0.331 ms
^C
--- 192.168.169.129 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2053ms
rtt min/avg/max/mdev = 0.274/0.297/0.331/0.024 ms
alastair@HP-Z640-1:~>
I then tried restarting Leap 15.4 again without having unplugged just in case a cache needed to be flushed:-
alastair@HP-Z640-1:~> ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname eno1
altname enp0s25
alastair@HP-Z640-1:~>
alastair@HP-Z640-1:~> ip neigh
192.168.169.129 dev eth0 lladdr 7c:5a:1c:82:f1:43 DELAY
alastair@HP-Z640-1:~>
alastair@HP-Z640-1:~> ping 192.168.169.129
PING 192.168.169.129 (192.168.169.129) 56(84) bytes of data.
From 192.168.169.137 icmp_seq=3 Destination Host Unreachable
From 192.168.169.137 icmp_seq=4 Destination Host Unreachable
From 192.168.169.137 icmp_seq=5 Destination Host Unreachable
From 192.168.169.137 icmp_seq=6 Destination Host Unreachable
From 192.168.169.137 icmp_seq=7 Destination Host Unreachable
From 192.168.169.137 icmp_seq=8 Destination Host Unreachable
^C
--- 192.168.169.129 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8124ms
pipe 3
alastair@HP-Z640-1:~>
Still no internet connection. Finally I unplugged the system and then started Leap 15.4 to resume this thread.