[RESOLU] HELP! Multiples erreurs logs et tunnel se coupe aléatoirement (mais de plus en

Bonjour,
depuis quelques temps (une à deux semaines je dirais) j'ai des erreurs multiples dans les logs (entre autres : "socket not connected", "connection timed out", "mptcp_verif_dss_csum csum is wrong...") qui reviennent régulièrement ainsi que des problèmes de connections aléatoire (apparemment le tunnel se coupe à ce moment là) et d’accès à certains sites de manière aléatoire... Je précise que j'ai une connection orange adsl pas rapide du tout (avec QOS) mais avec un ping correct (24ms) ainsi que 2 routeurs 4G illimités très rapides : Bouygues 4G box sans QOS car assez stable niveau débits et avec ping moyen de 55/60ms et Routeur 4G Free avec QOS car bien moins stable niveaux débits et ping 45/55ms; J'ai essayé (faute d'autre idées) d'intervertir les wan 12/13/14 (qui correspondent actuellement respectivement à Bouygues-4G/Orange-ADSL/Free-4G) dans différents ordres: sans résultats... De même j'ai réinitialisé plusieurs fois l'overthebox (une fois simple reset et 2 fois réinstallation avec le dernier firmware: sans résultat) et enfin j'ai essayé de mettre mes routeurs en dhcp au lieu d'ip fixe actuellement, mais j'avais encore plus de problèmes: la livebox n'était plus détecté après quelques temps (il fallait que je la redémarre) et j'avais des déconnections aléatoires (d'après le log de l'overthebox) de bouygues qui ne correspondait pourtant pas à la durée dhcp du routeur 4GBox (???)...
Bref je ne sais plus quoi faire car parfois cela fonctionne très bien et par moment j'ai que des problèmes donc toute aide serait la bienvenue (changement de docker???).
En espérant de l'aide, merci par avance!!!
Cordialement.

Mes infos overthebox:
Device ID: e46ea2a5-055f-418c-8c78-1eb2b17b0c09
Service name: overthebox.50bdd73e-3bcc-4a1c-bd35-2ad1118cb177

Une copie du log récent où à peu prés toutes les erreurs cités ci dessus sont présentes:

