Package Details: sqm-scripts 1.5.0-1

Git Clone URL: https://aur.archlinux.org/sqm-scripts.git (read-only, click to copy)
Package Base: sqm-scripts
Description: SQM scripts traffic shaper
Upstream URL: https://github.com/tohojo/sqm-scripts
Licenses: GPL
Submitter: Chocobo1
Maintainer: Chocobo1
Last Packager: Chocobo1
Votes: 2
Popularity: 0.192167
First Submitted: 2018-12-26 10:12
Last Updated: 2021-01-04 12:27

Latest Comments

Slenderchat commented on 2021-02-17 06:00

Current version of .service file shipped with this package breaks systemd-networkd-wait-online.service and possibly NetworkManager-wait-online.service as well. This is happening because sqm ifb interfaces is being setup before "network.target", so they are instantly up and systemd-networkd-wait-online.service is instantly exits with success. Maintainer should change .service file so that it includes this lines:

Wants=network-online.target
After=network-online.target

Instead of this:

Wants=network.target
Before=network.target

As a workaround. Possibly systemd-networkd bug. This is systemd-networkd log before the change:

фев 17 08:33:22 SlenderServer systemd[1]: Starting Network Service...
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: ifb4enp3s0: Gained IPv6LL
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: Enumeration completed
фев 17 08:33:22 SlenderServer systemd[1]: Started Network Service.
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: enp3s0: Interface name change detected, enp3s0 has been renamed to eth0.
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: eno1: Interface name change detected, eno1 has been renamed to eth1.
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: eth0: Interface name change detected, eth0 has been renamed to enp3s0.
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: eth1: Interface name change detected, eth1 has been renamed to eno1.
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: SQM_IFB_27454: Could not find device, waiting for device initialization: No such device
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: SQM_IFB_49d74: Could not find device, waiting for device initialization: No such device
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: ifb4enp3s0: Link DOWN
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: ifb4enp3s0: Lost carrier
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: SQM_IFB_5e5d1: Could not find device, waiting for device initialization: No such device
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: ifb4enp3s0: Link UP
фев 17 08:33:22 SlenderServer systemd-networkd[1330]: ifb4enp3s0: Gained carrier
фев 17 08:33:23 SlenderServer systemd-networkd[1330]: enp3s0: Link UP
фев 17 08:33:23 SlenderServer systemd-networkd[1330]: eno1: Link UP
фев 17 08:33:24 SlenderServer systemd-networkd[1330]: enp3s0: Gained carrier
фев 17 08:33:26 SlenderServer systemd-networkd[1330]: enp3s0: Gained IPv6LL
фев 17 08:33:27 SlenderServer systemd-networkd[1330]: eno1: Gained carrier
фев 17 08:33:28 SlenderServer systemd-networkd[1330]: tun0: Link UP
фев 17 08:33:28 SlenderServer systemd-networkd[1330]: tun0: Gained carrier
фев 17 08:33:28 SlenderServer systemd-networkd[1330]: tun0: Gained IPv6LL
фев 17 08:33:29 SlenderServer systemd-networkd[1330]: eno1: Gained IPv6LL
фев 17 08:35:30 SlenderServer systemd-networkd[1330]: tun0: Link DOWN
фев 17 08:35:30 SlenderServer systemd-networkd[1330]: tun0: Lost carrier
фев 17 08:35:30 SlenderServer systemd-networkd[1330]: ifb4enp3s0: Link DOWN
фев 17 08:35:30 SlenderServer systemd-networkd[1330]: ifb4enp3s0: Lost carrier

And systemd-networkd-wait-online.service log:

фев 17 08:33:22 SlenderServer systemd[1]: Starting Wait for Network to be Configured...
фев 17 08:33:22 SlenderServer systemd[1]: Finished Wait for Network to be Configured.
фев 17 08:35:31 SlenderServer systemd[1]: systemd-networkd-wait-online.service: Succeeded.
фев 17 08:35:31 SlenderServer systemd[1]: Stopped Wait for Network to be Configured.

And this is after the change. systemd-networkd.service:

фев 17 08:35:55 SlenderServer systemd[1]: Starting Network Service...
фев 17 08:35:55 SlenderServer systemd-networkd[1223]: Enumeration completed
фев 17 08:35:55 SlenderServer systemd[1]: Started Network Service.
фев 17 08:35:55 SlenderServer systemd-networkd[1223]: enp3s0: Interface name change detected, enp3s0 has been renamed to eth0.
фев 17 08:35:55 SlenderServer systemd-networkd[1223]: eno1: Interface name change detected, eno1 has been renamed to eth1.
фев 17 08:35:55 SlenderServer systemd-networkd[1223]: eth0: Interface name change detected, eth0 has been renamed to enp3s0.
фев 17 08:35:55 SlenderServer systemd-networkd[1223]: eth1: Interface name change detected, eth1 has been renamed to eno1.
фев 17 08:35:56 SlenderServer systemd-networkd[1223]: enp3s0: Link UP
фев 17 08:35:56 SlenderServer systemd-networkd[1223]: eno1: Link UP
фев 17 08:35:57 SlenderServer systemd-networkd[1223]: enp3s0: Gained carrier
фев 17 08:35:59 SlenderServer systemd-networkd[1223]: enp3s0: Gained IPv6LL
фев 17 08:36:01 SlenderServer systemd-networkd[1223]: eno1: Gained carrier
фев 17 08:36:02 SlenderServer systemd-networkd[1223]: eno1: Gained IPv6LL
фев 17 08:36:11 SlenderServer systemd-networkd[1223]: ifb4enp3s0: Link UP
фев 17 08:36:11 SlenderServer systemd-networkd[1223]: ifb4enp3s0: Gained carrier
фев 17 08:36:11 SlenderServer systemd-networkd[1223]: ifb4enp3s0: Gained IPv6LL
фев 17 08:36:12 SlenderServer systemd-networkd[1223]: tun0: Link UP
фев 17 08:36:12 SlenderServer systemd-networkd[1223]: tun0: Gained carrier
фев 17 08:36:12 SlenderServer systemd-networkd[1223]: tun0: Gained IPv6LL

systemd-networkd-wait-online.service:

фев 17 08:35:55 SlenderServer systemd[1]: Starting Wait for Network to be Configured...
фев 17 08:36:11 SlenderServer systemd[1]: Finished Wait for Network to be Configured.

jconger commented on 2020-06-01 11:50

I had to look up the meaning of the @ in the unit file name. The systemd unit can have multiple instances because the unit file is named sqm@.service so you don't run "systemd status sqm@.service", you run a named instance like "systemd status sqm@default.service".

I believe the correct thing to do is to copy /etc/sqm/default.conf to /etc/sqm/IFACE.conf and configure it for your up, down, etc. You start with systemctl start sqm@IFACE.

longspear commented on 2020-04-04 13:10

anyone know how to get the systemd file to work properly? been struggling to enable it