1 Temat przez whiteindian (edytowany przez whiteindian 2016-02-11 12:41:47)

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Temat: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Witajcie,

Nie mogę uporać się z pewną anomalią.
Po wpięciu modemu, nie zadziałał automatycznie.
Doptero gdy uruchomiłem komendę

uqmi -d /dev/cdc-wdm0 --start-network internet --autoconnect

Okazało się, że - jak mi podpowiedział kolega Sigma z forum - był to tryb a'ala HiLink

Dezaktywowałem go komendą

uqmi -d /dev/cdc-wdm0 --stop-network 4294967295 --autoconnect

ifup wan

Jednak modem nadal łączy się automatycznie wyłącznie z pierwszą kartą SIM któa zadziałała z modemem w ruterze. Ani Orange ani Play w Roamingu (prepaid) tylko Aero2 działające w trybie testu (nie BDI) z APN=internet.

W momencie gdy piszę modem w ruterze jest w trybie pracy, wcześniej rozdzielał Internet po wifi i lan.


Jesli nie zrestartuję routera, logread pokazuje qmi bringup failed


root@OpenWrt:~# logread
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.420000] option 1-1:1.1: GSM modem (1-port) converter detected
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.430000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.430000] option 1-1:1.2: GSM modem (1-port) converter detected
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.440000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.450000] usbcore: registered new interface driver qcserial
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.460000] usbserial: USB Serial support registered for Qualcomm USB modem
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.510000] ath: EEPROM regdomain: 0x0
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.510000] ath: EEPROM indicates default country code should be used
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.510000] ath: doing EEPROM country->regdmn map search
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.510000] ath: country maps to regdmn code: 0x3a
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.510000] ath: Country alpha2 being used: US
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.510000] ath: Regpair used: 0x3a
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.520000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.520000] ieee80211 phy0: Atheros AR9340 Rev:2 mem=0xb8100000, irq=47
Thu Feb 11 08:38:24 2016 kern.warn kernel: [   18.530000] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.540000] cfg80211: Calling CRDA for country: US
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.540000] cfg80211: Regulatory domain changed to country: US
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.550000] cfg80211:  DFS Master region: FCC
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.550000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.560000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.570000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A)
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.580000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.590000] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.600000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.610000] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.690000] ath: EEPROM regdomain: 0x0
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.690000] ath: EEPROM indicates default country code should be used
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.690000] ath: doing EEPROM country->regdmn map search
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.690000] ath: country maps to regdmn code: 0x3a
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.690000] ath: Country alpha2 being used: US
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.690000] ath: Regpair used: 0x3a
Thu Feb 11 08:38:24 2016 kern.debug kernel: [   18.700000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Thu Feb 11 08:38:24 2016 kern.info kernel: [   18.700000] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb0000000, irq=40
Thu Feb 11 08:38:28 2016 user.emerg syslog: this file has been obseleted. please call "/sbin/block mount" directly
Thu Feb 11 08:38:28 2016 daemon.err block: /dev/ubi0_1 is already mounted
Thu Feb 11 08:38:28 2016 cron.info crond[1409]: crond (busybox 1.23.2) started, log level 8
Thu Feb 11 08:38:29 2016 authpriv.info dropbear[1429]: Not backgrounding
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.580000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.600000] device eth0.1 entered promiscuous mode
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.600000] device eth0 entered promiscuous mode
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'lan' is enabled
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'lan' is setting up now
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.620000] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'lan' is now up
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.630000] device wwan0 entered promiscuous mode
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.640000] br-lan: port 2(wwan0) entered forwarding state
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.640000] br-lan: port 2(wwan0) entered forwarding state
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.650000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'loopback' is enabled
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'loopback' is now up
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'wan6' is enabled
Thu Feb 11 08:38:34 2016 kern.info kernel: [   30.690000] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Bridge 'br-lan' link is up
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Network device 'wwan0' link is up
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Network device 'lo' link is up
Thu Feb 11 08:38:34 2016 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Feb 11 08:38:35 2016 kern.info kernel: [   31.960000] eth0: link up (1000Mbps/Full duplex)
Thu Feb 11 08:38:35 2016 kern.info kernel: [   31.960000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Feb 11 08:38:35 2016 daemon.notice netifd: Network device 'eth0' link is up
Thu Feb 11 08:38:35 2016 kern.info kernel: [   31.990000] br-lan: port 1(eth0.1) entered forwarding state
Thu Feb 11 08:38:35 2016 kern.info kernel: [   31.990000] br-lan: port 1(eth0.1) entered forwarding state
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.000000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Thu Feb 11 08:38:35 2016 daemon.notice netifd: VLAN 'eth0.1' link is up
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.160000] cfg80211: Calling CRDA for country: PL
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.160000] cfg80211: Regulatory domain changed to country: PL
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.170000] cfg80211:  DFS Master region: ETSI
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.170000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.180000] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.190000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.200000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.210000] cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
Thu Feb 11 08:38:35 2016 kern.info kernel: [   32.220000] cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Thu Feb 11 08:38:36 2016 kern.info kernel: [   32.640000] br-lan: port 2(wwan0) entered forwarding state
Thu Feb 11 08:38:36 2016 daemon.notice netifd: VLAN 'eth0.2' link is up
Thu Feb 11 08:38:36 2016 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Feb 11 08:38:36 2016 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Feb 11 08:38:36 2016 daemon.notice netifd: wan (1763): Waiting for network registration
Thu Feb 11 08:38:36 2016 daemon.notice netifd: wan (1763): Starting network internet
Thu Feb 11 08:38:37 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Feb 11 08:38:37 2016 kern.info kernel: [   33.990000] br-lan: port 1(eth0.1) entered forwarding state
Thu Feb 11 08:38:38 2016 daemon.notice netifd: radio0 (1766): Configuration file: /var/run/hostapd-phy0.conf
Thu Feb 11 08:38:38 2016 kern.info kernel: [   34.750000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Thu Feb 11 08:38:38 2016 daemon.notice netifd: radio1 (1767): Configuration file: /var/run/hostapd-phy1.conf
Thu Feb 11 08:38:38 2016 kern.info kernel: [   34.780000] device wlan0 entered promiscuous mode
Thu Feb 11 08:38:38 2016 kern.info kernel: [   34.820000] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Thu Feb 11 08:38:38 2016 kern.info kernel: [   34.830000] device wlan1 entered promiscuous mode
Thu Feb 11 08:38:38 2016 kern.info kernel: [   34.830000] br-lan: port 4(wlan1) entered forwarding state
Thu Feb 11 08:38:38 2016 kern.info kernel: [   34.840000] br-lan: port 4(wlan1) entered forwarding state
Thu Feb 11 08:38:38 2016 daemon.notice netifd: radio0 (1766): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 11 08:38:38 2016 daemon.notice netifd: radio0 (1766): Using interface wlan0 with hwaddr a0:63:91:7d:04:b7 and ssid "kubatura"
Thu Feb 11 08:38:38 2016 daemon.notice netifd: radio1 (1767): wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 11 08:38:38 2016 daemon.notice netifd: radio1 (1767): wlan1: interface state COUNTRY_UPDATE->HT_SCAN
Thu Feb 11 08:38:38 2016 daemon.notice netifd: wan (1763): Starting DHCP
Thu Feb 11 08:38:38 2016 user.emerg syslog: setting up led WAN (green)
Thu Feb 11 08:38:38 2016 user.emerg syslog: setting up led USB
Thu Feb 11 08:38:38 2016 user.emerg syslog: setting up led WLAN2G
Thu Feb 11 08:38:38 2016 daemon.notice netifd: Interface 'wan' is now up
Thu Feb 11 08:38:38 2016 daemon.notice netifd: radio1 (1767): Using interface wlan1 with hwaddr a0:63:91:7d:04:b9 and ssid "kubatura5"
Thu Feb 11 08:38:38 2016 user.emerg syslog: setting up led WLAN5G
Thu Feb 11 08:38:38 2016 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Feb 11 08:38:38 2016 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Feb 11 08:38:38 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Feb 11 08:38:38 2016 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Feb 11 08:38:38 2016 daemon.notice netifd: wan (1763): Command failed: Unknown error
Thu Feb 11 08:38:39 2016 daemon.notice netifd: Interface 'wan_6' is enabled
Thu Feb 11 08:38:39 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity
Thu Feb 11 08:38:39 2016 daemon.notice netifd: Interface 'wan_6' is setting up now
Thu Feb 11 08:38:39 2016 daemon.notice netifd: wan (1763): Command failed: Unknown error
Thu Feb 11 08:38:39 2016 user.notice root: qmi bringup failed, retry in 15s
Thu Feb 11 08:38:39 2016 kern.info kernel: [   35.780000] br-lan: port 4(wlan1) entered disabled state
Thu Feb 11 08:38:39 2016 daemon.notice netifd: wan_4 (2085): udhcpc (v1.23.2) started
Thu Feb 11 08:38:39 2016 daemon.notice netifd: wan_4 (2085): Sending discover...
Thu Feb 11 08:38:40 2016 daemon.warn odhcpd[1374]: DHCPV6 SOLICIT IA_NA from 000100011dc0eba800508db78552 on br-lan: ok fd6c:6990:c185::b04/128
Thu Feb 11 08:38:40 2016 daemon.warn odhcpd[1374]: DHCPV6 REQUEST IA_NA from 000100011dc0eba800508db78552 on br-lan: ok fd6c:6990:c185::b04/128
Thu Feb 11 08:38:40 2016 daemon.info procd: - init complete -
Thu Feb 11 08:38:40 2016 kern.info kernel: [   36.990000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 08:38:40 2016 kern.info kernel: [   37.000000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 08:38:40 2016 kern.info kernel: [   37.010000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Thu Feb 11 08:38:40 2016 daemon.notice netifd: radio0 (1766): wlan0: interface state COUNTRY_UPDATE->ENABLED
Thu Feb 11 08:38:40 2016 daemon.notice netifd: radio0 (1766): wlan0: AP-ENABLED
Thu Feb 11 08:38:40 2016 kern.info kernel: [   37.280000] br-lan: port 4(wlan1) entered forwarding state
Thu Feb 11 08:38:40 2016 kern.info kernel: [   37.290000] br-lan: port 4(wlan1) entered forwarding state
Thu Feb 11 08:38:40 2016 kern.info kernel: [   37.290000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Thu Feb 11 08:38:41 2016 daemon.notice netifd: radio1 (1767): wlan1: interface state HT_SCAN->ENABLED
Thu Feb 11 08:38:41 2016 daemon.notice netifd: radio1 (1767): wlan1: AP-ENABLED
Thu Feb 11 08:38:41 2016 daemon.notice netifd: Network device 'wlan0' link is up
Thu Feb 11 08:38:41 2016 daemon.notice netifd: Network device 'wlan1' link is up
Thu Feb 11 08:38:42 2016 kern.info kernel: [   39.000000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 08:38:42 2016 daemon.notice netifd: wan_4 (2085): Sending discover...
Thu Feb 11 08:38:42 2016 kern.info kernel: [   39.290000] br-lan: port 4(wlan1) entered forwarding state
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq[2184]: started, version 2.73 cachesize 150
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq[2184]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq[2184]: DNS service limited to local subnets
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq-dhcp[2184]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq[2184]: using local addresses only for domain lan
Thu Feb 11 08:38:44 2016 daemon.warn dnsmasq[2184]: no servers found in /tmp/resolv.conf.auto, will retry
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq[2184]: read /etc/hosts - 1 addresses
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq[2184]: read /tmp/hosts/dhcp - 1 addresses
Thu Feb 11 08:38:44 2016 daemon.info dnsmasq-dhcp[2184]: read /etc/ethers - 0 addresses
Thu Feb 11 08:38:44 2016 user.notice upnp daemon: external interface not found, not starting
Thu Feb 11 08:38:45 2016 daemon.notice netifd: wan_4 (2085): Sending discover...
Thu Feb 11 08:38:46 2016 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Feb 11 08:38:48 2016 user.notice ddns-scripts[2455]: myddns_ipv4: PID '2455' started at 2016-02-11 08:38
Thu Feb 11 08:38:48 2016 user.warn ddns-scripts[2455]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Feb 11 08:38:48 2016 user.warn ddns-scripts[2455]: myddns_ipv4: PID '2455' exit WITH ERROR '1' at 2016-02-11 08:38
Thu Feb 11 08:40:00 2016 cron.info crond[1409]: USER root pid 2767 cmd /bin/tester.sh
Thu Feb 11 08:40:01 2016 daemon.notice netifd: wan_4 (2085): Received SIGTERM
Thu Feb 11 08:40:01 2016 daemon.notice netifd: Interface 'wan_4' is now down
Thu Feb 11 08:40:01 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity loss
Thu Feb 11 08:40:01 2016 daemon.notice netifd: wan (2777): Stopping network
Thu Feb 11 08:40:01 2016 daemon.notice netifd: Interface 'wan_6' is now down
Thu Feb 11 08:40:01 2016 daemon.notice netifd: Interface 'wan_6' is disabled
Thu Feb 11 08:40:01 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Thu Feb 11 08:40:01 2016 daemon.notice netifd: wan (2777): Command failed: Permission denied
Thu Feb 11 08:40:01 2016 daemon.notice netifd: Interface 'wan' is now down
Thu Feb 11 08:40:01 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 11 08:40:02 2016 daemon.notice netifd: wan (2815): Waiting for network registration
Thu Feb 11 08:40:02 2016 daemon.notice netifd: wan (2815): Starting network internet
Thu Feb 11 08:40:02 2016 daemon.notice netifd: wan (2815): Starting DHCP
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Interface 'wan' is now up
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Feb 11 08:40:02 2016 daemon.notice netifd: wan (2815): Command failed: Unknown error
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Interface 'wan_6' is enabled
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity
Thu Feb 11 08:40:02 2016 daemon.notice netifd: Interface 'wan_6' is setting up now
Thu Feb 11 08:40:02 2016 daemon.notice netifd: wan (2815): Command failed: Unknown error
Thu Feb 11 08:40:02 2016 user.notice root: qmi bringup failed, retry in 15s
Thu Feb 11 08:40:02 2016 daemon.notice netifd: wan_4 (2882): udhcpc (v1.23.2) started
Thu Feb 11 08:40:03 2016 daemon.notice netifd: wan_4 (2882): Sending discover...
Thu Feb 11 08:40:04 2016 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Feb 11 08:40:06 2016 daemon.notice netifd: wan_4 (2882): Sending discover...
Thu Feb 11 08:40:06 2016 user.notice ddns-scripts[3039]: myddns_ipv4: PID '3039' started at 2016-02-11 08:40
Thu Feb 11 08:40:06 2016 user.warn ddns-scripts[3039]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Feb 11 08:40:06 2016 user.warn ddns-scripts[3039]: myddns_ipv4: PID '3039' exit WITH ERROR '1' at 2016-02-11 08:40
Thu Feb 11 08:40:09 2016 daemon.notice netifd: wan_4 (2882): Sending discover...
Thu Feb 11 08:40:24 2016 authpriv.info dropbear[3100]: Child connection from 192.168.1.2:49844
Thu Feb 11 08:40:32 2016 authpriv.notice dropbear[3100]: Password auth succeeded for 'root' from 192.168.1.2:49844
Thu Feb 11 08:41:14 2016 daemon.notice netifd: Interface 'wan_6' is now down
Thu Feb 11 08:41:14 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Thu Feb 11 08:41:14 2016 daemon.notice netifd: wan_4 (2882): Received SIGTERM
Thu Feb 11 08:41:14 2016 daemon.notice netifd: Interface 'wan_4' is now down
Thu Feb 11 08:41:14 2016 daemon.notice netifd: Interface 'wan_4' is disabled
Thu Feb 11 08:41:14 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity loss
Thu Feb 11 08:41:14 2016 daemon.notice netifd: wan (3233): Stopping network
Thu Feb 11 08:41:16 2016 daemon.notice netifd: wan (3233): Command failed: Permission denied
Thu Feb 11 08:41:16 2016 daemon.notice netifd: Interface 'wan' is now down
Thu Feb 11 08:41:16 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 11 08:41:16 2016 daemon.notice netifd: wan (3303): Waiting for network registration
Thu Feb 11 08:41:16 2016 daemon.notice netifd: wan (3303): Starting network internet

-----------
Nie wiem czy skrypt podnoszenia w ogóle od początku działa, zauważyłem że modem po kilku minutach może się podnosi (o ile się podnosi), ale nie wiem czy jest to regularne........

touch /bin/tester.sh
chmod 755 /bin/tester.sh
nano /bin/tester.sh



    #!/bin/sh
    if ! ping -q -c 1 -W 10 8.8.8.8 > /dev/null; then
        (ifup wan) &
    fi

/etc/init.d/cron stop
echo "*/2 * * * * /bin/tester.sh" >> /etc/crontabs/root

--------------------------------------

Jest to mój drugi post, proszę o wyrozumiałość, mogę nie zrozumieć waszych poleceń, lecz nie wiem co się dzieje, i nie chcę bardziej pomgmatwać sprawy.

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

an (3303): Waiting for network registration itd. Modem na po prostu problem z logowaniem się. Jesteś pewien że modem nie ma simlocka/cardlocka?

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

3 Odpowiedź przez whiteindian (edytowany przez whiteindian 2016-02-11 13:09:09)

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Nie ma, bo działa na każdej karcie w komputerze PC od 2 lat.

4 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Włóż karę orange, połącz modem przez hub usb z własnym zasianiem (koniecznie), zaloguj sie przez ssh do routera i pokaż:

uci show network
uqmi -d /dev/cdc-wdm0 --get-pin-status
uqmi -d /dev/cdc-wdm0 --get-serving-system
uqmi -d /dev/cdc-wdm0 --get-signal-info
uqmi -d /dev/cdc-wdm0 --get-data-status

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

5 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Hub Unitek Y-2143, chyba na pewno ma zasilacz 2A.

root@OpenWrt:~# uci show network
network.loopback=interface
network.loopback.ifname='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.globals.ula_prefix='fd6c:6990:c185::/48'
network.lan=interface
network.lan.force_link='1'
network.lan.type='bridge'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.lan.macaddr='a0:63:91:7d:04:b7'
network.lan._orig_ifname='eth0.1 wlan0 wlan1'
network.lan._orig_bridge='true'
network.lan.ifname='eth0.1 wwan0'
network.wan=interface
network.wan._orig_ifname='eth0.2'
network.wan._orig_bridge='false'
network.wan.proto='qmi'
network.wan.device='/dev/cdc-wdm0'
network.wan.apn='internet'
network.wan.ipv6='0'
network.wan.username='root'
network.wan.password='password'
network.wan.mode='all'
network.wan6=interface
network.wan6.ifname='eth0.2'
network.wan6.proto='dhcpv6'
network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device='switch0'
network.@switch_vlan[0].vlan='1'
network.@switch_vlan[0].ports='0t 1 2 3 4'
network.@switch_vlan[1]=switch_vlan
network.@switch_vlan[1].device='switch0'
network.@switch_vlan[1].vlan='2'
network.@switch_vlan[1].ports='0t 5'
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-pin-status
{
        "pin1_status": "disabled",
        "pin1_verify_tries": 3,
        "pin1_unblock_tries": 10,
        "pin2_status": "not_verified",
        "pin2_verify_tries": 3,
        "pin2_unblock_tries": 10
}
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-serving-system
{
        "registration": "registered",
        "plmn_mcc": 260,
        "plmn_mnc": 3,
        "plmn_description": "Orange",
        "roaming": false
}
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-signal-info
{
        "type": "wcdma",
        "rssi": -73,
        "ecio": -8
}
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-data-status
"disconnected"
root@OpenWrt:~#

6 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

network.lan.ifname='eth0.1 wwan0'

Tu jest źle. Tylko 'eth0.1', wwan0 nie ma prawa tu istnieć. Zmień to na lanie i normalnie zrób ifup wan.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

7 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Poprawione. Ale nadal tylko Aero2 działą po routerze. Musiałem robić jego restart bo tak to nie wstawał.

root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-serving-system
{
        "registration": "registered",
        "plmn_mcc": 260,
        "plmn_mnc": 1,
        "plmn_description": "Aero2",
        "roaming": false
}
root@OpenWrt:~#  uqmi -d /dev/cdc-wdm0 --get-signal-info
{
        "type": "wcdma",
        "rssi": -58,
        "ecio": -13
}
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-data-status
"connected"
root@OpenWrt:~#

Faktycznie świetny sygnał, ale Orange leci z NetWorks! któy praktycznie mam pod nosem, i T-M nieraz pracuje przy sygnale ok. -60dBm

8 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Wróć znów do tego Orange, pokaż to co wyżej +

ifstatus wan
ifstatus wan_4
logread

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

9 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Karta Play w raomingu T-M znowuż nie może otrzymać danych na temat sygnału, kursor w terminalu stoi, przerwałem.

----------------


root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-serving-system
{
        "registration": "registered",
        "plmn_mcc": 260,
        "plmn_mnc": 3,
        "plmn_description": "Orange",
        "roaming": false
}
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-signal-info
{
        "type": "wcdma",
        "rssi": -67,
        "ecio": -12
}
root@OpenWrt:~# qmi -d /dev/cdc-wdm0 --get-data-status
-ash: qmi: not found
root@OpenWrt:~# ifstatus wan
{
        "up": true,
        "pending": false,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "uptime": 11,
        "l3_device": "wwan0",
        "proto": "qmi",
        "metric": 0,
        "delegation": true,
        "ipv4-address": [

        ],
        "ipv6-address": [

        ],
        "ipv6-prefix": [

        ],
        "ipv6-prefix-assignment": [

        ],
        "route": [

        ],
        "dns-server": [

        ],
        "dns-search": [

        ],
        "inactive": {
                "ipv4-address": [

                ],
                "ipv6-address": [

                ],
                "route": [

                ],
                "dns-server": [

                ],
                "dns-search": [

                ]
        },
        "data": {

        }
}
root@OpenWrt:~# ifstatus wan_4
{
        "up": false,
        "pending": true,
        "available": true,
        "autostart": true,
        "dynamic": true,
        "proto": "dhcp",
        "device": "wwan0",
        "data": {

        }
}
root@OpenWrt:~# logread
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Interface 'lan' is now up
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Interface 'loopback' is enabled
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Interface 'loopback' is now up
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Interface 'wan6' is enabled
Thu Feb 11 14:17:16 2016 kern.info kernel: [   31.070000] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Network device 'lo' link is up
Thu Feb 11 14:17:16 2016 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.320000] cfg80211: Calling CRDA for country: PL
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.320000] cfg80211: Regulatory domain changed to country: PL
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.330000] cfg80211:  DFS Master region: ETSI
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.330000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.340000] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.350000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.360000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.370000] cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.380000] cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.860000] eth0: link up (1000Mbps/Full duplex)
Thu Feb 11 14:17:18 2016 daemon.notice netifd: Network device 'eth0' link is up
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.900000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.900000] br-lan: port 1(eth0.1) entered forwarding state
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.910000] br-lan: port 1(eth0.1) entered forwarding state
Thu Feb 11 14:17:18 2016 kern.info kernel: [   32.910000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Thu Feb 11 14:17:18 2016 daemon.notice netifd: VLAN 'eth0.1' link is up
Thu Feb 11 14:17:18 2016 daemon.notice netifd: VLAN 'eth0.2' link is up
Thu Feb 11 14:17:18 2016 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Feb 11 14:17:18 2016 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Feb 11 14:17:18 2016 kern.info kernel: [   33.090000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Thu Feb 11 14:17:18 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Feb 11 14:17:18 2016 daemon.notice netifd: Bridge 'br-lan' link is up
Thu Feb 11 14:17:18 2016 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Feb 11 14:17:20 2016 user.emerg syslog: setting up led WAN (green)
Thu Feb 11 14:17:20 2016 user.emerg syslog: setting up led USB
Thu Feb 11 14:17:20 2016 user.emerg syslog: setting up led WLAN2G
Thu Feb 11 14:17:20 2016 user.emerg syslog: setting up led WLAN5G
Thu Feb 11 14:17:20 2016 kern.info kernel: [   34.910000] br-lan: port 1(eth0.1) entered forwarding state
Thu Feb 11 14:17:21 2016 daemon.notice netifd: radio1 (1818): Configuration file: /var/run/hostapd-phy1.conf
Thu Feb 11 14:17:21 2016 kern.info kernel: [   35.570000] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Thu Feb 11 14:17:21 2016 daemon.notice netifd: radio1 (1818): wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 11 14:17:21 2016 kern.info kernel: [   35.600000] device wlan1 entered promiscuous mode
Thu Feb 11 14:17:21 2016 daemon.notice netifd: radio0 (1817): Configuration file: /var/run/hostapd-phy0.conf
Thu Feb 11 14:17:21 2016 daemon.notice netifd: radio1 (1818): wlan1: interface state COUNTRY_UPDATE->HT_SCAN
Thu Feb 11 14:17:21 2016 kern.info kernel: [   35.680000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Thu Feb 11 14:17:21 2016 kern.info kernel: [   35.720000] device wlan0 entered promiscuous mode
Thu Feb 11 14:17:21 2016 kern.info kernel: [   35.720000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 14:17:21 2016 kern.info kernel: [   35.730000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 14:17:21 2016 daemon.notice netifd: radio0 (1817): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 11 14:17:21 2016 daemon.notice netifd: radio0 (1817): Using interface wlan0 with hwaddr a0:63:91:7d:04:b7 and ssid "kubatura"
Thu Feb 11 14:17:21 2016 daemon.notice netifd: radio1 (1818): Using interface wlan1 with hwaddr a0:63:91:7d:04:b9 and ssid "kubatura5"
Thu Feb 11 14:17:21 2016 daemon.notice netifd: wan (1814): Waiting for network registration
Thu Feb 11 14:17:21 2016 daemon.notice netifd: wan (1814): Starting network internet
Thu Feb 11 14:17:21 2016 daemon.info procd: - init complete -
Thu Feb 11 14:17:22 2016 kern.info kernel: [   36.570000] br-lan: port 3(wlan0) entered disabled state
Thu Feb 11 14:17:22 2016 daemon.warn odhcpd[1426]: DHCPV6 SOLICIT IA_NA from 000100011dc0eba800508db78552 on br-lan: ok fd6c:6990:c185::b04/128
Thu Feb 11 14:17:22 2016 daemon.warn odhcpd[1426]: DHCPV6 REQUEST IA_NA from 000100011dc0eba800508db78552 on br-lan: ok fd6c:6990:c185::b04/128
Thu Feb 11 14:17:22 2016 daemon.notice netifd: wan (1814): Starting DHCP
Thu Feb 11 14:17:22 2016 daemon.notice netifd: Interface 'wan' is now up
Thu Feb 11 14:17:22 2016 daemon.notice netifd: Network device 'wwan0' link is up
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Feb 11 14:17:23 2016 daemon.notice netifd: wan (1814): Command failed: Unknown error
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Interface 'wan_6' is enabled
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Interface 'wan_6' is setting up now
Thu Feb 11 14:17:23 2016 daemon.notice netifd: wan (1814): Command failed: Unknown error
Thu Feb 11 14:17:23 2016 user.notice root: qmi bringup failed, retry in 15s
Thu Feb 11 14:17:23 2016 kern.info kernel: [   37.390000] br-lan: port 2(wlan1) entered forwarding state
Thu Feb 11 14:17:23 2016 kern.info kernel: [   37.400000] br-lan: port 2(wlan1) entered forwarding state
Thu Feb 11 14:17:23 2016 kern.info kernel: [   37.410000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Thu Feb 11 14:17:23 2016 kern.info kernel: [   37.450000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 14:17:23 2016 kern.info kernel: [   37.450000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 14:17:23 2016 kern.info kernel: [   37.460000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Thu Feb 11 14:17:23 2016 daemon.notice netifd: radio1 (1818): wlan1: interface state HT_SCAN->ENABLED
Thu Feb 11 14:17:23 2016 daemon.notice netifd: radio1 (1818): wlan1: AP-ENABLED
Thu Feb 11 14:17:23 2016 daemon.notice netifd: radio0 (1817): wlan0: interface state COUNTRY_UPDATE->ENABLED
Thu Feb 11 14:17:23 2016 daemon.notice netifd: radio0 (1817): wlan0: AP-ENABLED
Thu Feb 11 14:17:23 2016 daemon.notice netifd: wan_4 (2207): udhcpc (v1.23.2) started
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Network device 'wlan1' link is up
Thu Feb 11 14:17:23 2016 daemon.notice netifd: Network device 'wlan0' link is up
Thu Feb 11 14:17:23 2016 daemon.notice netifd: wan_4 (2207): Sending discover...
Thu Feb 11 14:17:25 2016 kern.info kernel: [   39.400000] br-lan: port 2(wlan1) entered forwarding state
Thu Feb 11 14:17:25 2016 kern.info kernel: [   39.450000] br-lan: port 3(wlan0) entered forwarding state
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq[2246]: started, version 2.73 cachesize 150
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq[2246]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq[2246]: DNS service limited to local subnets
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq-dhcp[2246]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq[2246]: using local addresses only for domain lan
Thu Feb 11 14:17:25 2016 daemon.warn dnsmasq[2246]: no servers found in /tmp/resolv.conf.auto, will retry
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq[2246]: read /etc/hosts - 1 addresses
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq[2246]: read /tmp/hosts/odhcpd - 1 addresses
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq[2246]: read /tmp/hosts/dhcp - 1 addresses
Thu Feb 11 14:17:25 2016 daemon.info dnsmasq-dhcp[2246]: read /etc/ethers - 0 addresses
Thu Feb 11 14:17:26 2016 user.notice upnp daemon: external interface not found, not starting
Thu Feb 11 14:17:26 2016 daemon.notice netifd: wan_4 (2207): Sending discover...
Thu Feb 11 14:17:28 2016 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Feb 11 14:17:29 2016 user.notice ddns-scripts[2517]: myddns_ipv4: PID '2517' started at 2016-02-11 14:17
Thu Feb 11 14:17:29 2016 daemon.notice netifd: wan_4 (2207): Sending discover...
Thu Feb 11 14:17:29 2016 user.warn ddns-scripts[2517]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Feb 11 14:17:30 2016 user.warn ddns-scripts[2517]: myddns_ipv4: PID '2517' exit WITH ERROR '1' at 2016-02-11 14:17
Thu Feb 11 14:18:00 2016 cron.info crond[1464]: USER root pid 2630 cmd /bin/tester.sh
Thu Feb 11 14:18:00 2016 daemon.notice netifd: wan_4 (2207): Received SIGTERM
Thu Feb 11 14:18:00 2016 daemon.notice netifd: Interface 'wan_4' is now down
Thu Feb 11 14:18:00 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity loss
Thu Feb 11 14:18:00 2016 daemon.notice netifd: wan (2640): Stopping network
Thu Feb 11 14:18:00 2016 daemon.notice netifd: Interface 'wan_6' is now down
Thu Feb 11 14:18:00 2016 daemon.notice netifd: Interface 'wan_6' is disabled
Thu Feb 11 14:18:00 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Thu Feb 11 14:18:04 2016 daemon.notice netifd: wan (2640): Command failed: Permission denied
Thu Feb 11 14:18:04 2016 daemon.notice netifd: Interface 'wan' is now down
Thu Feb 11 14:18:04 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 11 14:18:05 2016 daemon.notice netifd: wan (2711): Waiting for network registration
Thu Feb 11 14:18:05 2016 daemon.notice netifd: wan (2711): Starting network internet
Thu Feb 11 14:18:06 2016 daemon.notice netifd: wan (2711): Starting DHCP
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Interface 'wan' is now up
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Network device 'wwan0' link is up
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Feb 11 14:18:06 2016 daemon.notice netifd: wan (2711): Command failed: Unknown error
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Interface 'wan_6' is enabled
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity
Thu Feb 11 14:18:06 2016 daemon.notice netifd: Interface 'wan_6' is setting up now
Thu Feb 11 14:18:06 2016 daemon.notice netifd: wan (2711): Command failed: Unknown error
Thu Feb 11 14:18:06 2016 user.notice root: qmi bringup failed, retry in 15s
Thu Feb 11 14:18:06 2016 daemon.notice netifd: wan_4 (2758): udhcpc (v1.23.2) started
Thu Feb 11 14:18:06 2016 daemon.notice netifd: wan_4 (2758): Sending discover...
Thu Feb 11 14:18:07 2016 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Feb 11 14:18:08 2016 user.notice ddns-scripts[2876]: myddns_ipv4: PID '2876' started at 2016-02-11 14:18
Thu Feb 11 14:18:08 2016 user.warn ddns-scripts[2876]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Feb 11 14:18:08 2016 user.warn ddns-scripts[2876]: myddns_ipv4: PID '2876' exit WITH ERROR '1' at 2016-02-11 14:18
Thu Feb 11 14:18:09 2016 daemon.notice netifd: wan_4 (2758): Sending discover...
Thu Feb 11 14:18:12 2016 daemon.notice netifd: wan_4 (2758): Sending discover...
Thu Feb 11 14:18:18 2016 daemon.notice netifd: wan (2942): Stopping network
Thu Feb 11 14:18:18 2016 daemon.notice netifd: Interface 'wan_6' is now down
Thu Feb 11 14:18:18 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Thu Feb 11 14:18:18 2016 daemon.notice netifd: wan_4 (2758): Received SIGTERM
Thu Feb 11 14:18:18 2016 daemon.notice netifd: Interface 'wan_4' is now down
Thu Feb 11 14:18:18 2016 daemon.notice netifd: Interface 'wan_4' is disabled
Thu Feb 11 14:18:18 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity loss
Thu Feb 11 14:18:19 2016 daemon.notice netifd: wan (2942): Command failed: Permission denied
Thu Feb 11 14:18:19 2016 daemon.notice netifd: Interface 'wan' is now down
Thu Feb 11 14:18:19 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 11 14:18:19 2016 daemon.notice netifd: wan (2974): Waiting for network registration
Thu Feb 11 14:18:19 2016 daemon.notice netifd: wan (2974): Starting network internet
Thu Feb 11 14:18:51 2016 daemon.notice netifd: wan (2974): Starting DHCP
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Interface 'wan' is now up
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Network device 'wwan0' link is up
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Feb 11 14:18:51 2016 daemon.notice netifd: wan (2974): Command failed: Unknown error
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Interface 'wan_6' is enabled
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity
Thu Feb 11 14:18:51 2016 daemon.notice netifd: Interface 'wan_6' is setting up now
Thu Feb 11 14:18:51 2016 daemon.notice netifd: wan (2974): Command failed: Unknown error
Thu Feb 11 14:18:51 2016 user.notice root: qmi bringup failed, retry in 15s
Thu Feb 11 14:18:51 2016 daemon.notice netifd: wan_4 (3073): udhcpc (v1.23.2) started
Thu Feb 11 14:18:51 2016 daemon.notice netifd: wan_4 (3073): Sending discover...
Thu Feb 11 14:18:52 2016 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Feb 11 14:18:53 2016 user.notice ddns-scripts[3192]: myddns_ipv4: PID '3192' started at 2016-02-11 14:18
Thu Feb 11 14:18:53 2016 user.warn ddns-scripts[3192]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Feb 11 14:18:53 2016 user.warn ddns-scripts[3192]: myddns_ipv4: PID '3192' exit WITH ERROR '1' at 2016-02-11 14:18
Thu Feb 11 14:18:54 2016 authpriv.info dropbear[3241]: Child connection from 192.168.1.2:50659
Thu Feb 11 14:18:54 2016 daemon.notice netifd: wan_4 (3073): Sending discover...
Thu Feb 11 14:18:57 2016 daemon.notice netifd: wan_4 (3073): Sending discover...
Thu Feb 11 14:19:05 2016 authpriv.notice dropbear[3241]: Password auth succeeded for 'root' from 192.168.1.2:50659
Thu Feb 11 14:20:00 2016 cron.info crond[1464]: USER root pid 3339 cmd /bin/tester.sh
Thu Feb 11 14:20:00 2016 daemon.notice netifd: wan_4 (3073): Received SIGTERM
Thu Feb 11 14:20:00 2016 daemon.notice netifd: Interface 'wan_4' is now down
Thu Feb 11 14:20:00 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity loss
Thu Feb 11 14:20:00 2016 daemon.notice netifd: wan (3349): Stopping network
Thu Feb 11 14:20:00 2016 daemon.notice netifd: Interface 'wan_6' is now down
Thu Feb 11 14:20:00 2016 daemon.notice netifd: Interface 'wan_6' is disabled
Thu Feb 11 14:20:00 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Thu Feb 11 14:20:00 2016 daemon.notice netifd: wan (3349): Command failed: Permission denied
Thu Feb 11 14:20:00 2016 daemon.notice netifd: Interface 'wan' is now down
Thu Feb 11 14:20:00 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 11 14:20:01 2016 daemon.notice netifd: wan (3385): Waiting for network registration
Thu Feb 11 14:20:01 2016 daemon.notice netifd: wan (3385): Starting network internet
Thu Feb 11 14:20:02 2016 daemon.notice netifd: wan (3385): Starting DHCP
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Interface 'wan' is now up
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Network device 'wwan0' link is up
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Interface 'wan_4' is enabled
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Interface 'wan_4' has link connectivity
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Interface 'wan_4' is setting up now
Thu Feb 11 14:20:02 2016 daemon.notice netifd: wan (3385): Command failed: Unknown error
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Interface 'wan_6' is enabled
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Interface 'wan_6' has link connectivity
Thu Feb 11 14:20:02 2016 daemon.notice netifd: Interface 'wan_6' is setting up now
Thu Feb 11 14:20:02 2016 daemon.notice netifd: wan (3385): Command failed: Unknown error
Thu Feb 11 14:20:02 2016 user.notice root: qmi bringup failed, retry in 15s
Thu Feb 11 14:20:02 2016 daemon.notice netifd: wan_4 (3468): udhcpc (v1.23.2) started
Thu Feb 11 14:20:03 2016 daemon.notice netifd: wan_4 (3468): Sending discover...
Thu Feb 11 14:20:03 2016 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Thu Feb 11 14:20:04 2016 user.notice ddns-scripts[3582]: myddns_ipv4: PID '3582' started at 2016-02-11 14:20
Thu Feb 11 14:20:04 2016 user.warn ddns-scripts[3582]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Feb 11 14:20:04 2016 user.warn ddns-scripts[3582]: myddns_ipv4: PID '3582' exit WITH ERROR '1' at 2016-02-11 14:20
Thu Feb 11 14:20:06 2016 daemon.notice netifd: wan_4 (3468): Sending discover...
Thu Feb 11 14:20:09 2016 daemon.notice netifd: wan_4 (3468): Sending discover...
root@OpenWrt:~#

10 Odpowiedź przez Cezary (edytowany przez Cezary 2016-02-11 15:14:51)

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Do sieci się zarejestrował, nie otrzymał nic od operatora z jakiegoś powodu.

Nie pamiętam już czy E398 działa w zwykłym trybie - jeżeli masz /dev/ttyUSB* to zmień proto na 3g i zobacz czy się połączy.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

11 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Wykonałem http://eko.one.pl/?p=openwrt-3g#obsugam … ybierasppp bez linii pincode

Wszystko fajnie, dzięki, oprócz jednej rzeczy.  Teraz modem z kartą Aero2 (a prawdopodobnie Plus również) w takim układzie nie działa....

Trudno mi powiedzieć czy na przykłąd abonamentu nie będę miał w T-M, a nocki uruchamiał z Plus. W sumie zastanawia mnie czy wydajność teraz jakoś się zmieni?

12 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

A w aero wpisz apn darmowy. Nie internet.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

13 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Zasugerowałęm się odruchowo, bo w Windows jakoś mu nie przeszkadzało z APN-internet, w dodatku mam włączony pakiet testowy.

Z pozsoatałych modemów mam E3131s2 bez HiLink i E180. Zwłaszcza ten pierwszy mnie interesuje, czy oba mają jakieś szczególne preferencje?

14 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Oba powinny chodzić bez problemów.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

15 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

ussd159 to archaiczny program, ale przykłądowo w Play sprawdzam stan pakietów i cały czas wyświetla mi tyle samo danych, jakby zapamiętał sprawdzanie z windowsa. 3ginfo pokazuje ile danych w ogóle zużyto.
W ogóle wypluwa jakiś ciąg robaczków pod sam koniec w terminalu.

ussd159 -v -p /dev/ttyUSB1 -t 30 -u *108# - czy tez kod w cudzysłowie.

Czy jest jakiś inny skuteczny dla USSD?

16 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Napisz skrypt. Jeżeli to virginmobile to masz gotowca w 3ginfo.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

17 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Toż to ten sam kod co w Virgin ale nie zwraca poprawnie,
"Play 24 Menu1 Konto2 Uslugi / Promocje0 WyjscieWiecej opcji znajdziesz w Play24 na ".

opengt
set com 115200n81
set comecho off
set senddelay 0.02
waitquiet 0.2 0.2
send "at+cmgf=0^m"
waitfor 5 "OK"
if % = -1 goto error
send "at+cscs=\"IRA\"^m"
waitfor 5 "OK"
if % = -1 goto error
send "AT+CUSD=1,\"AA180C3702\",15^m"
waitfor 5 "+CUSD:"
if % = -1 goto error
get 1 "^m" $s
print $s
exit 0
:error
print ""
exit 0

18 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

A co wg ciebie *108# miało robić? Bo wg tego co pokazałeś to jest jakieś menu do usług w play a nie bezpośrednia odpowiedź.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

19 Odpowiedź przez whiteindian (edytowany przez whiteindian 2016-02-13 16:47:26)

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Pod windowsem play pod tym kodem zwraca poprawnie ile pozostało danych.

20 Odpowiedź przez whiteindian (edytowany przez whiteindian 2016-02-17 09:41:26)

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Podłączam chyba na temat: dwa modemy z harmonogramem.

Modem1: Huawei E3131s2 bez HiLink - dzienny z Aero2
Modem2: Huawei E398 - nocny z Plus (1:00 - 7:00)

Modem2 ma byc cały dzień wyłączony, po godzinie 1:00 wyłącz/włącz i pobiera transmission 1:30; nad ranem 6:30 wyłącza się. Nie wiem czy wystarczy poradnik http://eko.one.pl/?p=openwrt-mwan3

21 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Nie, po prostu w cronie wyłącz jeden włącz drugi modem o określonej godzinie. Mwan3 do niczego ci nie jest potrzebny w tym przypadku.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

22 Odpowiedź przez whiteindian

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Nie będzie się gryzło ze skryptem automatycznego sprawdzania łącza?

23 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

To sobie odpowiednio zmienisz skrypt żeby raz sprawdzał to a raz inne łącze.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

24 Odpowiedź przez whiteindian (edytowany przez whiteindian 2016-02-25 09:09:49)

  • Skąd: Polska Centralna
  • Zarejestrowany: 2016-01-27
  • Posty: 172

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Czy mój Unitek Y-2143 to dobry hub, zwłaszcza że planowałem wpiąć aż dwa modemy?

25 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,075

Odp: WNDR4300 - QMI kłopoty z autopołączeniem i podniesieniem E398.

Tego nikt nie wie. Musisz kupić i przetestować.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona