Trochę się nie odzywałem, no i problemy inne się pojawiły w międzyczasie...
Od niedawna używam najnowszego Gargoyle - zmiany wizualne na duży plus. Stabilność jak na razie bez zarzutu, choć to dopiero kilka dni (odpukać.....
.
Do rzeczy: zmieniłem sieć z Plusa na nju mobile i zauważyłem że modem zmienia dość często rodzaj połączenia pomiędzy LTE a DCHSPA+. Więc picocomem wydałem mu polecenie: at^syscfgex="03",3fffffff,2,4,7fffffffffffffff,, żeby łączył się tylko z LTE. I tu pojawił się mały klops: od tej pory żeby modem się połączył trzeba użyć polecenia ifup wan - nic innego nie pomaga, ani restart routera ani wyłączenie i włączenie zasilania? Co się stało? Jak to naprawić?
Logi ze startującego połączenia wyglądają tak:
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan' is setting up now
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan (4456): Waiting for network registration
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan (4456): Starting network internet
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan (4456): Starting DHCP
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan' is now up
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Network device 'wwan0' link is up
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan (4456): Command failed: Unknown error
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan_6' is enabled
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan_6' has link connectivity
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan_6' is setting up now
Thu Mar 9 22:32:51 2017 daemon.notice netifd: Interface 'wan_6' is now up
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan (4456): Command failed: Unknown error
Thu Mar 9 22:32:51 2017 user.notice root: qmi bringup failed, retry in 15s
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan_4 (4502): udhcpc (v1.23.2) started
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan_4 (4502): Sending discover...
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan_4 (4502): Sending select for 10.70.135.127...
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan_4 (4502): Lease of 10.70.135.127 obtained, lease time 7200
Thu Mar 9 22:32:51 2017 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Mar 9 22:32:52 2017 daemon.notice netifd: Interface 'wan_4' is now up
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: reading /tmp/resolv.conf.auto
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain micro
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain micro
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain micro
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain oss
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain oss
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain oss
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain null
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain null
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain null
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain ing
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain ing
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain ing
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain indy
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain indy
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain indy
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain gopher
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain gopher
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain gopher
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain geek
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain geek
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain geek
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain fur
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain fur
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain fur
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain free
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain free
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain free
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain bbs
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain bbs
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain bbs
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain dyn
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain dyn
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain dyn
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain parody
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain parody
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain parody
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.142.171.235#53 for domain glue
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 95.211.32.162#53 for domain glue
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 66.244.95.20#53 for domain glue
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 176.58.118.172#53 for domain bit
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 106.187.47.17#53 for domain bit
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 178.32.31.41#53 for domain bit
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using local addresses only for domain lan
Thu Mar 9 22:32:52 2017 daemon.warn dnsmasq[2640]: ignoring nameserver 10.10.10.10 - local interface
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 194.204.159.1#53
Thu Mar 9 22:32:52 2017 daemon.info dnsmasq[2640]: using nameserver 194.204.152.34#53
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Thu Mar 9 22:32:56 2017 authpriv.info dropbear[4359]: Exit (root): Exited normally
Thu Mar 9 22:32:57 2017 kern.warn kernel: [ 357.070000] ipt_bandwidth: timezone shift of 60 minutes detected, adjusting
Thu Mar 9 22:32:57 2017 kern.warn kernel: [ 357.080000] old minutes west=0, new minutes west=-60
Czy w nich jest wszystko ok? Chodzi mi o to:
Thu Mar 9 22:32:51 2017 daemon.notice netifd: wan (4456): Command failed: Unknown error
Thu Mar 9 22:32:51 2017 user.notice root: qmi bringup failed, retry in 15s
i o to:
Thu Mar 9 22:32:52 2017 daemon.notice netifd: wan_4 (4502): /sbin/uci: Invalid argument
Dodatkowo: o co chodzi z tym wan_4? to na bank jest związane z modemem, bo po połączeniu równo co co godzinę pojawiają się takie logi w ilości około 10 szt. poprzedzone informacją o odnowieniu nadanego adresu IP przez operatora. Dlaczego to się nazywa wan_4, a nie wan, albo wwan0 i skąd te błędy? Czy to musi się co godzinę pojawiać?
Sorry jeśli to lamerskie pytania, ale ciekawość mnie zżera i spokoju nie daje 
Xiaomi Mi Router 3G + Huawei E3372s-153 HiLinkGargoyle 1.11.0.0 (0e0ff65f) by obsymój speedtest.pl