działa po dodaniu opóźnienia. ciekawi mnie skąd tak jest, że modem jeden wstaje dłużej drugi krócej. może jest to kwestia najnowszego firmware? wgrałem A13-tkę, może to od tego? -_^;

tak czy siak, dziękuję, może faktycznie nie ma co rozkminiać. dobrego!

a może tu coś mam nie tak?

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'jakiśtamadresipv6::/48'
        option packet_steering '2'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option delegate '0'

config interface 'wan'
        option device '/dev/cdc-wdm0'
        option proto 'qmi'
        option pdptype 'ipv4'
        option apn 'internet'
        option auth 'pap'
        option username 'internet'
        option password 'internet'
        option sourcefilter '0'
        option delegate '0'

config device
        option name 'wwan0'
        option ipv6 '0'

dostawca nju mobile

po reboocie...

Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.878986] option 2-1:1.0: GSM modem (1-port) converter detected
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.879390] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.884938] option 2-1:1.1: GSM modem (1-port) converter detected
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.891545] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.897988] option 2-1:1.2: GSM modem (1-port) converter detected
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.904487] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.910540] option 2-1:1.3: GSM modem (1-port) converter detected
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.917119] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
Fri Jan 30 19:34:43 2026 daemon.info dropbear: Using network interface 'lan' (network device 'br-lan') for direct binding
Fri Jan 30 19:34:43 2026 kern.info kernel: [   34.971563] qmi_wwan 2-1:1.4: cdc-wdm0: USB WDM device
Fri Jan 30 19:34:43 2026 user.notice ucitrack: Setting up non-init /etc/config/fstab reload handler: /sbin/block mount
Fri Jan 30 19:34:43 2026 user.notice ucitrack: Setting up /etc/config/system reload trigger for non-procd /etc/init.d/led
Fri Jan 30 19:34:44 2026 user.notice ucitrack: Setting up /etc/config/luci_statistics reload dependency on /etc/config/system
Fri Jan 30 19:34:44 2026 user.info : Binding to interface 'br-lan'
Fri Jan 30 19:34:44 2026 authpriv.info dropbear[2469]: Not backgrounding
Fri Jan 30 19:34:44 2026 user.notice ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/system
Fri Jan 30 19:34:44 2026 daemon.notice netifd: Interface 'wan' is setting up now
Fri Jan 30 19:34:44 2026 daemon.notice netifd: wan (2601): ls: /sys/devices/platform/soc/8af8800.usb/8a00000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.4/net: No such file or directory
Fri Jan 30 19:34:44 2026 daemon.notice netifd: wan (2601): The interface could not be found.
Fri Jan 30 19:34:44 2026 daemon.notice netifd: wan (2655): Stopping network wan
Fri Jan 30 19:34:44 2026 daemon.notice netifd: wan (2655): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Fri Jan 30 19:34:44 2026 daemon.notice netifd: Interface 'wan' is now down
Fri Jan 30 19:34:45 2026 user.info adblock-4.4.2-r4[1398]: adblock instance started ::: action: boot, priority: 0, pid: 1398
Fri Jan 30 19:34:45 2026 kern.warn kernel: [   37.067472] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Fri Jan 30 19:34:45 2026 kern.warn kernel: [   37.067546] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
Fri Jan 30 19:34:45 2026 kern.info kernel: [   37.100846] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Fri Jan 30 19:34:45 2026 kern.info kernel: [   37.101762] ath10k_pci 0000:01:00.0: wmi print 'free: 114572 iram: 12644 sram: 29508'
Fri Jan 30 19:34:46 2026 kern.info kernel: [   37.432969] ath10k_pci 0000:01:00.0: rts threshold -1
Fri Jan 30 19:34:46 2026 kern.warn kernel: [   37.433880] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Fri Jan 30 19:34:46 2026 kern.info kernel: [   37.438829] qmi_wwan 2-1:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.0.auto-1, WWAN/QMI device, 8a:96:ed:71:ef:6e
Fri Jan 30 19:34:46 2026 kern.info kernel: [   37.443189] br-lan: port 3(phy0-ap0) entered blocking state

