Cezary napisał/a:Nie, nie jest prawdą to co napisałeś. OpenWrt nigdy nie daje prekonfigurowanych obrazów, tam domyślnie jest tylko sprzetowo ustawiony wan na dhcp i tyle (o ile w ogóle jest wan). I nic więcej nie ustawia.
To całe życie żyłem w błędzie! Myślałem, że na etapie budowania są wstrzykiwane jakieś specjalne configi i dlatego wszystko działa. ZTE to mój pierwszy modem LTE z OpenWRT więc stąd zdziwienie. Cała reszta sprzętu to "zwykłe" routery.
smereka napisał/a:A ja lubię Lucynę
Zresztą jak się samemu wszystko skonfiguruje to wtedy jakoś minimalnie się nad tym panuje. Oczywiście można kogoś poprosić o pomoc fizyczna lub logiczną na tym forum z czego proponuje korzystać 
Też tak lubię.
Jak się coś skaszani (samo, albo przez nas), to przynajmniej wiadomo co i jak odkręcić.
Wracajac do mojej zabawy modemem...
U mnie dzieje się coś dziwnego, zabrałem się za szybkie testy, zalockowałem 1800Mhz z pobliskiego BTSa, odpaliłem jakiś speed test po SSH i błędy, coś jakby się przywiesza. To było na mifi, więc wgrałem pełny obraz od IceG, wziąłem modem na kolana i odpaliłem speed test, ale z laptopa.
Jak się zacznie test downloadu, jak zagregują się 2 pasma, jak zaczyna pobieranie, to modem wariuje i sie resetuje. Diody gasną. W logach mam
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.845685] usb 2-1: USB disconnect, device number 3
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.854033] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.855415] option 2-1:1.2: device disconnected
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.868371] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.869806] option 2-1:1.3: device disconnected
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.875836] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.880070] option 2-1:1.4: device disconnected
Thu Jul 28 18:56:31 2022 daemon.notice netifd: Network device 'wwan0' link is down
Thu Jul 28 18:56:31 2022 daemon.notice netifd: Network alias 'wwan0' link is down
Thu Jul 28 18:56:31 2022 daemon.notice netifd: Interface 'wan_4' has link connectivity loss
Thu Jul 28 18:56:31 2022 kern.info kernel: [ 484.892840] qmi_wwan 2-1:1.5 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.0.auto-1, WWAN/QMI device
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): udhcpc: SIOCGIFINDEX: No such device
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): udhcpc: received SIGTERM
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): udhcpc: unicasting a release of 10.247.116.38 to 10.247.116.37
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): udhcpc: sending release
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): udhcpc: can't bind to interface wwan0: No such device
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): udhcpc: bindtodevice: No such device
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): udhcpc: entering released state
Thu Jul 28 18:56:31 2022 daemon.notice netifd: wan_4 (13193): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan_4" } (Permission denied)
Thu Jul 28 18:56:31 2022 daemon.notice netifd: Interface 'wan_4' is now down
Thu Jul 28 18:56:31 2022 daemon.notice netifd: Interface 'wan_4' is disabled
Thu Jul 28 18:56:31 2022 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Thu Jul 28 18:56:33 2022 daemon.notice netifd: wan (16317): Stopping network wan
Thu Jul 28 18:56:33 2022 daemon.notice netifd: wan (16317): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Thu Jul 28 18:56:33 2022 daemon.notice netifd: Interface 'wan' is now down
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.348609] usb 2-1: new SuperSpeed Gen 1 USB device number 4 using xhci-hcd
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.515464] option 2-1:1.2: GSM modem (1-port) converter detected
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.515891] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.523836] option 2-1:1.3: GSM modem (1-port) converter detected
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.528325] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.535454] option 2-1:1.4: GSM modem (1-port) converter detected
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.540581] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.577209] qmi_wwan 2-1:1.5: cdc-wdm0: USB WDM device
Thu Jul 28 18:56:49 2022 kern.info kernel: [ 502.578895] qmi_wwan 2-1:1.5 wwan0: register 'qmi_wwan' at usb-xhci-hcd.0.auto-1, WWAN/QMI device, ba:90:08:13:cc:6d
Thu Jul 28 18:56:51 2022 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jul 28 18:56:51 2022 daemon.notice netifd: wan (17434): Waiting for SIM initialization
Thu Jul 28 18:56:52 2022 daemon.notice netifd: wan (17434): Failed to parse message data
Thu Jul 28 18:56:52 2022 daemon.notice netifd: wan (17434): PIN verification is disabled
Thu Jul 28 18:56:53 2022 daemon.notice netifd: wan (17434): Device does not support 802.3 mode. Informing driver of raw-ip only for wwan0 ..
Thu Jul 28 18:56:53 2022 daemon.notice netifd: wan (17434): Waiting for network registration
Thu Jul 28 18:56:55 2022 daemon.notice netifd: wan (17434): Starting network wan
Thu Jul 28 18:56:55 2022 daemon.notice netifd: wan (17434): Setting up wwan0
Thu Jul 28 18:56:55 2022 daemon.notice netifd: Interface 'wan' is now up
Thu Jul 28 18:56:55 2022 daemon.notice netifd: Network device 'wwan0' link is up
Thu Jul 28 18:56:55 2022 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Jul 28 18:56:55 2022 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Jul 28 18:56:55 2022 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Jul 28 18:56:55 2022 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Jul 28 18:56:55 2022 daemon.notice netifd: wan_4 (17850): udhcpc: started, v1.35.0
Thu Jul 28 18:56:55 2022 daemon.notice netifd: wan_4 (17850): udhcpc: broadcasting discover
Thu Jul 28 18:56:55 2022 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Jul 28 18:56:56 2022 daemon.notice netifd: wan_4 (17850): udhcpc: broadcasting select for 10.253.194.75, server 10.253.194.76
Thu Jul 28 18:56:56 2022 daemon.notice netifd: wan_4 (17850): udhcpc: lease of 10.253.194.75 obtained from 10.253.194.76, lease time 7200
Thu Jul 28 18:56:56 2022 daemon.notice netifd: Interface 'wan_4' is now up
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using nameserver 194.204.159.1#53
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using nameserver 194.204.152.34#53
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using only locally-known addresses for test
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using only locally-known addresses for local
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Thu Jul 28 18:56:56 2022 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Thu Jul 28 18:56:56 2022 user.notice wrtbwmon: Restart for ifup of wan (wwan0)
Thu Jul 28 18:56:57 2022 user.notice firewall: Reloading firewall due to ifup of wan_4 (wwan0)
Thu Jul 28 18:56:58 2022 user.notice wrtbwmon: Restart for ifup of wan_4 (wwan0)
Jest to powtarzalne.
Jak wylacze lockowanie (zarowno pasmo jak i BTS) problem znika zupelnie...