Thank you very much @bonnietwin and @bbitsch
I have set ALL network cards in APU1 to wol=g and powered down the box:
On APU1 I did executed these commands:
ethtool -s green0p0 wol g
ethtool -s green0p1 wol g
ethtool -s green0p2 wol g
APU2 card connected to APU1 now goes in forwarding state after APU1 halts/power off:
Jan 13 22:10:05 silver-x86-64 kernel: igb 0000:02:00.0 green0p1: igb: green0p1 NIC Link is Down
Jan 13 22:10:05 silver-x86-64 kernel: green0: port 2(green0p1) entered disabled state
Jan 13 22:10:06 silver-x86-64 kernel: igb 0000:02:00.0 green0p1: igb: green0p1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: RX/TX
Jan 13 22:10:06 silver-x86-64 kernel: green0: port 2(green0p1) entered blocking state
Jan 13 22:10:06 silver-x86-64 kernel: green0: port 2(green0p1) entered forwarding state
And, as expected, the WOL command from APU2 to APU1 now works: my script that powers it on and check that samba is up reported success:
./RedFire up
is_alive: ping a.b.c.d attempt 6. smbclient:Seems samba on a.b.c.d is up
Thank you - I will try to go back to 4.14.03, BUT the APU1 needs flashrom 0.9 to accomplish that.
And, up to now, I failed to find a binary - I know I had a TinyCore bootable USB somewhere, but I did not found it yet.
The flashrom 1.2 that is shipped now in core 162 does not work - see this post on errors thrown on APU1. How update the BIOS from IPFire with PC Engines APUx - #15 by hjkl
So until I found the flashrom 0.9 I will have to run a cron job to set wol=g on all cards from APU1
Thank you again!
Late edit: found my TinyCore USB Boot and that had on it FLashROM v0.9.7-r1711-APU: I have downgraded APU1 bios to v4.12.0.6. that was on the USB disk with TinyCore.
Board : PC Engines apu1
HW Version : 1.0
Serial : -64
BIOS Version: v4.12.0.6 (10/29/2020)
Later edit: neither BIOS Version: v4.12.0.6 (10/29/2020) or BIOS Version: v4.14.0.3 (08/10/2021) put Wake-on: g
Board : PC Engines apu1
HW Version : 1.0
Serial : 1012235
BIOS Version: v4.14.0.3 (08/10/2021)
I tested both - all 3 network cards go with Wake-on: d after reboot.
So I have added in /etc/sysconfig/rc.local these lines.
ethtool -s green0p0 wol g
ethtool -s green0p1 wol g
ethtool -s green0p2 wol g
It seems that new kernel does that and not the BIOS firmware…
But I am not an expert…
Thank you very much!