root@OpenWrt:~# ifstatus wan
{
        "up": false,
        "pending": false,
        "available": false,
        "autostart": true,
        "dynamic": false,
        "proto": "qmi",
        "data": {

        },
        "errors": [
                {
                        "subsystem": "interface",
                        "code": "NO_DEVICE"
                }
        ]
}

uqmi -d /dev/cdc-wdm0 --get-data-status
^C"Failed to connect to service"
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-data-status
"Failed to connect to service"

root@OpenWrt:~# /etc/init.d/modem_switch boot

i standardzik:

Fri Jan 30 19:42:37 2026 kern.info kernel: [  509.190872] usb 2-1: USB disconnect, device number 2
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.191452] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.195063] option 2-1:1.0: device disconnected
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.203284] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.207323] option 2-1:1.1: device disconnected
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.215935] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.219839] option 2-1:1.2: device disconnected
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.228295] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.232427] option 2-1:1.3: device disconnected
Fri Jan 30 19:42:38 2026 kern.info kernel: [  509.240543] qmi_wwan 2-1:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.0.auto-1, WWAN/QMI device
Fri Jan 30 19:42:48 2026 kern.info kernel: [  519.891235] usb 2-1: new SuperSpeed USB device number 3 using xhci-hcd
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.053352] option 2-1:1.0: GSM modem (1-port) converter detected
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.053740] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.059119] option 2-1:1.1: GSM modem (1-port) converter detected
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.065692] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.072106] option 2-1:1.2: GSM modem (1-port) converter detected
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.078485] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.084928] option 2-1:1.3: GSM modem (1-port) converter detected
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.091381] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.116927] qmi_wwan 2-1:1.4: cdc-wdm0: USB WDM device
Fri Jan 30 19:42:48 2026 kern.info kernel: [  520.118331] qmi_wwan 2-1:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.0.auto-1, WWAN/QMI device, 12:ff:7f:43:05:ea
Fri Jan 30 19:42:49 2026 daemon.notice netifd: Interface 'wan' is setting up now
Fri Jan 30 19:42:49 2026 daemon.notice netifd: wan (4270): Waiting for SIM initialization
Fri Jan 30 19:42:53 2026 daemon.notice netifd: wan (4270): Request timed out
Fri Jan 30 19:42:55 2026 daemon.notice netifd: wan (4270): Request timed out
Fri Jan 30 19:42:55 2026 daemon.notice netifd: wan (4270): Failed to parse message data
Fri Jan 30 19:42:55 2026 daemon.notice netifd: wan (4270): SIM in illegal state - Power-cycling SIM
Fri Jan 30 19:42:56 2026 daemon.notice netifd: wan (4270): Request timed out
Fri Jan 30 19:42:56 2026 daemon.notice netifd: wan (4270): "Failed to connect to service"
Fri Jan 30 19:43:00 2026 daemon.notice netifd: wan (4270): Request timed out
Fri Jan 30 19:43:00 2026 daemon.notice netifd: wan (4270): "Failed to connect to service"
root@OpenWrt:~# ifdown wan
root@OpenWrt:~# ifup wan