Fri Feb 22 05:27:01 2019 user.notice otb-qos: checking QoS
Fri Feb 22 05:27:03 2019 daemon.info logread[19265]: Logread connected to 167.114.241.173:22837
Fri Feb 22 05:27:04 2019 daemon.info ss-redir-track: Shadowsocks is up
Fri Feb 22 05:27:04 2019 user.info ss-redir-initd: Plugging shadowsocks cable in...
Fri Feb 22 05:27:06 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:06 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:06 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:06 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:06 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:06 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:06 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:06 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:08 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:08 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:09 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:09 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:10 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:10 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:10 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:10 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:10 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:10 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:10 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:10 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:10 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:10 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:10 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:10 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:11 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:11 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:11 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:11 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:12 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:12 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:12 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:12 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:13 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:13 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:14 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:14 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:14 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:14 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:14 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:14 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:14 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:14 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:14 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:14 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:14 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:14 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:14 2019 daemon.info ss-redir-track: Shadowsocks is down
Fri Feb 22 05:27:14 2019 user.info ss-redir-initd: Unplugging shadowsocks cable...
Fri Feb 22 05:27:15 2019 daemon.err glorytun[2954]: read: Operation timed out
Fri Feb 22 05:27:15 2019 daemon.info glorytun[2954]: STOPPED tun0
Fri Feb 22 05:27:24 2019 daemon.err ss-redir[4025]: 2019-02-22 05:27:24 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:25 2019 daemon.err otb-daemon[3699]: curl: (28) Connection timed out after 5001 milliseconds
Fri Feb 22 05:27:31 2019 daemon.err otb-daemon[3699]: curl: (28) Connection timed out after 5001 milliseconds
Fri Feb 22 05:27:35 2019 daemon.err ss-redir[4024]: 2019-02-22 05:27:35 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:37 2019 daemon.err otb-daemon[3699]: curl: (28) Connection timed out after 5001 milliseconds
Fri Feb 22 05:27:44 2019 daemon.err otb-daemon[3699]: curl: (28) Connection timed out after 5001 milliseconds
Fri Feb 22 05:27:45 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:45 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:48 2019 daemon.err glorytun[2954]: 151.127.13.5.5006: connected
Fri Feb 22 05:27:48 2019 daemon.info glorytun[2954]: STARTED tun0
Fri Feb 22 05:27:55 2019 daemon.err ss-redir[4027]: 2019-02-22 05:27:55 ERROR: getpeername: Socket not connected
Fri Feb 22 05:27:58 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:58 ERROR: remote recv: Operation timed out
Fri Feb 22 05:27:59 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:59 ERROR: remote recv: Operation timed out
Fri Feb 22 05:27:59 2019 daemon.err glorytun[2954]: read: Operation timed out
Fri Feb 22 05:27:59 2019 daemon.info glorytun[2954]: STOPPED tun0
Fri Feb 22 05:27:59 2019 daemon.err ss-redir[4026]: 2019-02-22 05:27:59 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:03 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:03 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:03 2019 daemon.err ss-redir[4027]: 2019-02-22 05:28:03 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:05 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:05 ERROR: getpeername: Socket not connected
Fri Feb 22 05:28:05 2019 daemon.err ss-redir[4024]: 2019-02-22 05:28:05 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:07 2019 daemon.err ss-redir[4027]: 2019-02-22 05:28:07 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:07 2019 daemon.err graph[18923]: curl: (28) Connection timed out after 10001 milliseconds
Fri Feb 22 05:28:08 2019 daemon.err ss-redir[4024]: 2019-02-22 05:28:08 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:08 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:08 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:08 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:08 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:13 2019 daemon.err ss-redir[4027]: 2019-02-22 05:28:13 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:14 2019 daemon.err ss-redir[4025]: 2019-02-22 05:28:14 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:15 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:15 ERROR: getpeername: Socket not connected
Fri Feb 22 05:28:16 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:16 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:17 2019 daemon.err ss-redir[4027]: 2019-02-22 05:28:17 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:19 2019 daemon.err ss-redir[4025]: 2019-02-22 05:28:19 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:20 2019 daemon.err ss-redir[4025]: 2019-02-22 05:28:20 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:20 2019 daemon.err ss-redir[4024]: 2019-02-22 05:28:20 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:21 2019 daemon.err ss-redir[4025]: 2019-02-22 05:28:21 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:22 2019 daemon.err ss-redir[4024]: 2019-02-22 05:28:22 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:22 2019 daemon.err graph[23491]: curl: (28) Connection timed out after 10002 milliseconds
Fri Feb 22 05:28:25 2019 daemon.err otb-daemon[3699]: curl: (28) Connection timed out after 5001 milliseconds
Fri Feb 22 05:28:25 2019 daemon.err ss-redir[4025]: 2019-02-22 05:28:25 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:25 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:25 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:25 2019 daemon.err ss-redir[4025]: 2019-02-22 05:28:25 ERROR: getpeername: Socket not connected
Fri Feb 22 05:28:30 2019 daemon.err ss-redir[4027]: 2019-02-22 05:28:30 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:31 2019 daemon.err otb-daemon[3699]: curl: (28) Connection timed out after 5001 milliseconds
Fri Feb 22 05:28:35 2019 daemon.err ss-redir[4025]: 2019-02-22 05:28:35 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:35 2019 daemon.err ss-redir[4024]: 2019-02-22 05:28:35 ERROR: remote recv: Operation timed out
Fri Feb 22 05:28:35 2019 daemon.err ss-redir[4026]: 2019-02-22 05:28:35 ERROR: getpeername: Socket not connected
Fri Feb 22 05:28:37 2019 daemon.err graph[24456]: curl: (28) Connection timed out after 10002 milliseconds
Fri Feb 22 05:28:38 2019 daemon.err otb-daemon[3699]: curl: (28) Connection timed out after 5001 milliseconds
Fri Feb 22 05:28:38 2019 daemon.err glorytun[2954]: 151.127.13.5.5006: connected
Fri Feb 22 05:28:38 2019 daemon.info glorytun[2954]: STARTED tun0
Fri Feb 22 05:28:43 2019 user.notice post-tracking-otb-autoroute: add rule matching 0x7874756e using table 101 and pref 30000
Fri Feb 22 05:28:43 2019 user.notice post-tracking-store-state: xtun0 tracking status changed to OK
Fri Feb 22 05:28:45 2019 daemon.info ss-redir-track: Shadowsocks is up
Fri Feb 22 05:28:45 2019 user.info ss-redir-initd: Plugging shadowsocks cable in...
Fri Feb 22 05:29:27 2019 daemon.err ss-redir[4024]: 2019-02-22 05:29:27 ERROR: remote recv: Operation timed out
Fri Feb 22 05:31:40 2019 daemon.err ss-redir[4024]: 2019-02-22 05:31:40 ERROR: remote recv: Operation timed out
Fri Feb 22 05:31:40 2019 daemon.err ss-redir[4027]: 2019-02-22 05:31:40 ERROR: remote recv: Operation timed out
Fri Feb 22 05:34:44 2019 daemon.err ss-redir[4025]: 2019-02-22 05:34:44 ERROR: remote recv: Operation timed out
Fri Feb 22 05:34:44 2019 daemon.err ss-redir[4024]: 2019-02-22 05:34:44 ERROR: remote recv: Operation timed out
Fri Feb 22 05:34:59 2019 daemon.err ss-redir[4024]: 2019-02-22 05:34:59 ERROR: remote recv: Operation timed out
Fri Feb 22 05:35:40 2019 daemon.err ss-redir[4024]: 2019-02-22 05:35:40 ERROR: remote recv: Operation timed out
Fri Feb 22 05:35:45 2019 daemon.err ss-redir[4027]: 2019-02-22 05:35:45 ERROR: remote recv: Operation timed out
Fri Feb 22 05:36:01 2019 daemon.err ss-redir[4024]: 2019-02-22 05:36:01 ERROR: remote recv: Operation timed out
Fri Feb 22 05:39:15 2019 daemon.err ss-redir[4027]: 2019-02-22 05:39:15 ERROR: remote recv: Operation timed out
Fri Feb 22 05:41:38 2019 kern.err kernel: [39534.311040] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 369064763 dss_csum_added 1 overflowed 1 iterations 1
Fri Feb 22 05:41:40 2019 kern.err kernel: [39535.535209] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 2566079346 dss_csum_added 1 overflowed 1 iterations 1
Fri Feb 22 05:41:43 2019 kern.err kernel: [39538.784955] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 2581916414 dss_csum_added 1 overflowed 1 iterations 1
Fri Feb 22 05:45:00 2019 kern.err kernel: [39736.356321] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 3053365688 dss_csum_added 1 overflowed 0 iterations 1
Fri Feb 22 05:45:00 2019 kern.err kernel: [39736.374588] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 3882931103 dss_csum_added 1 overflowed 0 iterations 1
Fri Feb 22 05:45:00 2019 kern.err kernel: [39736.448106] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 3446431230 dss_csum_added 1 overflowed 0 iterations 1
Fri Feb 22 06:35:05 2019 daemon.err otb-tracker[3570]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Feb 22 06:45:30 2019 user.notice post-tracking-mptcp: eth0.5 switched off
Fri Feb 22 06:45:30 2019 user.notice post-tracking-otb-autoroute: del default route for eth0.5 using gateway 192.168.2.1 and metric 14
Fri Feb 22 06:45:30 2019 user.notice post-tracking-otb-autoroute: del 151.127.13.5 route for eth0.5 using gateway 192.168.2.1 and metric 14
Fri Feb 22 06:45:30 2019 user.notice post-tracking-otb-autoroute: del 192.168.2.1 route for eth0.5 using gateway 192.168.2.1 and metric 14
Fri Feb 22 06:45:30 2019 user.notice post-tracking-store-state: wan14 tracking status changed to ERROR
Fri Feb 22 06:45:33 2019 user.notice post-tracking-mptcp: eth0.5 switched to on
Fri Feb 22 06:45:33 2019 user.notice post-tracking-otb-autoroute: add default route for eth0.5 using gateway 192.168.2.1 and metric 14
Fri Feb 22 06:45:33 2019 user.notice post-tracking-otb-autoroute: add 151.127.13.5 route for eth0.5 using gateway 192.168.2.1 and metric 14
Fri Feb 22 06:45:33 2019 user.notice post-tracking-otb-autoroute: add 192.168.2.1 route for eth0.5 using gateway 192.168.2.1 and metric 14
Fri Feb 22 06:45:33 2019 user.notice post-tracking-store-state: wan14 tracking status changed to OK
Fri Feb 22 07:36:18 2019 daemon.err ss-redir[4024]: 2019-02-22 07:36:18 ERROR: send: Broken pipe
Fri Feb 22 07:37:27 2019 daemon.info glorytun-udp: starting glorytun-udp instance xtun0
Fri Feb 22 07:37:27 2019 user.info ss-redir-initd: Starting service...
Fri Feb 22 07:37:28 2019 user.notice otb-qos: stopping QoS
Fri Feb 22 07:37:29 2019 user.notice otb-qos: starting QoS
Fri Feb 22 07:37:29 2019 user.notice otb-qos: setting upload QoS on eth0.4 [wan13] to 800kbps
Fri Feb 22 07:37:29 2019 user.notice otb-qos: QoS is not present, setting it up on eth0.4
Fri Feb 22 07:37:29 2019 user.notice otb-qos: sending download QoS on eth0.4 [wan13] - maximum download 9000kbps
Fri Feb 22 07:37:29 2019 daemon.info glorytun: starting glorytun instance tun0
Fri Feb 22 07:37:30 2019 user.info swconfig: Gathering VLAN facts...
Fri Feb 22 07:37:30 2019 user.info swconfig: Configuring if range 15
Fri Feb 22 07:37:30 2019 user.info swconfig: Setting mode into trunk mode
Fri Feb 22 07:37:30 2019 user.info swconfig: Setting native VID to 1
Fri Feb 22 07:37:30 2019 user.info swconfig: Adding new VIDs 1
Fri Feb 22 07:37:36 2019 user.info ss-redir-initd: Plugging shadowsocks cable in...
Fri Feb 22 07:38:01 2019 daemon.info glorytun: starting glorytun instance tun0
Fri Feb 22 07:38:01 2019 user.notice otb-qos: stopping QoS
Fri Feb 22 07:38:01 2019 user.notice otb-qos: upload QoS deleted on eth0.4 [wan13]
Fri Feb 22 07:38:01 2019 user.notice otb-qos: starting QoS
Fri Feb 22 07:38:01 2019 user.notice otb-qos: setting upload QoS on eth0.4 [wan13] to 800kbps
Fri Feb 22 07:38:01 2019 user.notice otb-qos: QoS is not present, setting it up on eth0.4
Fri Feb 22 07:38:01 2019 user.notice otb-qos: sending download QoS on eth0.4 [wan13] - maximum download 9000kbps
Fri Feb 22 07:38:01 2019 user.notice otb-qos: setting upload QoS on eth0.5 [wan14] to 20000kbps
Fri Feb 22 07:38:01 2019 user.notice otb-qos: QoS is not present, setting it up on eth0.5
Fri Feb 22 07:38:01 2019 user.notice otb-qos: sending download QoS on eth0.5 [wan14] - maximum download 92000kbps
Fri Feb 22 07:38:01 2019 user.info ss-redir-initd: Starting service...
Fri Feb 22 07:38:02 2019 daemon.info glorytun-udp: starting glorytun-udp instance xtun0
Fri Feb 22 07:38:03 2019 user.info swconfig: Gathering VLAN facts...
Fri Feb 22 07:38:03 2019 user.info swconfig: Configuring if range 15
Fri Feb 22 07:38:04 2019 user.info swconfig: Setting mode into trunk mode
Fri Feb 22 07:38:04 2019 user.info swconfig: Setting native VID to 1
Fri Feb 22 07:38:04 2019 user.info swconfig: Adding new VIDs 1
Fri Feb 22 07:38:06 2019 user.info ss-redir-initd: Plugging shadowsocks cable in...
Fri Feb 22 07:38:19 2019 daemon.err ss-redir[4026]: 2019-02-22 07:38:19 ERROR: send: Broken pipe
Fri Feb 22 07:38:29 2019 daemon.err ss-redir[4025]: 2019-02-22 07:38:29 ERROR: getpeername: Socket not connected
Fri Feb 22 07:40:08 2019 user.notice otb-qos: QoS has changed on eth0.5 need to restart
Fri Feb 22 07:40:08 2019 user.notice otb-qos: restarting QoS
Fri Feb 22 07:40:08 2019 user.notice otb-qos: stopping QoS
Fri Feb 22 07:40:09 2019 user.notice otb-qos: upload QoS deleted on eth0.4 [wan13]
Fri Feb 22 07:40:09 2019 user.notice otb-qos: upload QoS deleted on eth0.5 [wan14]
Fri Feb 22 07:40:09 2019 user.notice otb-qos: starting QoS
Fri Feb 22 07:40:09 2019 user.notice otb-qos: setting upload QoS on eth0.4 [wan13] to 800kbps
Fri Feb 22 07:40:09 2019 user.notice otb-qos: QoS is not present, setting it up on eth0.4
Fri Feb 22 07:40:09 2019 user.notice otb-qos: sending download QoS on eth0.4 [wan13] - maximum download 9000kbps
Fri Feb 22 07:40:09 2019 user.notice otb-qos: setting upload QoS on eth0.5 [wan14] to 20000kbps
Fri Feb 22 07:40:09 2019 user.notice otb-qos: QoS is not present, setting it up on eth0.5
Fri Feb 22 07:40:09 2019 user.notice otb-qos: sending download QoS on eth0.5 [wan14] - maximum download 92000kbps