Multicast Wake on LAN with Fujitsu Lifebook E556
-
@deimos So you say they all have the same version of bios installed. Are there updates available that may fix wol? I’m running out of ideas here, I don’t think its a fog issue at this point.
-
@george1421 said in Multicast Wake on LAN with Fujitsu Lifebook E556:
@deimos So you say they all have the same version of bios installed. Are there updates available that may fix wol? I’m running out of ideas here, I don’t think its a fog issue at this point.
I´ll report, if I figured out the reason. I now do not think its a fog issue, too.
-
@Deimos Trying to nail this down at bit more… Can you connect a machine that does not wol to the switch port where the machine wakes up properly?
As well a question. Do I get this right. Machines waking up do this fine every time you try. And machines that don’t never do wol at all. Or is it a random thing, sometimes works and then not for the same machine?
-
@sebastian-roth said in Multicast Wake on LAN with Fujitsu Lifebook E556:
@Deimos Trying to nail this down at bit more… Can you connect a machine that does not wol to the switch port where the machine wakes up properly?
As well a question. Do I get this right. Machines waking up do this fine every time you try. And machines that don’t never do wol at all. Or is it a random thing, sometimes works and then not for the same machine?
I’ll test that as soon as the stressful exam time is over. In February I will start a comprehensive test and report the results.
-
Just bumping this so we don’t loose track of it. @Deimos Let us know when you have new information on this.
-
@sebastian-roth said in Multicast Wake on LAN with Fujitsu Lifebook E556:
Just bumping this so we don’t loose track of it. @Deimos Let us know when you have new information on this.
Jap, I will. But now we have other FOG problems. “HTTP 500 Internal Server Error”. I will make new thread.
-
A simple test environment did not make things easier. All 6 computers have deployed via WOL in multicast without difficulty.
Previously, when multicast with about 25 computers some have failed at the WOL, and I can´t say what it might have been. All computers have identical settings in the BIOS, all had the same image history etc.
I’ll keep working on it.
Maybe it´s still a 1.4.0 problem. I’m a little bit scared to update the FOG, because failure would have serious consequences and work, and there’s really no time for it.
-
@deimos I guess we need to get a packet dump of the WOL packets to rule out FOG being the issue. Please install
tcpdumpand then runtcpdump -w /tmp/wol.pcap port 9(as root - leave the command running). This will only capture WakeOnLAN packets. Then schedule a Multicast Task for your 25 clients and wait for most of them to boot up, then stop tcpdump (ctrl + c). Please upload the wol.pcap to your dropbox/fileshare and post a link here. -
Today is test day.
I have five devices where WOL used to work, and five devices that do not mess with WOL. I will group these together and then start a multicast task with the processes mentioned by @SebastianRoth in the background.
Also I will test a multicast WOL with our HP ProBooks 650G1.
-
The command tcpdump -w /tmp/wol.pcap port 9 doesn´t work. Error message:
“NFLOG link-layer type filtering not implemented.”With command tcpdump -w /tmp/wol.pcap it works.
But the file is crashed.
Content: "Ôò¡ ï "I´ll try again and wait till the four WOL-working clients are deploying.
-
So, now none of the clients are booting with WOL.
Restarted service FOGMulticastManager.
tcpdump doesn´t make any other log either.
-
@Deimos What do you mean by file is crashed. The dump file is not ascii readable text but a binary format. You need to load that in wireshark for example. Or upload to your gdrive/dropbox and post a link so we can have a look.
-
@sebastian-roth said in Multicast Wake on LAN with Fujitsu Lifebook E556:
@Deimos What do you mean by file is crashed. The dump file is not ascii readable text but a binary format. You need to load that in wireshark for example. Or upload to your gdrive/dropbox and post a link so we can have a look.
It´s only 1KB and the message after stopping the process is
Last login: Fri Feb 16 08:28:52 2018 from CLIENT.DOMAIN
[root@fog-sig-bund-de ~]# sudo tcpdump -w /tmp/wol.pcap
tcpdump: listening on nflog, link-type NFLOG (Linux netfilter log messages), cap ture size 262144 bytes
^C0 packets captured
0 packets received by filter
0 packets dropped by kernel
[root@fog-sig-bund-de ~]#I am not sure if this is expected.
-
I will upload the file on my homepage later.
-
So I looked at the file with my wireshark at home (forbidden in office)
There´s no data.I will set up a new fog from scratch and try to WOL the devices. I will report later.