Fri Jan 30 19:43:38 2026 daemon.notice netifd: Interface 'wan' is now down
Fri Jan 30 19:43:39 2026 daemon.warn odhcpd[1461]: No default route present, setting ra_lifetime to 0!
Fri Jan 30 19:43:41 2026 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Fri Jan 30 19:43:41 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Fri Jan 30 19:43:41 2026 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 2 names
Fri Jan 30 19:43:41 2026 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Fri Jan 30 19:43:41 2026 daemon.notice netifd: Interface 'wan' is setting up now
Fri Jan 30 19:43:41 2026 daemon.notice netifd: wan (4644): Waiting for SIM initialization
Fri Jan 30 19:43:45 2026 daemon.notice netifd: wan (4644): Failed to parse message data
Fri Jan 30 19:43:45 2026 daemon.notice netifd: wan (4644): PIN verification is disabled
Fri Jan 30 19:43:46 2026 daemon.notice netifd: wan (4644): Device does not support 802.3 mode. Informing driver of raw-ip only for wwan0 ..
Fri Jan 30 19:43:46 2026 daemon.notice netifd: wan (4644): Waiting for network registration
Fri Jan 30 19:43:51 2026 daemon.notice netifd: wan (4644): Starting network wan
Fri Jan 30 19:43:52 2026 daemon.notice netifd: wan (4644): Setting up wwan0
Fri Jan 30 19:43:52 2026 daemon.notice netifd: Interface 'wan' is now up
Fri Jan 30 19:43:52 2026 daemon.notice netifd: Network device 'wwan0' link is up
Fri Jan 30 19:43:52 2026 daemon.notice netifd: Network alias 'wwan0' link is up
Fri Jan 30 19:43:52 2026 daemon.notice netifd: Interface 'wan_4' is enabled
Fri Jan 30 19:43:52 2026 daemon.notice netifd: Interface 'wan_4' has link connectivity
Fri Jan 30 19:43:52 2026 daemon.notice netifd: Interface 'wan_4' is setting up now
Fri Jan 30 19:43:52 2026 daemon.notice netifd: wan_4 (4753): udhcpc: started, v1.36.1
Fri Jan 30 19:43:52 2026 user.notice SQM: Starting SQM script: piece_of_cake.qos on wwan0, in: 62500 Kbps, out: 15500 Kbps
Fri Jan 30 19:43:52 2026 daemon.notice netifd: wan_4 (4753): udhcpc: broadcasting discover
Fri Jan 30 19:43:52 2026 daemon.notice netifd: wan_4 (4753): udhcpc: broadcasting select for 10.8.112.85, server 10.8.112.86
Fri Jan 30 19:43:53 2026 daemon.notice netifd: wan_4 (4753): udhcpc: lease of 10.8.112.85 obtained from 10.8.112.86, lease time 7200
Fri Jan 30 19:43:53 2026 daemon.notice netifd: Interface 'wan_4' is now up

także jednak trzeba zrobić ifdown najpierw żeby działało ^^

zahaszowałem wpisy 'case' w /etc/init.d/modem_switch ale nic to nie zmieniło;

może /etc/init.d/modem_switch w ogóle nie jest uruchamiany

service jest:

root@OpenWrt:~# service
/etc/init.d/modem_switch           enabled         stopped

także ani (chyba)

/etc/init.d/modem_switch shutdown

nie jest odpalane

ani

/etc/init.d/modem_switch boot

hmm może board_name jest inny i dlatego?

problem rozwiązany:

root@OpenWrt:~# cat /etc/rc.local
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.

sleep 30
ifdown wan
ifup wan

xD

Error: Unknown error (SIM_ILLEGAL_STATE)

trzeba dać restart interface wan przez LuCi i wówczas wstaje normalnie i tworzy się podinterfejs wan_4 z adresem IPv4 po DHCP

jakie logi mogę sprawdzić jeszcze żeby to zweryfikować? może mogę usunąć jakieś ustawienia i ustawić na nowo? konfigurowałem z palca przez ssh, później zaktualizowałem pakiety przez opkg te które były dostępne i doinstalowałem do luci wsparcie dla qmi żebym mógł podglądać i ew zmieniać ustawienia przez LuCi

openwrt 24.10.5

druga sprawa to bardzo słaba wydajność wifi w porównaniu do oficjalnego firmware'u, duże pingi itp - zarówno na 5GHz jak i w paśmie 2,4GHz.

ale to może następnie, jak uda się rozgryźć ten modem

a takie info z sysloga:

