Just returned to machine now and am here if you have had a chance to read my latest post.
and here is the configuration you requested:-
alastair@HP-Z640-1:~> sudo cat /etc/sysconfig/network/ifcfg-eth0
[sudo] password for root:
BOOTPROTO='dhcp4'
STARTMODE='hotplug'
ZONE='work'
alastair@HP-Z640-1:~>
Try changing startmode to
STARTMODE='auto'then reboot and report back.
Tried and now have STARTMODE=āautoā but on re-booting I still have to unplug.
I am not sure how my system had STARTMODE=āhotplugā it might have been from when I was working on virtual machine but I certainly did not intentionally edit ifcfg-eth0.
What I have not been able to work out is how to include wickedd-nanny to get the hotplug to work.
As I recall STARTMODE=āautoā should supersede on-boot but will try that instead.
No joy with on-boot and then no lights on NIC so had to revert to STARTMODE=āautoā and then unplug and replug lan connection.
With your help I could try getting wickedd-nanny to work but meanwhile it is a good job I am next to the machine so I can unplug and plug in the lan.
I have found that if I shut down windows10 using the āred buttonā which commands shutdown /s /t3 which is intended to make it possible to open the system with WoL then when I boot into Leap 15.4 I cannot ping the wan (8.8.8.8) even if I unplug and re-plug the lan.
If I shutdown windows10 using the shutdown button I can no longer start the machine with WoL but if I restart using the machine with the hardware button and boot to Leap 15.4 I still have no connection unless I then unplug and re-plug the lan.
Clearly the power state of the machine is one of the factors but this should not be so if I shut down from Leap15.4. In fact if I shut down from Leap 15.4 I can then wake up the machine using WoL but still must unplug and re-plug the lan cable before I get an internet connection.
I have been checking through the basic networking for leap references trying to get my lan connection to work correctly.
It seems the documentation is slightly in conflict with what I presently have on my leap 15.4 system because the reference says:-
... trueBlockquote By default, the nanny daemon is active on the system. It is enabled in the /etc/wicked/common.xml configuration file:
This setting causes ifup and ifreload to apply a policy with the effective configuration to the nanny daemon; then, nanny configures wickedd and thus ensures hotplug support. It waits in the background for events or changes (such as new devices or carrier on).
Blockquote
But this is not what I have. Other info in the man pages suggest I must enable wickedd-nanny but all this is getting too much.
Since STARTMODE=āautoā does not work, please could somebody help me getting STARTMODE=āhotplugā to work.
Should I start a new thread on this problem perhaps?
Yes, it does seem to be a quirk of the NIC hardware in your machine.
Hi Dean,
OK but I had rather hoped you would be able to look into the problem further. I believe the first hurdle is sorting out the ifconfig hotplug issue and getting nanny to work. Please can you help me with this as the manual is not correct and I am struggling with this.
Regards,
Budge
I have returned to this because thread because my problem may be related. I have two almost identical Z640 machines in the same dual boot environment and today I was able to compare the two. The second machine does not have the same problem and one difference between them is that the problem machine had been used when I was trying a virtual machine setup.
Although I am not now using this I see from looking at the interfaces on the firewall that there are several interfaces which should not be there as they are no longer needed. These are eth1 (which doesnāt exist but was for an USB dongle to give another network connection,) a docker interface which I didnāt set up intentionally but may have been created when I was working on the virtual machine and another interface, the name of which I forget and do not have in front of me.
My question is how may I remove these redundant interfaces please?
Do you mean from firewalld? Rules affecting unused interfaces should have no impact, but you can use firewall-cmd (CLI) or firewall-config (graphical UI) to configure or remove as desired. The docker0 interface appears in recent firewalld configuration by default (to serve those that may be using it). I just ignore it as it has no effect in my systems.
From a network configuration POV, you are using wicked and can use YaST to remove any unwanted interface configuration.
Hi and thanks for staying with me on this.
I had asked because I am shooting in the dark here and last night I couldnāt get any internet connection on at all on Leap 15.4 even after unplugging and re-plugging the lan cable. (Windows works fine so hardware seems OK).
In desperation I wondered why four interfaces are showing on firewall but only one when I use Yast. I looked for network interfaces but the Leap 15.4 documentation is not helpful so thanks for explaining the docker interface. The other one I had forgotten in my last post is br which must have been left over from my VM test a while ago and that was what I wanted to clear out.
I have been through all the command you suggested and tried static and dhcp with hotplug and auto and even put back the usb dongle with many re-boots on the way but unless there are other command I should try I am stuck.
Bottom line for me now is fresh install as I am too ignorant on the details of how the connection is made and what is going on in the background which I am missing and my real work is piling up!
Hi Dean,
Decided to do a new installation to clear any clutter and am trying Leap 15.5 just for fun.
Full of confidence I was able to identify a problem with the DNS configuration and am working on correct solution. At least I am moving forward. Once resolved I shall give you feedback to close this thread.
Thanks once more for you help.
Budge.
OK, I think I have found one problem. I have been comparing one HP Z640 which has an almost identical spec with the āproblemā machine. Both were configured using Yast but the machine (HP-Z640-2) which works has a Network Setting with two devices shown:-
br0 configured with the static IP and
eth0 which has no ip address and a note stating included in br0.
The static host name is showing correctly as HP-Z640-2 and on this machine I have not allowed DHCP to set the Hostname. All is working as expected and I have no problems with dual booting and wol.
On the first machine which has been giving me trouble I think the trouble is with br0 which is not being used and has been left over from when I had been using the dongle. The only way I can get the machine to connect at present is to allow DHCP to set the Hostname. This is wrong and I need sort it out.
With reluctance I am accepting that my mobo network port has an intermittent hardware problem.
I am using the USB dongle for network connection now and will buy a network card.
Thatās all for now.
Budgie2
Case closed. Found the problem which was no less than two Trunk switches away and was an eroded contact on one of the older cat 5 cable RJ45 connections. I re-made all the RJ45 connections on the whole route using a better quality sockets and so far all is well.
Once again I apologise for all the hassle and for blaming my otherwise great Z640.
Special thanks to Dino for his patience and not giving up on me.
Regards,
Alastair.