RokeJulianLockhart@s1e8h4:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp75s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 9c:6b:00:16:bb:f4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.179/24 brd 192.168.1.255 scope global dynamic noprefixroute enp75s0
valid_lft 41421sec preferred_lft 41421sec
inet6 fe80::8ef0:8cf4:fcf8:cda9/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp69s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 8c:b8:7e:a0:65:86 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.147/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp69s0
valid_lft 41432sec preferred_lft 41432sec
inet6 fe80::9c11:3de0:4422:bc0f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
RokeJulianLockhart@s1e8h4:~>
demonstrating that I do have multiple network devices installed, and despite iw previously showing enp75s0 as phy0 (which was necessary to enable WOL). Any ideas why?
Yet it’s the only way to enable WOL, and WOL has never worked on wireless devices. Why would it be able to control WOL if it doesn’t support Ethernet, @arvidjaar?
PS /home/RokeJulianLockhart> sudo iw phy0 wowlan show
WoWLAN is disabled.
PS /home/RokeJulianLockhart> sudo iw phy0 wowlan enable magic-packet
PS /home/RokeJulianLockhart> sudo iw phy0 wowlan show
WoWLAN is enabled:
* wake up on magic packet
PS /home/RokeJulianLockhart> sudo iw phy1 wowlan show
WoWLAN is disabled.
PS /home/RokeJulianLockhart> sudo iw phy1 wowlan enable magic-packet
PS /home/RokeJulianLockhart> sudo iw phy1 wowlan show
WoWLAN is enabled:
* wake up on magic packet
PS /home/RokeJulianLockhart>
It definitely appears to work for both Ethernet and Wi-Fi.
@malcolmlewis, this computer also functions as a Wi-Fi repeater, because I need the ability to run this network in a decentralized manner (except of course for the gateway) in addition to the dedicated repeaters I posses. I’ve never had any issues until now, with this tool.
@malcolmlewis, I’ve never used it without an Ethernet cable connected. It appears to work regardless of Ethernet connectivity, it’s just erratic for, presumably, another reason. That’s what I’m trying to discern - it obviously does support Ethernet, or it and most articles online are misidentifying Ethernet as Wi-Fi.
@rokejulianlockhart trying to understand your setup… So clients connect to those two wifi devices and bounce is elsewhere? O are you just using wifi or ethernet based on priority?
@malcolmlewis, I didn’t configure those network devices manually. My MB came with a Wi-Fi module, but it was inadequate, so I installed a separate one in a PCI-E slot, because I need it to act as an AP for nearby devices. I additionally use Ethernet for the majority of communications to the network gateway. I connected all to my network using the KDE Plasma 5 network plasmoid.
I expect that network packets are routed between devices based upon priority determined automatically factoring in the speed and throughput of each device. For instance, I expect that Ethernet is used due to its superior speed until its capacity has been reached, and then network packets are either withheld/dropped, or routed via Wi-Fi instead. However, I have no idea of what actually occurs — the system configured this.
Have you any idea of how to verify how the order of priority is determined?
Yeah, @malcolmlewis. It only acts as an AP when I want it to. Otherwise, the wireless NICS sit mostly idle and can accept incoming connects like usual. Heck, sometimes I use one or both as clients for another AP - due to the poor internet around here, sometimes I connect this PC to my smartphone’s hotspot instead.