Thu Jan 29 23:50:02 2026 daemon.notice netifd: wan (2601): Waiting for SIM initialization
Thu Jan 29 23:50:08 2026 daemon.notice netifd: wan (2601): Request timed out
Thu Jan 29 23:50:08 2026 daemon.notice netifd: wan (2601): Failed to parse message data
Thu Jan 29 23:50:08 2026 daemon.notice netifd: wan (2601): SIM in illegal state - Power-cycling SIM
Thu Jan 29 23:50:09 2026 daemon.notice netifd: wan (2601): Request timed out
Thu Jan 29 23:50:09 2026 daemon.notice netifd: wan (2601): "Failed to connect to service"
Thu Jan 29 23:50:13 2026 daemon.notice netifd: wan (2601): Request timed out
Thu Jan 29 23:50:13 2026 daemon.notice netifd: wan (2601): "Failed to connect to service"
Thu Jan 29 23:50:18 2026 daemon.notice netifd: wan (2601): Failed to parse message data
Thu Jan 29 23:50:18 2026 daemon.notice netifd: wan (2601): SIM in illegal state - Power-cycling SIM
Thu Jan 29 23:50:19 2026 daemon.notice netifd: wan (2601): "Unknown error"
Thu Jan 29 23:50:27 2026 daemon.notice netifd: wan (2601): Failed to parse message data
Thu Jan 29 23:50:27 2026 daemon.notice netifd: wan (2601): SIM in illegal state - Power-cycling SIM
Thu Jan 29 23:50:36 2026 daemon.notice netifd: wan (2601): Failed to parse message data
Thu Jan 29 23:50:36 2026 daemon.notice netifd: wan (2601): SIM in illegal state - Power-cycling SIM
Thu Jan 29 23:50:44 2026 daemon.notice netifd: wan (2601): SIM in illegal state - Power-cycling SIM

(..) - restart z palca:

Thu Jan 29 23:51:36 2026 daemon.notice netifd: wan (2601): SIM in illegal state - Power-cycling SIM
Thu Jan 29 23:51:39 2026 daemon.notice netifd: wan (6132): Stopping network wan
Thu Jan 29 23:51:39 2026 daemon.notice netifd: wan (6132): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Thu Jan 29 23:51:39 2026 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 29 23:52:32 2026 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 29 23:52:33 2026 daemon.notice netifd: wan (7781): Waiting for SIM initialization
Thu Jan 29 23:52:34 2026 daemon.notice netifd: wan (7781): Failed to parse message data
Thu Jan 29 23:52:34 2026 daemon.notice netifd: wan (7781): PIN verification is disabled
Thu Jan 29 23:52:35 2026 daemon.notice netifd: wan (7781): Device does not support 802.3 mode. Informing driver of raw-ip only for wwan0 ..
Thu Jan 29 23:52:35 2026 daemon.notice netifd: wan (7781): Waiting for network registration
Thu Jan 29 23:52:40 2026 daemon.notice netifd: wan (7781): Starting network wan
Thu Jan 29 23:52:41 2026 daemon.notice netifd: wan (7781): Setting up wwan0
Thu Jan 29 23:52:41 2026 daemon.notice netifd: Interface 'wan' is now up
Thu Jan 29 23:52:41 2026 daemon.notice netifd: Network device 'wwan0' link is up
Thu Jan 29 23:52:41 2026 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Jan 29 23:52:41 2026 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Jan 29 23:52:41 2026 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Jan 29 23:52:41 2026 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Jan 29 23:52:41 2026 daemon.notice netifd: wan_4 (7876): udhcpc: started, v1.36.1
Thu Jan 29 23:52:41 2026 user.notice SQM: Starting SQM script: piece_of_cake.qos on wwan0, in: 50000 Kbps, out: 20000 Kbps
Thu Jan 29 23:52:41 2026 daemon.notice netifd: wan_4 (7876): udhcpc: broadcasting discover
Thu Jan 29 23:52:42 2026 daemon.notice netifd: wan_4 (7876): udhcpc: broadcasting select for 10.6.98.87, server 10.6.98.88
Thu Jan 29 23:52:42 2026 daemon.notice netifd: wan_4 (7876): udhcpc: lease of 10.6.98.87 obtained from 10.6.98.88, lease time 7200
Thu Jan 29 23:52:42 2026 daemon.notice netifd: Interface 'wan_4' is now up

