You are not logged in.
- Topics: Active | Unanswered
#1 2020-04-26 21:28:29
- lukestu
- Member
- Registered: 2020-04-26
- Posts: 3
WOL Magic Packet not working with via_velocity NIC
I'm brand-new to Arch, but not to linux. Last week I decided to update my home NAS and switch to Arch from Debian, in this case Debian Jessie so it was a desperately needed update. Almost everything is working well and I'm very impressed with Arch so far.
I do have this one issue though...wake-on-lan is not working for either of the two onboard nics and I've spent the whole weekend trying to get it to work, read the (excellent) arch wiki's on the subject and numerous forums posts etc. It worked perfectly with my previous debian installation, and still does when I connect that drive back, so I can safely say it's not the bios.
See below for logs and output, but to summarize:
* Hardware: VIA EDEN X2 mobo with dual 1GBE NICs - old but fine for a nas
* When I run systemctl suspend, the nas suspends. Lights on the nics stay on, but only pressing the power button wakes it. Network does not work after this, however, until I reboot.
* Used ethtool to set g
* Used networkd .link to run ethtool to set magic packet for enp1s0 (the only nic I want to wake on lan)
* tried both vanilla (5.6.6) and lts (5.4.34) kernels
* edited udev to run ethtool -s enp1s0 wol g
* Added modprobe.d file to add option to set wol directly: options via_velocity wol_opts=0
* nc --udp --listen --local-port=9 --hexdump confirms the magic packet reaches the interface.
* Nas is configured only for local /24 network.
* Nas is headless and since no network is available after resume, I can't see those logs. I can make a plan if they are truly necessary.
None of the above allows the nas to be woken from sleep by wol magic packet. As I say, this works perfectly in an old Debian 8 installation, worked from the get-go. Anything else I can try? Any help is very much appreciated...!
ethtool output:
[root@nas ~]# ethtool enp1s0
Settings for enp1s0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No Supports auto-negotiation: Yes
Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: No Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: puag
Wake-on: g
Current message level: 0x00000002 (2)
probe
Link detected: yesjournalctl -b | grep network:
[root@nas ~]# journalctl -b |grep network
Apr 26 22:14:45 nas kernel: drop_monitor: Initializing network drop monitor service
Apr 26 22:14:51 nas systemd-networkd[342]: Enumeration completed
Apr 26 22:14:51 nas systemd-networkd[342]: enp1s0: Interface name change detected, enp1s0 has been renamed to eth0.
Apr 26 22:14:51 nas kernel: audit: type=1130 audit(1587932091.926:24): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 22:14:51 nas audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 22:14:51 nas systemd-networkd[342]: enp2s0: Interface name change detected, enp2s0 has been renamed to eth1.
Apr 26 22:14:51 nas systemd-networkd[342]: eth1: Interface name change detected, eth1 has been renamed to enp2s0.
Apr 26 22:14:52 nas systemd-networkd[342]: eth0: Interface name change detected, eth0 has been renamed to enp1s0.
Apr 26 22:14:52 nas systemd-networkd[342]: enp1s0: IPv6 successfully enabled
Apr 26 22:14:52 nas systemd-networkd[342]: enp1s0: Link UP
Apr 26 22:14:52 nas systemd-networkd[342]: enp1s0: Gained carrier
Apr 26 22:14:53 nas systemd-networkd[342]: enp1s0: Gained IPv6LL
Apr 26 22:15:05 nas audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 22:15:05 nas kernel: audit: type=1130 audit(1587932105.276:29): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 22:15:05 nas systemd-networkd[342]: ipsec0: Link UP
Apr 26 22:15:05 nas systemd-networkd[342]: ipsec0: Gained carrier
Apr 26 22:16:19 nas systemd[425]: Listening on GnuPG network certificate management daemon.
Apr 26 22:19:01 nas systemd-networkd[342]: enp2s0: Link UP
Apr 26 22:19:01 nas systemd-networkd[342]: enp2s0: Gained carriermodinfo via_velocity:
[root@nas ~]# modinfo via_velocity
filename: /lib/modules/5.4.34-1-lts/kernel/drivers/net/ethernet/via/via-velocity.ko.xz
description: VIA Networking Velocity Family Gigabit Ethernet Adapter Driver
license: GPL
author: VIA Networking Technologies, Inc.
srcversion: F545FF7EA5B29EEEA71FF92
alias: pci:v00001106d00003119sv*sd*bc*sc*i*
alias: of:N*T*Cvia,velocity-vt6110C*
alias: of:N*T*Cvia,velocity-vt6110
depends:
retpoline: Y
intree: Y
name: via_velocity
vermagic: 5.4.34-1-lts SMP mod_unload
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 56:4E:47:D3:09:37:E6:14:AE:FB:CC:2F:E1:88:56:6C:2A:39:75:70
sig_hashalgo: sha512
signature: 3D:70:92:5E:C7:BD:40:F8:B2:BA:3B:B8:61:C3:C8:18:D4:5E:83:C1:
4B:4E:4E:97:30:85:49:AB:D3:B9:64:0B:A1:9B:74:23:97:7A:C6:42: E9:35:CB:B5:FF:B8:53:DB:CF:7A:76:1C:D5:DD:7A:CF:91:94:2D:5D:
A8:96:72:27:1A:E6:79:91:F3:3B:EE:FF:1A:1D:1E:EA:55:BF:E6:6A:
61:2E:1E:B0:7F:CF:AF:BD:72:7F:BE:6C:32:FA:37:7A:6B:27:7A:9E:
98:D6:20:93:48:29:07:1F:EB:52:47:2F:FC:4F:30:D1:9B:83:EC:7E:
3B:AD:20:C4:2D:E5:40:74:1F:F9:87:6B:DD:CB:0F:4F:F8:A6:64:49:
CC:C8:E5:17:E1:3B:38:71:EA:43:0C:82:AE:DA:9E:F8:97:C1:D9:F1:
8E:06:8D:B8:1B:A9:0C:55:B4:B8:34:A8:D7:9A:5B:CA:70:B5:B3:C6:
0B:EB:F4:F4:5E:E6:40:ED:66:F7:D7:06:FB:30:F9:52:7B:1D:FE:CD:
04:06:13:22:C2:FD:EF:D8:EC:21:62:F8:0C:62:8D:1D:99:DE:AF:FD:
81:07:18:7E:91:04:2C:85:FE:AC:09:43:8F:44:36:1D:10:8B:07:79:
66:A8:53:50:48:EA:E0:0E:52:BA:63:C8:37:F5:4D:0F:BC:82:19:9E:
E6:BF:76:EC:5A:8C:20:9D:19:39:8D:A8:C2:9C:49:2C:F8:31:46:AA:
B0:8B:9C:A0:05:C0:05:20:99:6D:F1:CA:53:AB:55:6B:3A:29:D0:08: 36:3F:D5:D9:B3:74:90:F9:4B:2A:36:40:B5:F0:11:A5:F3:61:96:A0:
05:3A:3B:C7:6F:1A:FC:60:80:59:55:40:6D:D6:E5:91:93:82:0A:63: E8:A5:88:18:B6:53:6A:4A:C2:65:72:CB:88:20:BE:09:0F:34:50:1B:
5D:C4:20:73:54:63:73:01:60:E4:B0:B7:0F:41:6C:BC:5C:D3:AB:8A:
23:CC:3C:83:67:45:3F:52:D8:57:2F:E9:D0:BA:0D:4A:66:A9:F8:B9:
C5:EA:F2:58:46:CB:09:21:C6:31:EB:99:BF:84:0A:C8:82:1F:7B:17:
3F:5A:8F:B3:F6:CC:9B:D4:A7:D9:F3:15:84:70:BC:0D:36:58:F6:84:
67:A6:15:26:36:18:E8:CD:12:D3:6E:A3:DC:82:0A:00:AB:E7:E2:CC:
8C:EA:65:1E:55:39:33:89:C3:00:AF:D0:B7:44:FB:22:42:27:FE:5C:
D6:70:4A:3E:8E:BE:CF:E9:D3:B5:07:E3:62:70:B5:96:8A:94:7B:FD:
D3:D9:FC:AB:AD:A9:21:30:EA:25:79:E2
parm: RxDescriptors:Number of receive descriptors (array of int)
parm: TxDescriptors:Number of transmit descriptors (array of int)
parm: rx_thresh:Receive fifo threshold (array of int)
parm: DMA_length:DMA length (array of int)
parm: IP_byte_align:Enable IP header dword aligned (array of int)
parm: flow_control:Enable flow control ability (array of int)
parm: speed_duplex:Setting the speed and duplex mode (array of int)
parm: wol_opts:Wake On Lan options (array of int)
parm: rx_copybreak:Copy breakpoint for copy-only-tiny-frames (int)/etc/modprobe.d/velocitywol.cond
[root@nas ~]# cat /etc/modprobe.d/velocitywol.conf
options via_velocity wol_opts=0networkd .link:
[root@nas ~]# cat /etc/systemd/network/50-wired.link
[Match]
MACAddress=00:1f:f2:09:5a:8e
[Link]
NamePolicy=kernel database onboard slot path
MACAddressPolicy=persistent
WakeOnLan=magicLast edited by lukestu (2020-04-26 21:35:50)
Offline
#2 2020-04-27 11:26:52
- lukestu
- Member
- Registered: 2020-04-26
- Posts: 3
Re: WOL Magic Packet not working with via_velocity NIC
Further developments:
* I can wake the nas using the unconfigured interface - enp2s0. This has no IP, route, or any configuration in networkd.
* If I make a basic .network file for enp2s0 with DHCP, it stops responding to magic packets.
Networkd at fault?
Offline
#3 2020-04-27 13:51:31
- lukestu
- Member
- Registered: 2020-04-26
- Posts: 3
Re: WOL Magic Packet not working with via_velocity NIC
After battling with this way too much, I tossed out networkd and manually configured my network interfaces with scripts using iproute2. Now WOL with magic packets works perfectly.
I guess thats why it's called 'bleeding edge' ... one tends to bleed 
Not marking this solved because it isnt really...
Offline