dalej wszystko ok, tylko trzeba było zresetować.

https://openwrt.org/toh/netgear/lbr20#i … mbs_speeds tu widzę że jest napisane że modem ma podłączone tylko dwie anteny i z tego tytułu nie ma pełnej agregacji;

to by się zgadzało też z obrazkiem, który wrzucił MIG, jeśli dobrze go rozumiem - przy modemie widzę tylko podpięte dwie anteny (FJ3 i FJ5 wypięte).

czy rozkręcając router i podpinając anteny LTE pod gniazda FJ3 i FJ5 uda się zwiększyć możliwości routera pod kątem agregacji, wykorzystując w pełni możliwości modemu?

czy ktoś z Was próbował?

dodatkowo zapytam, jakie firmware modemu używaliście i jak z instalacją - na stronie routera w WiKi OpenWRT widzę że możliwe jest zaktualizowanie firmware modemu przez qfirehose z forum Quectel'a - czy ktoś z Was to już robił i jakie wyniki? które firmware polecacie (do współpracy z najnowszym OpenWRT)?

znalazłem taki router za 350zł na allegro - póki co wydaje się najsolidniejszy - cena poniżej 500zł, agregacja 4 pasm (przynajmniej w teorii, a być może w praktyce - po ew podpięciu wyjść antenowych FJ3 i FJ5) no i bardzo proste wgrywanie OpenWRT.

czytałem że lubi się resetować jeśli nie jest po QMI - a jak po QMI? czy ktoś miał z nim złe doświadczenia?

proszę o info apropos tego routera, dziękuję!

ten router to faktycznie jakieś badziewie - czy może mój jest uszkodzony?

dziś się po prostu zawiesił - tj nie szło połączyć z netem.

takie logi:

Jan  4 16:32:06 (none) kern.err goahead[756]: zte_web_util.c, 1814 zte_goform_set_cmd_process -> goformId:[LOGIN].
Jan  4 16:32:06 (none) kern.err goahead[756]: zte_web_util.c, 1868 zte_goform_whitelist_check: zte_goform_id is OK.
Jan  4 16:32:06 (none) kern.err goahead[756]: zte_web_mgmt.c, 370 zte_mgmt_login: ip_address is 192.168.0.22
Jan  4 16:32:08 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:13 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:18 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:18 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:32:23 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:28 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:30 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:32:33 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:33 (none) kern.err DM-FOTA[2015]: platform/dmc_print.c, 380, #####current time is 1767544353,expected polling time is 1768894860
Jan  4 16:32:33 (none) kern.warn DM-FOTA[2015]: platform/dmc_print.c, 380, OMA_DM_POLLING_NOT_PASSED
Jan  4 16:32:33 (none) kern.warn DM-FOTA[2015]: platform/dmc_print.c, 380, OMA_DM_POLLING_SLEEP 60 about seconds
Jan  4 16:32:38 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:43 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:32:43 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:48 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:53 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:32:55 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:32:58 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:03 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:08 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:33:08 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:12 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1001 !!!
Jan  4 16:33:20 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:33:24 (none) daemon.err udhcpd[13968]: max_leases=235 is too big, setting to 101
Jan  4 16:33:24 (none) daemon.emerg dnsmasq[14005]: lease_file is NULL:
Jan  4 16:33:24 (none) daemon.emerg dnsmasq[14005]: init_dns_ip:num is 1
Jan  4 16:33:30 (none) kern.err DM-FOTA[2015]: platform/dmc_print.c, 380, #####current time is 1767544410,expected polling time is 1768894860
Jan  4 16:33:30 (none) kern.warn DM-FOTA[2015]: platform/dmc_print.c, 380, OMA_DM_POLLING_NOT_PASSED
Jan  4 16:33:30 (none) kern.warn DM-FOTA[2015]: platform/dmc_print.c, 380, OMA_DM_POLLING_SLEEP 60 about seconds
Jan  4 16:33:31 (none) kern.emerg rndis[742]: rndis.c, 243 receive MSG_CMD_WEB_REQ_RNDIS_DISCONNECT
Jan  4 16:33:31 (none) kern.warn rndis[742]: soft_timer.c, 355 DeleteSoftTimer 0x000f failed, not exist!
Jan  4 16:33:31 (none) kern.err rndis[742]: soft_timer.c, 87 sigwaitinfo() returned err: 4; Interrupted system call
Jan  4 16:33:31 (none) kern.notice rndis[742]: soft_timer.c, 314 CreateSoftTimer index 0 success:  usTimerID = 15,  ucFlag = 0,  ulCurInterval = 50000,  ulNextInterval = 50000,  procCallBack = 0x402eb4,  args =  (nil).
Jan  4 16:33:31 (none) kern.err rndis[742]: soft_timer.c, 87 sigwaitinfo() returned err: 4; Interrupted system call
Jan  4 16:33:31 (none) kern.emerg rndis[742]: rndis.c, 581 do not need to report backup ignore......
Jan  4 16:33:31 (none) kern.err rndis[742]: rndis.c, 1639 send_message failed:can not get target msg id 0x1046!
Jan  4 16:33:32 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:32 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:32 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1001 !!!
Jan  4 16:33:32 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:32 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1022 !!!
Jan  4 16:33:32 (none) kern.err zte_router[1064]: zte_router.c, 110 send_message failed:can not get target msg id 0x1046!
Jan  4 16:33:32 (none) kern.warn kernel: [ 1186.160000]
Jan  4 16:33:32 (none) kern.warn kernel: [ 1186.160000] /home/scl/ci/workspace/Soft4_MF286R1_TMOPL_CPE/qsdk/build_dir/linux-ar71xx_generic/zte_genl_kernel-1.0/zte_genl_kernel_main.c[197]: INFO:Recv from userspace: [5]
Jan  4 16:33:33 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:33:33 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:38 (none) kern.emerg rndis[742]: rndis.c, 211 receive MSG_CMD_WEB_REQ_RNDIS_CONNECT
Jan  4 16:33:38 (none) kern.notice rndis[742]: soft_timer.c, 358 DeleteSoftTimer 0x000f success!
Jan  4 16:33:38 (none) kern.notice rndis[742]: soft_timer.c, 314 CreateSoftTimer index 0 success:  usTimerID = 15,  ucFlag = 0,  ulCurInterval = 50000,  ulNextInterval = 50000,  procCallBack = 0x402eb4,  args =  (nil).
Jan  4 16:33:38 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:43 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:45 (none) kern.err rndis[742]: soft_timer.c, 87 sigwaitinfo() returned err: 4; Interrupted system call
Jan  4 16:33:45 (none) kern.emerg rndis[742]: rndis.c, 1037 ProcAtZGIPDNSNotify :1,IP,10.6.165.108,10.6.165.108,194.204.159.1,194.204.152.34,,,,
Jan  4 16:33:45 (none) kern.emerg rndis[742]: rndis.c, 1041 ProcAtZGIPDNSNotify IP
Jan  4 16:33:45 (none) kern.err rndis[742]: soft_timer.c, 87 sigwaitinfo() returned err: 4; Interrupted system call
Jan  4 16:33:45 (none) kern.emerg rndis[742]: rndis.c, 581 do not need to report backup ignore......
Jan  4 16:33:45 (none) kern.err rndis[742]: rndis.c, 1639 send_message failed:can not get target msg id 0x1046!
Jan  4 16:33:45 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1022 !!!
Jan  4 16:33:45 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:33:46 (none) kern.warn kernel: [ 1200.160000]
Jan  4 16:33:46 (none) kern.warn kernel: [ 1200.160000] /home/scl/ci/workspace/Soft4_MF286R1_TMOPL_CPE/qsdk/build_dir/linux-ar71xx_generic/zte_genl_kernel-1.0/zte_genl_kernel_main.c[197]: INFO:Recv from userspace: [1]
Jan  4 16:33:46 (none) daemon.emerg dnsmasq[14832]: lease_file is NULL:
Jan  4 16:33:46 (none) daemon.emerg dnsmasq[14832]: init_dns_ip:num is 1
Jan  4 16:33:46 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1025 !!!
Jan  4 16:33:46 (none) kern.err zte_router[1064]: zte_router.c, 110 send_message failed:can not get target msg id 0x1046!
Jan  4 16:33:48 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:53 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:33:58 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:33:58 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:34:04 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:34:09 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:34:10 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:34:14 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:34:19 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:34:23 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:34:24 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:34:27 (none) kern.err DM-FOTA[2015]: platform/dmc_print.c, 380, #####current time is 1767544467,expected polling time is 1768894860
Jan  4 16:34:27 (none) kern.warn DM-FOTA[2015]: platform/dmc_print.c, 380, OMA_DM_POLLING_NOT_PASSED
Jan  4 16:34:27 (none) kern.warn DM-FOTA[2015]: platform/dmc_print.c, 380, OMA_DM_POLLING_SLEEP 60 about seconds
Jan  4 16:34:28 (none) kern.err rndis[742]: rndis.c, 1840 Rndis_check_connectstate: in
Jan  4 16:34:28 (none) kern.err rndis[742]: rndis.c, 1844 Rndis_check_connectstate: normal connection state, return!
Jan  4 16:34:29 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:34:30 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1001 !!!
Jan  4 16:34:35 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:34:45 (none) daemon.err udhcpd[16120]: max_leases=235 is too big, setting to 101
Jan  4 16:34:45 (none) daemon.emerg dnsmasq[16157]: lease_file is NULL:
Jan  4 16:34:45 (none) daemon.emerg dnsmasq[16157]: init_dns_ip:num is 1
Jan  4 16:34:48 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:35:00 (none) daemon.err udhcpd[16612]: max_leases=235 is too big, setting to 101
Jan  4 16:35:00 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:35:00 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:35:00 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:35:00 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!
Jan  4 16:35:00 (none) daemon.emerg dnsmasq[16649]: lease_file is NULL:
Jan  4 16:35:00 (none) daemon.emerg dnsmasq[16649]: init_dns_ip:num is 1
Jan  4 16:35:00 (none) kern.err mainControl[744]: lib_mainControl.c, 3977 ZT_ASR_setCops:-return UNI_ERROR_FALSE
Jan  4 16:35:04 (none) kern.err zte_router[1064]: zte_router.c, 5326 RECV usSourceModuleID is 0x1040 !!!

czy instalowanie na nim OpenWRT poprawi w jakiś sposób jego działanie?

przeczytałem że to modem, i że najlepiej korzystać z OpenWRT 23.05

ciekawe że jak podpiąłem po LAN to prędkości 2* takie jak po WiFi -,-; (ok 20Mbps czyli nadal bez rewelacji ale jednak - lepiej).

może OpenWRT więcej z niego "wyciśnie"?

tj, nowsze OpenWRT bo z tego, co czytałem, to już jest OpenWRT w nim w sofcie od ZTE

sprawdzę czy da się zainstalować korzystając z exploita będąc podpiętym po LAN'ie (uważam że nie powinno to robić różnicy, czy po LAN czy po WLAN bo te interfejsy *chyba* są zbridgowane - ale spróbuję dla pewności)

jeśli się nie uda złamać go exploitem zdalnie, to idzie na olx i zastanowię się nad innym rozwiązaniem

czy mf286d to też problematyczny sprzęt?

chcę mieć spokój "na lata" - i stabilne, bez restartów łącze, które wyda te 50/50

poprzednio korzystałem z Mikrotika a na OpenWRT miałem WRT54GS - ale to z 20 lat temu

może pora na 5G?