FAQ o OpenWrt | Sprzedam różne routery | Oddam

andrzej.k · 2017-06-16 15:11:45

andrzej.k
Użytkownik
Nieaktywny

Skąd: Zduńska Wola
Zarejestrowany: 2017-06-16
Posty: 44

Temat: Połączenie modemu w trybie bridge do routera z LEDE

Witam,

przełączyłem swój modem Huawei E5186s-22a pracujący w sieci PLAY w tryb pracy bridge mode. Modem zgodnie z instrukcją z tej strony: https://torba.quora.com/Replacing-firmw … LTE-router
podłączyłem do portu lan/wan, a na routerze (NETGEAR r7800 z LEDE z Luci najnowszy obraz od Cezarego) do portu wan. W LEDE interfejs WAN ustawiony jest na klienta DHCP. Widzę, że router otrzymuje z serwera DHCP PLAY swój numer ip, numer ip bramy, numery ip DNSów itp. Swój komputer podłączony mam testowo kabelkiem do portu lan routera. Nic nie wychodzi poza moją sieć lan, pingi np do 8.8.8.8 czy uzyskanej z DHCP bramy operatora nie przechodzą. Co robię źle? LEDE mam zresetowane do ustawień fabrycznych, które w mojej ocenie powinny działać (dawać dostęp do internetu poprzez modem w trybie bridge).

Kiedy modem pracuje w trybie routera czyli gdy mam podwójny NAT wszystko działa. Chciałbym pozbyć się podwójnego NAT, ale coś mi nie idzie.
Z góry dziękuję za pomoc.

Moja sieć domowa: LTE-A od PLAY -> Huawei B715 + antena ALL-ANT L4G MIMO -> Netgear R7800 (OpenWrt 18.06-SNAPSHOT od Cezarego) -> Netgear S8000 -> 2 x D-Link GO-SW-8G -> Netgear EX7300 -> Netgear WN3100RPv2 -> QNAP TS-251+ (2 x 4TB WD RED, RAID 1) -> APC Back BX700U-FR
Pozdrawiam!

Cezary · 2017-06-16 15:22:22

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 115,839

Odp: Połączenie modemu w trybie bridge do routera z LEDE

pokaż

uci show network
uci show firewall
ifconfig
logread

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

andrzej.k · 2017-06-16 15:31:49

andrzej.k
Użytkownik
Nieaktywny

Skąd: Zduńska Wola
Zarejestrowany: 2017-06-16
Posty: 44

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Dziękuję za szybką odpowiedź. Tak jak napisałem wcześniej LEDE testowo mam zresetowane do ustawień fabrycznych. Jeżeli uda mi się zmusić router do pracy z modemem ustawionym w tryb bridge, to zmodyfikuję swoją konfigurację, którą trzymam w bezpiecznym miejscu.

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='fd75:1818:2ad9::/48'
network.lan=interface
network.lan.type='bridge'
network.lan.ifname='eth1'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.wan=interface
network.wan.ifname='eth0'
network.wan.proto='dhcp'
network.wan6=interface
network.wan6.ifname='eth0'
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='1 2 3 4 6'
network.@switch_vlan[1]=switch_vlan
network.@switch_vlan[1].device='switch0'
network.@switch_vlan[1].vlan='2'
network.@switch_vlan[1].ports='5 0'

uci show firewall:

firewall.@defaults[0]=defaults
firewall.@defaults[0].syn_flood='1'
firewall.@defaults[0].input='ACCEPT'
firewall.@defaults[0].output='ACCEPT'
firewall.@defaults[0].forward='REJECT'
firewall.@zone[0]=zone
firewall.@zone[0].name='lan'
firewall.@zone[0].network='lan'
firewall.@zone[0].input='ACCEPT'
firewall.@zone[0].output='ACCEPT'
firewall.@zone[0].forward='ACCEPT'
firewall.@zone[1]=zone
firewall.@zone[1].name='wan'
firewall.@zone[1].network='wan' 'wan6'
firewall.@zone[1].input='REJECT'
firewall.@zone[1].output='ACCEPT'
firewall.@zone[1].forward='REJECT'
firewall.@zone[1].masq='1'
firewall.@zone[1].mtu_fix='1'
firewall.@forwarding[0]=forwarding
firewall.@forwarding[0].src='lan'
firewall.@forwarding[0].dest='wan'
firewall.@rule[0]=rule
firewall.@rule[0].name='Allow-DHCP-Renew'
firewall.@rule[0].src='wan'
firewall.@rule[0].proto='udp'
firewall.@rule[0].dest_port='68'
firewall.@rule[0].target='ACCEPT'
firewall.@rule[0].family='ipv4'
firewall.@rule[1]=rule
firewall.@rule[1].name='Allow-Ping'
firewall.@rule[1].src='wan'
firewall.@rule[1].proto='icmp'
firewall.@rule[1].icmp_type='echo-request'
firewall.@rule[1].family='ipv4'
firewall.@rule[1].target='ACCEPT'
firewall.@rule[2]=rule
firewall.@rule[2].name='Allow-IGMP'
firewall.@rule[2].src='wan'
firewall.@rule[2].proto='igmp'
firewall.@rule[2].family='ipv4'
firewall.@rule[2].target='ACCEPT'
firewall.@rule[3]=rule
firewall.@rule[3].name='Allow-DHCPv6'
firewall.@rule[3].src='wan'
firewall.@rule[3].proto='udp'
firewall.@rule[3].src_ip='fc00::/6'
firewall.@rule[3].dest_ip='fc00::/6'
firewall.@rule[3].dest_port='546'
firewall.@rule[3].family='ipv6'
firewall.@rule[3].target='ACCEPT'
firewall.@rule[4]=rule
firewall.@rule[4].name='Allow-MLD'
firewall.@rule[4].src='wan'
firewall.@rule[4].proto='icmp'
firewall.@rule[4].src_ip='fe80::/10'
firewall.@rule[4].icmp_type='130/0' '131/0' '132/0' '143/0'
firewall.@rule[4].family='ipv6'
firewall.@rule[4].target='ACCEPT'
firewall.@rule[5]=rule
firewall.@rule[5].name='Allow-ICMPv6-Input'
firewall.@rule[5].src='wan'
firewall.@rule[5].proto='icmp'
firewall.@rule[5].icmp_type='echo-request' 'echo-reply' 'destination-unreachable' 'packet-too-big' 'time-exceeded' 'bad-header' 'unknown-header-type' 'router-solicitation' 'neighbour-solicitation' 'router-advertisement' 'neighbour-advertisement'
firewall.@rule[5].limit='1000/sec'
firewall.@rule[5].family='ipv6'
firewall.@rule[5].target='ACCEPT'
firewall.@rule[6]=rule
firewall.@rule[6].name='Allow-ICMPv6-Forward'
firewall.@rule[6].src='wan'
firewall.@rule[6].dest='*'
firewall.@rule[6].proto='icmp'
firewall.@rule[6].icmp_type='echo-request' 'echo-reply' 'destination-unreachable' 'packet-too-big' 'time-exceeded' 'bad-header' 'unknown-header-type'
firewall.@rule[6].limit='1000/sec'
firewall.@rule[6].family='ipv6'
firewall.@rule[6].target='ACCEPT'
firewall.@rule[7]=rule
firewall.@rule[7].name='Allow-IPSec-ESP'
firewall.@rule[7].src='wan'
firewall.@rule[7].dest='lan'
firewall.@rule[7].proto='esp'
firewall.@rule[7].target='ACCEPT'
firewall.@rule[8]=rule
firewall.@rule[8].name='Allow-ISAKMP'
firewall.@rule[8].src='wan'
firewall.@rule[8].dest='lan'
firewall.@rule[8].dest_port='500'
firewall.@rule[8].proto='udp'
firewall.@rule[8].target='ACCEPT'
firewall.@include[0]=include
firewall.@include[0].path='/etc/firewall.user'

ifconfig:

br-lan    Link encap:Ethernet  HWaddr B0:7F:B9:F8:20:93
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::b27f:b9ff:fef8:2093/64 Scope:Link
          inet6 addr: fd75:1818:2ad9::1/60 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5360 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1397 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:571291 (557.9 KiB)  TX bytes:474961 (463.8 KiB)

eth0      Link encap:Ethernet  HWaddr B0:7F:B9:F8:20:94
          inet addr:10.76.0.153  Bcast:10.76.0.155  Mask:255.255.255.252
          inet6 addr: fe80::b27f:b9ff:fef8:2094/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3905 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2500 (2.4 KiB)  TX bytes:308327 (301.1 KiB)
          Interrupt:30

eth1      Link encap:Ethernet  HWaddr B0:7F:B9:F8:20:93
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5460 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1480 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:654804 (639.4 KiB)  TX bytes:482142 (470.8 KiB)
          Interrupt:31

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:510 errors:0 dropped:0 overruns:0 frame:0
          TX packets:510 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:33668 (32.8 KiB)  TX bytes:33668 (32.8 KiB)

logread:

Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Booting Linux on physical CPU 0x0
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000] Linux version 4.4.71 (cezary@eko.one.pl) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3101-bce140e) ) #0 SMP Thu Jun 8 21:02:37 2017
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5787d
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Machine model: Netgear Nighthawk X4S R7800
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Memory policy: Data cache writealloc
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.000000] On node 0 totalpages: 122880
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat c07ed480, node_mem_map dda39000
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.000000]   Normal zone: 960 pages used for memmap
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.000000]   Normal zone: 122880 pages, LIFO batch:31
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] PERCPU: Embedded 11 pages/cpu @dda0c000 s13824 r8192 d23040 u45056
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.000000] pcpu-alloc: s13824 r8192 d23040 u45056 alloc=11*4096
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 121920
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000] Kernel command line:
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000] Bootloader command line (ignored): console=ttyHSL1,115200n8
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Memory: 478496K/491520K available (4249K kernel code, 246K rwdata, 1544K rodata, 220K init, 227K bss, 13024K reserved, 0K cma-reserved, 0K highmem)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000] Virtual kernel memory layout:
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]     vmalloc : 0xde800000 - 0xff800000   ( 528 MB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xde000000   ( 480 MB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]       .text : 0xc0208000 - 0xc07b0738   (5794 kB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]       .init : 0xc07b1000 - 0xc07e8000   ( 220 kB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]       .data : 0xc07e8000 - 0xc0825a40   ( 247 kB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    0.000000]        .bss : 0xc0828000 - 0xc0860f40   ( 228 kB)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] Hierarchical RCU implementation.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000]     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] NR_IRQS:16 nr_irqs:16 16
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000000] clocksource: dg_timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 305801671480 ns
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000007] sched_clock: 32 bits at 6MHz, resolution 160ns, wraps every 343597383600ns
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000023] Switching to timer-based delay loop, resolution 160ns
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000209] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.50 BogoMIPS (lpj=62500)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000231] pid_max: default: 32768 minimum: 301
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000340] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000355] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.000972] CPU: Testing write buffer coherency: ok
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.001314] Setting up static identity map for 0x42208280 - 0x422082d8
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.004358] Brought up 2 CPUs
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.004377] SMP: Total of 2 processors activated (25.00 BogoMIPS).
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.004388] CPU: All CPU(s) started in SVC mode.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.015029] VFP support v0.3: implementor 51 architecture 64 part 4d variant 2 rev 0
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.015259] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.015300] futex hash table entries: 512 (order: 3, 32768 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.015469] pinctrl core: initialized pinctrl subsystem
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.016870] NET: Registered protocol family 16
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.018123] DMA: preallocated 2048 KiB pool for atomic coherent allocations
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.041452] cpuidle: using governor ladder
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.072467] cpuidle: using governor menu
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.087769] qcom_rpm 108000.rpm: RPM firmware 3.0.16777364
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.127014] pps_core: LinuxPPS API ver. 1 registered
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.127031] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.127071] PTP clock support registered
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.128253] clocksource: Switched to clocksource dg_timer
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.130156] NET: Registered protocol family 2
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.130715] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.130755] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.130807] TCP: Hash tables configured (established 4096 bind 4096)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.130854] UDP hash table entries: 256 (order: 1, 8192 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.130876] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.131068] NET: Registered protocol family 1
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.131131] PCI: CLS 0 bytes, default 64
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    0.132458] No memory allocated for crashlog
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.139763] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.139785] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.142484] io scheduler noop registered
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.142506] io scheduler deadline registered (default)
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    0.144014] 1b500000.pci supply vdda not found, using dummy regulator
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    0.144104] 1b500000.pci supply vdda_phy not found, using dummy regulator
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    0.144181] 1b500000.pci supply vdda_refclk not found, using dummy regulator
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.144659] PCI host bridge /soc/pci@1b500000 ranges:
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.144694]    IO 0x0fe00000..0x0fefffff -> 0x0fe00000
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.144716]   MEM 0x08000000..0x0fdfffff -> 0x08000000
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.165454] qcom-pcie 1b500000.pci: PCI host bridge to bus 0000:00
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.165476] pci_bus 0000:00: root bus resource [bus 00-ff]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.165495] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfe00000-0xfefffff])
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.165510] pci_bus 0000:00: root bus resource [mem 0x08000000-0x0fdfffff]
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.165525] pci_bus 0000:00: scanning bus
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.165572] pci 0000:00:00.0: [17cb:0101] type 01 class 0x060400
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.165676] pci 0000:00:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.165729] pci 0000:00:00.0: supports D1
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.165742] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.165759] pci 0000:00:00.0: PME# disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.165996] pci_bus 0000:00: fixups for bus
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.166020] PCI: bus0: Fast back to back transfers disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.166038] pci 0000:00:00.0: scanning [bus 01-01] behind bridge, pass 0
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.166173] pci_bus 0000:01: scanning bus
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.166316] pci 0000:01:00.0: [168c:0046] type 00 class 0x028000
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.166630] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.166994] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167370] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167407] pci 0000:01:00.0: PME# disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167709] pci_bus 0000:01: fixups for bus
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.167771] PCI: bus1: Fast back to back transfers disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167785] pci_bus 0000:01: bus scan returning with max=01
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167804] pci 0000:00:00.0: scanning [bus 01-01] behind bridge, pass 1
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167823] pci_bus 0000:00: bus scan returning with max=01
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167897] pci 0000:00:00.0: fixup irq: got 135
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167910] pci 0000:00:00.0: assigning IRQ 135
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167975] pci 0000:01:00.0: fixup irq: got 135
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.167988] pci 0000:01:00.0: assigning IRQ 135
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.168049] pci 0000:00:00.0: BAR 8: assigned [mem 0x08000000-0x081fffff]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.168071] pci 0000:01:00.0: BAR 0: assigned [mem 0x08000000-0x081fffff 64bit]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.168173] pci 0000:00:00.0: PCI bridge to [bus 01]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.168194] pci 0000:00:00.0:   bridge window [mem 0x08000000-0x081fffff]
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.168630] aer 0000:00:00.0:pcie02: service driver aer loaded
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    0.168956] 1b700000.pci supply vdda not found, using dummy regulator
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    0.169055] 1b700000.pci supply vdda_phy not found, using dummy regulator
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    0.169129] 1b700000.pci supply vdda_refclk not found, using dummy regulator
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.169605] PCI host bridge /soc/pci@1b700000 ranges:
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.169637]    IO 0x31e00000..0x31efffff -> 0x31e00000
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.169656]   MEM 0x2e000000..0x31dfffff -> 0x2e000000
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.204077] qcom-pcie 1b700000.pci: PCI host bridge to bus 0001:00
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.204095] pci_bus 0001:00: root bus resource [bus 00-ff]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.204109] pci_bus 0001:00: root bus resource [mem 0x2e000000-0x31dfffff]
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204121] pci_bus 0001:00: scanning bus
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204161] pci 0001:00:00.0: [17cb:0101] type 01 class 0x060400
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204248] pci 0001:00:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204294] pci 0001:00:00.0: supports D1
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204307] pci 0001:00:00.0: PME# supported from D0 D1 D3hot
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204324] pci 0001:00:00.0: PME# disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204557] pci_bus 0001:00: fixups for bus
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.204577] PCI: bus0: Fast back to back transfers disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204594] pci 0001:00:00.0: scanning [bus 01-01] behind bridge, pass 0
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204723] pci_bus 0001:01: scanning bus
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.204865] pci 0001:01:00.0: [168c:0046] type 00 class 0x028000
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.205175] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.205537] pci 0001:01:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.205912] pci 0001:01:00.0: PME# supported from D0 D3hot D3cold
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.205950] pci 0001:01:00.0: PME# disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206243] pci_bus 0001:01: fixups for bus
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.206304] PCI: bus1: Fast back to back transfers disabled
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206318] pci_bus 0001:01: bus scan returning with max=01
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206336] pci 0001:00:00.0: scanning [bus 01-01] behind bridge, pass 1
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206354] pci_bus 0001:00: bus scan returning with max=01
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206403] pcieport 0000:00:00.0: fixup irq: got 135
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206416] pcieport 0000:00:00.0: assigning IRQ 135
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206480] pci 0000:01:00.0: fixup irq: got 135
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206492] pci 0000:01:00.0: assigning IRQ 135
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206565] pci 0001:00:00.0: fixup irq: got 168
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206578] pci 0001:00:00.0: assigning IRQ 168
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206640] pci 0001:01:00.0: fixup irq: got 168
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.206652] pci 0001:01:00.0: assigning IRQ 168
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.206705] pci 0001:00:00.0: BAR 8: assigned [mem 0x2e000000-0x2e1fffff]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.206727] pci 0001:01:00.0: BAR 0: assigned [mem 0x2e000000-0x2e1fffff 64bit]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.206827] pci 0001:00:00.0: PCI bridge to [bus 01]
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.206844] pci 0001:00:00.0:   bridge window [mem 0x2e000000-0x2e1fffff]
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    0.207200] aer 0001:00:00.0:pcie02: service driver aer loaded
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.210877] gsbi 16300000.gsbi: GSBI port protocol: 6 crci: 0
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.211959] gsbi 1a200000.gsbi: GSBI port protocol: 3 crci: 0
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.213068] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.215811] msm_serial 16340000.serial: msm_serial: detected port #0
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.215924] msm_serial 16340000.serial: uartclk = 1843200
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.215989] 16340000.serial: ttyMSM0 at MMIO 0x16340000 (irq = 169, base_baud = 115200) is a MSM
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.216028] msm_serial: console setup on port #0
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.855501] console [ttyMSM0] enabled
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.860279] msm_serial: driver initialized
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.870960] loop: module loaded
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.872860] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xa1
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.872907] nand: AMD/Spansion S34MS01G2
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.879576] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Thu Jun  8 23:02:43 2017 kern.info kernel: [    0.883419] Scanning device for bad blocks
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.216809] random: nonblocking pool is initialized
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.524233] 9 ofpart partitions found on MTD device qcom-nandc
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.524259] Creating 9 MTD partitions on "qcom-nandc":
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.529037] 0x000000000000-0x000000c80000 : "qcadata"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.535211] 0x000000c80000-0x000001180000 : "APPSBL"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.540313] 0x000001180000-0x000001200000 : "APPSBLENV"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.545287] 0x000001200000-0x000001340000 : "art"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.550323] 0x000001340000-0x000001480000 : "artbak"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.555063] 0x000001480000-0x000001680000 : "kernel"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.560223] 0x000001680000-0x000007900000 : "ubi"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.565195] 0x000007900000-0x000008000000 : "reserve"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    1.569751] 0x000001480000-0x000007900000 : "firmware"
Thu Jun  8 23:02:43 2017 kern.info kernel: [    1.576772] no rootfs found after FIT image in "firmware"
Thu Jun  8 23:02:43 2017 kern.info kernel: [    1.579460] spi_qup 1a280000.spi: IN:block:16, fifo:64, OUT:block:16, fifo:64
Thu Jun  8 23:02:43 2017 kern.err kernel: [    1.585314] m25p80 spi32766.0: unrecognized JEDEC id bytes: 00,  0,  0
Thu Jun  8 23:02:43 2017 kern.warn kernel: [    1.591390] m25p80: probe of spi32766.0 failed with error -2
Thu Jun  8 23:02:43 2017 kern.info kernel: [    1.598268] libphy: Fixed MDIO Bus: probed
Thu Jun  8 23:02:43 2017 kern.info kernel: [    1.603996] libphy: GPIO Bitbanged MDIO: probed
Thu Jun  8 23:02:43 2017 kern.info kernel: [    1.629425] switch0: Atheros AR8337 rev. 2 switch registered on gpio-0
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.439029] stmmac - user ID: 0x10, Synopsys ID: 0x37
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.439055]  Ring mode enabled
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.443053]  DMA HW capability register supported
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.446005]  Enhanced/Alternate descriptors
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.450779]     Enabled extended descriptors
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.454772]  RX Checksum Offload Engine supported (type 2)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.458998]  TX Checksum insertion supported
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.464320]  Wake-Up On Lan supported
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.468808]  Enable RX Mitigation via HW Watchdog Timer
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.473604] stmmac - user ID: 0x10, Synopsys ID: 0x37
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.477342]  Ring mode enabled
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.482629]  DMA HW capability register supported
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.485502]  Enhanced/Alternate descriptors
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.490274]     Enabled extended descriptors
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.494268]  RX Checksum Offload Engine supported (type 2)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.498436]  TX Checksum insertion supported
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.503888]  Wake-Up On Lan supported
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.508242]  Enable RX Mitigation via HW Watchdog Timer
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.512534] i2c /dev entries driver
Thu Jun  8 23:02:43 2017 kern.err kernel: [    2.517490] gcc-ipq806x 900000.clock-controller: tsens calibration failed
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.521198] Speed bin: 0
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.527253] PVS bin: 4
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    2.530403] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    2.532068] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.539463] sdhci: Secure Digital Host Controller Interface driver
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.546528] sdhci: Copyright(c) Pierre Ossman
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.552852] sdhci-pltfm: SDHCI platform and OF driver helper
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.559254] L2 @ QSB rate. Forcing new rate.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.563042] L2 @ 384000 KHz
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.567308] CPU0 @ 800000 KHz
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.569779] CPU1 @ QSB rate. Forcing new rate.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.572903] CPU1 @ 384000 KHz
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.579212] NET: Registered protocol family 10
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.581413] NET: Registered protocol family 17
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.584618] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    2.589429] 8021q: 802.1Q VLAN Support v1.8
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    2.601924] Registering SWP/SWPB emulation handler
Thu Jun  8 23:02:43 2017 kern.err kernel: [    2.610231] cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
Thu Jun  8 23:02:43 2017 kern.err kernel: [    2.611623] cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:1, -19
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    2.620520] UBI: auto-attach mtd6
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    2.626832] ubi0: attaching mtd6
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.087752] ubi0: scanning is finished
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.103859] ubi0: attached mtd6 (name "ubi", size 98 MiB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.103890] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.108237] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.115114] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.121936] ubi0: good PEBs: 788, bad PEBs: 0, corrupted PEBs: 0
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.128716] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.134889] ubi0: max/mean erase counter: 14/9, WL threshold: 4096, image sequence number: 909942278
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.142000] ubi0: available PEBs: 0, total reserved PEBs: 788, PEBs reserved for bad PEB handling: 20
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.151393] ubi0: background thread "ubi_bgt0d" started, PID 61
Thu Jun  8 23:02:43 2017 kern.info kernel: [    4.161458] block ubiblock0_0: created from ubi0:0(rootfs)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    4.166044] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
Thu Jun  8 23:02:43 2017 kern.info kernel: [    4.171678] hctosys: unable to open rtc device (rtc0)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    4.188337] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    4.188517] Freeing unused kernel memory: 220K (c07b1000 - c07e8000)
Thu Jun  8 23:02:43 2017 user.info kernel: [    4.672346] init: Console is alive
Thu Jun  8 23:02:43 2017 user.info kernel: [    4.672474] init: - watchdog -
Thu Jun  8 23:02:43 2017 user.info kernel: [    5.370006] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.404235] usbcore: registered new interface driver usbfs
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.404302] usbcore: registered new interface driver hub
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.408742] usbcore: registered new device driver usb
Thu Jun  8 23:02:43 2017 kern.notice kernel: [    5.423824] SCSI subsystem initialized
Thu Jun  8 23:02:43 2017 kern.debug kernel: [    5.426427] libata version 3.00 loaded.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.428652] ahci 29000000.sata: forcing port_map 0x0 -> 0x1
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.428698] ahci 29000000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.433025] ahci 29000000.sata: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.442871] scsi host0: ahci
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.450083] ata1: SATA max UDMA/133 mmio [mem 0x29000000-0x2900017f] port 0x100 irq 26
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.798636] ata1: SATA link down (SStatus 0 SControl 300)
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.800316] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.803414] ehci-platform: EHCI generic platform driver
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.811915] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.814981] ohci-platform: OHCI generic platform driver
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.918153] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.918206] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.922798] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x00010010
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.930218] xhci-hcd xhci-hcd.0.auto: irq 171, io mem 0x11000000
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.940025] hub 1-0:1.0: USB hub found
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.945084] hub 1-0:1.0: 1 port detected
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.949081] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.952668] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.958121] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.966505] hub 2-0:1.0: USB hub found
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.973975] hub 2-0:1.0: 1 port detected
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.977889] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.981595] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.986988] xhci-hcd xhci-hcd.1.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x00010010
Thu Jun  8 23:02:43 2017 kern.info kernel: [    5.994462] xhci-hcd xhci-hcd.1.auto: irq 172, io mem 0x10000000
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.004017] hub 3-0:1.0: USB hub found
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.009402] hub 3-0:1.0: 1 port detected
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.013207] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.016902] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.022426] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.030670] hub 4-0:1.0: USB hub found
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.038126] hub 4-0:1.0: 1 port detected
Thu Jun  8 23:02:43 2017 kern.info kernel: [    6.044465] usbcore: registered new interface driver usb-storage
Thu Jun  8 23:02:43 2017 user.info kernel: [    6.045776] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Thu Jun  8 23:02:43 2017 user.info kernel: [    6.061755] init: - preinit -
Thu Jun  8 23:02:43 2017 kern.info kernel: [    9.638711] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Thu Jun  8 23:02:43 2017 user.info kernel: [   10.760643] mount_root: loading kmods from internal overlay
Thu Jun  8 23:02:43 2017 user.info kernel: [   10.776280] kmodloader: loading kernel modules from //etc/modules-boot.d/*
Thu Jun  8 23:02:43 2017 user.info kernel: [   10.777568] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.786590] blk_update_request: I/O error, dev mtdblock0, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.789764] blk_update_request: I/O error, dev mtdblock0, sector 8
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.795922] blk_update_request: I/O error, dev mtdblock0, sector 16
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.802278] blk_update_request: I/O error, dev mtdblock0, sector 24
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.808351] blk_update_request: I/O error, dev mtdblock0, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.814074] Buffer I/O error on dev mtdblock0, logical block 0, async page read
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.821806] blk_update_request: I/O error, dev mtdblock1, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.827951] blk_update_request: I/O error, dev mtdblock1, sector 8
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.834332] blk_update_request: I/O error, dev mtdblock1, sector 16
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.840470] blk_update_request: I/O error, dev mtdblock1, sector 24
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.846578] blk_update_request: I/O error, dev mtdblock1, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.852354] Buffer I/O error on dev mtdblock1, logical block 0, async page read
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.242315] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 150
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.332136] UBIFS (ubi0:1): recovery needed
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.527097] UBIFS (ubi0:1): recovery completed
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.527188] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.530508] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.538357] UBIFS (ubi0:1): FS size: 89899008 bytes (85 MiB, 708 LEBs), journal size 4444160 bytes (4 MiB, 35 LEBs)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.548320] UBIFS (ubi0:1): reserved for root: 4246152 bytes (4146 KiB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.558465] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID 98C283B3-CC04-444B-8843-88FADFEA8521, small LPT model
Thu Jun  8 23:02:43 2017 user.info kernel: [   11.566567] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Thu Jun  8 23:02:43 2017 user.err kernel: [   11.576660] block: unable to load configuration (fstab: Entry not found)
Thu Jun  8 23:02:43 2017 user.info kernel: [   11.583393] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
Thu Jun  8 23:02:43 2017 user.err kernel: [   11.590351] block: unable to load configuration (fstab: Entry not found)
Thu Jun  8 23:02:43 2017 user.info kernel: [   11.596603] block: attempting to load /etc/config/fstab
Thu Jun  8 23:02:43 2017 user.err kernel: [   11.604038] block: unable to load configuration (fstab: Entry not found)
Thu Jun  8 23:02:43 2017 user.err kernel: [   11.608320] block: no usable configuration
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.648720] UBIFS (ubi0:1): un-mount UBI device 0
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.648751] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.656894] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 151
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.820462] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.820494] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.827276] UBIFS (ubi0:1): FS size: 89899008 bytes (85 MiB, 708 LEBs), journal size 4444160 bytes (4 MiB, 35 LEBs)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.837251] UBIFS (ubi0:1): reserved for root: 4246152 bytes (4146 KiB)
Thu Jun  8 23:02:43 2017 kern.notice kernel: [   11.847473] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID 98C283B3-CC04-444B-8843-88FADFEA8521, small LPT model
Thu Jun  8 23:02:43 2017 kern.err kernel: [   11.862095] Buffer I/O error on dev mtdblock0, logical block 0, async page read
Thu Jun  8 23:02:43 2017 kern.err kernel: [   11.867838] Buffer I/O error on dev mtdblock1, logical block 0, async page read
Thu Jun  8 23:02:43 2017 user.info kernel: [   12.220890] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Thu Jun  8 23:02:43 2017 user.err kernel: [   12.221121] block: unable to load configuration (fstab: Entry not found)
Thu Jun  8 23:02:43 2017 user.info kernel: [   12.226793] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
Thu Jun  8 23:02:43 2017 user.err kernel: [   12.234006] block: unable to load configuration (fstab: Entry not found)
Thu Jun  8 23:02:43 2017 user.info kernel: [   12.240493] block: attempting to load /etc/config/fstab
Thu Jun  8 23:02:43 2017 user.err kernel: [   12.246822] block: unable to load configuration (fstab: Entry not found)
Thu Jun  8 23:02:43 2017 user.err kernel: [   12.251845] block: no usable configuration
Thu Jun  8 23:02:43 2017 user.info kernel: [   12.290717] mount_root: overlay filesystem has not been fully initialized yet
Thu Jun  8 23:02:43 2017 user.info kernel: [   12.297289] mount_root: switching to ubifs overlay
Thu Jun  8 23:02:43 2017 user.warn kernel: [   12.308268] urandom-seed: Seed file not found (/etc/urandom.seed)
Thu Jun  8 23:02:43 2017 user.info kernel: [   12.375492] procd: - early -
Thu Jun  8 23:02:43 2017 user.info kernel: [   12.375595] procd: - watchdog -
Thu Jun  8 23:02:43 2017 user.info kernel: [   13.031099] procd: - ubus -
Thu Jun  8 23:02:43 2017 user.info kernel: [   13.197254] procd: - init -
Thu Jun  8 23:02:43 2017 user.info kernel: [   13.303416] kmodloader: loading kernel modules from /etc/modules.d/*
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.308308] tun: Universal TUN/TAP device driver, 1.6
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.308984] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.316971] ip6_tables: (C) 2000-2006 Netfilter Core Team
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.323844] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.325323] Backport generated by backports.git backports-20160324-13-g24da7d3c
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.349234] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   13.349309] ath10k_pci 0000:01:00.0: enabling bus mastering
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.349744] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   13.480689] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   13.480721] ath10k_pci 0000:01:00.0: Falling back to user helper
Thu Jun  8 23:02:43 2017 kern.err kernel: [   13.506818] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   13.506976] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   13.514747] ath10k_pci 0000:01:00.0: Falling back to user helper
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.969275] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.969310] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.980283] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.4-00072 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast crc32 75ec955f
Thu Jun  8 23:02:43 2017 kern.err kernel: [   13.996900] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0046,subsystem-vendor=168c,subsystem-device=cafe��=D��q����̻.����
                                                                     n, from ath10k/QCA9984/hw1.0/board-2.bin
Thu Jun  8 23:02:43 2017 kern.info kernel: [   13.999970] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 9dbf1af5
Thu Jun  8 23:02:43 2017 kern.info kernel: [   15.351173] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal file max-sta 512 raw 0 hwcrypto 1
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   15.424973] ath: EEPROM regdomain: 0x0
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   15.424988] ath: EEPROM indicates default country code should be used
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   15.425000] ath: doing EEPROM country->regdmn map search
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   15.425014] ath: country maps to regdmn code: 0x3a
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   15.425026] ath: Country alpha2 being used: US
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   15.425036] ath: Regpair used: 0x3a
Thu Jun  8 23:02:43 2017 kern.info kernel: [   15.430600] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   15.430716] ath10k_pci 0001:01:00.0: enabling bus mastering
Thu Jun  8 23:02:43 2017 kern.info kernel: [   15.431245] ath10k_pci 0001:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   15.570466] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:01:00.0.bin failed with error -2
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   15.570540] ath10k_pci 0001:01:00.0: Falling back to user helper
Thu Jun  8 23:02:43 2017 kern.err kernel: [   15.741850] firmware ath10k!pre-cal-pci-0001:01:00.0.bin: firmware_loading_store: map pages failed
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   15.742094] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/cal-pci-0001:01:00.0.bin failed with error -2
Thu Jun  8 23:02:43 2017 kern.warn kernel: [   15.749821] ath10k_pci 0001:01:00.0: Falling back to user helper
Thu Jun  8 23:02:43 2017 kern.info kernel: [   15.975081] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
Thu Jun  8 23:02:43 2017 kern.info kernel: [   15.975120] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Thu Jun  8 23:02:43 2017 kern.info kernel: [   15.987119] ath10k_pci 0001:01:00.0: firmware ver 10.4-3.4-00072 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast crc32 75ec955f
Thu Jun  8 23:02:43 2017 kern.err kernel: [   15.992656] ath10k_pci 0001:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0046,subsystem-vendor=168c,subsystem-device=cafe from ath10k/QCA9984/hw1.0/board-2.bin
Thu Jun  8 23:02:43 2017 kern.info kernel: [   16.005708] ath10k_pci 0001:01:00.0: board_file api 1 bmi_id N/A crc32 9dbf1af5
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.361248] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal file max-sta 512 raw 0 hwcrypto 1
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   17.435016] ath: EEPROM regdomain: 0x0
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   17.435032] ath: EEPROM indicates default country code should be used
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   17.435043] ath: doing EEPROM country->regdmn map search
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   17.435059] ath: country maps to regdmn code: 0x3a
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   17.435070] ath: Country alpha2 being used: US
Thu Jun  8 23:02:43 2017 kern.debug kernel: [   17.435080] ath: Regpair used: 0x3a
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.550311] u32 classifier
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.550330]     input device check on
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.551901]     Actions configured
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.556627] Mirror/redirect action on
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.562837] nf_conntrack version 0.5.0 (7479 buckets, 29916 max)
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.566595] fuse init (API version 7.23)
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.572485] usbcore: registered new interface driver cdc_acm
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.572653] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.579419] usbcore: registered new interface driver cdc_wdm
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.589026] ip_tables: (C) 2000-2006 Netfilter Core Team
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.734050] usbcore: registered new interface driver usblp
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.737685] usbcore: registered new interface driver usbserial
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.738469] usbcore: registered new interface driver usbserial_generic
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.744351] usbserial: USB Serial support registered for generic
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.774304] xt_time: kernel timezone is -0000
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.776121] usbcore: registered new interface driver cdc_ether
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.780540] usbcore: registered new interface driver cdc_ncm
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.785460] usbcore: registered new interface driver huawei_cdc_ncm
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.811538] PPP generic driver version 2.4.2
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.813719] NET: Registered protocol family 24
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.817685] usbcore: registered new interface driver qmi_wwan
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.822609] usbcore: registered new interface driver rndis_host
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.828050] usbcore: registered new interface driver sierra
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.831011] usbserial: USB Serial support registered for Sierra USB modem
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.839221] usbcore: registered new interface driver sierra_net
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.845307] usbcore: registered new interface driver cdc_mbim
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.850164] usbcore: registered new interface driver option
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.854863] usbserial: USB Serial support registered for GSM modem (1-port)
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.862047] usbcore: registered new interface driver qcserial
Thu Jun  8 23:02:43 2017 kern.info kernel: [   17.867186] usbserial: USB Serial support registered for Qualcomm USB modem
Thu Jun  8 23:02:43 2017 user.info kernel: [   17.873198] kmodloader: done loading kernel modules from /etc/modules.d/*
Thu Jun  8 23:02:45 2017 user.notice : Added device handler type: tunnel
Thu Jun  8 23:02:45 2017 user.notice : Added device handler type: Network device
Thu Jun  8 23:02:45 2017 user.notice : Added device handler type: bridge
Thu Jun  8 23:02:45 2017 user.notice : Added device handler type: macvlan
Thu Jun  8 23:02:45 2017 user.notice : Added device handler type: 8021ad
Thu Jun  8 23:02:45 2017 user.notice : Added device handler type: 8021q
Thu Jun  8 23:02:45 2017 user.notice : 'radio0' is disabled
Thu Jun  8 23:02:45 2017 user.notice : 'radio1' is disabled
Thu Jun  8 23:02:45 2017 user.notice : 'radio0' is disabled
Thu Jun  8 23:02:45 2017 user.notice : 'radio1' is disabled
Thu Jun  8 23:02:45 2017 kern.warn kernel: [   21.516584] blk_update_request: 10 callbacks suppressed
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.516608] blk_update_request: I/O error, dev mtdblock0, sector 0
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.521993] blk_update_request: I/O error, dev mtdblock0, sector 8
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.539969] blk_update_request: I/O error, dev mtdblock0, sector 16
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.540440] blk_update_request: I/O error, dev mtdblock0, sector 24
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.551546] blk_update_request: I/O error, dev mtdblock0, sector 0
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.551579] Buffer I/O error on dev mtdblock0, logical block 0, async page read
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.558130] blk_update_request: I/O error, dev mtdblock1, sector 0
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.565247] blk_update_request: I/O error, dev mtdblock1, sector 8
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.571508] blk_update_request: I/O error, dev mtdblock1, sector 16
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.577575] blk_update_request: I/O error, dev mtdblock1, sector 24
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.583833] blk_update_request: I/O error, dev mtdblock1, sector 0
Thu Jun  8 23:02:45 2017 kern.err kernel: [   21.589569] Buffer I/O error on dev mtdblock1, logical block 0, async page read
Thu Jun  8 23:02:45 2017 daemon.err block: /dev/ubiblock0_0 is already mounted on /rom
Thu Jun  8 23:02:45 2017 daemon.err block: /dev/ubi0_1 is already mounted on /overlay
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'lan' is enabled
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'lan' is setting up now
Thu Jun  8 23:02:46 2017 kern.info kernel: [   22.429756] device eth1 entered promiscuous mode
Thu Jun  8 23:02:46 2017 kern.info kernel: [   22.431610] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'lan' is now up
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'loopback' is enabled
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'loopback' is now up
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'wan' is enabled
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'wan6' is enabled
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Network device 'lo' link is up
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Network device 'eth0' link is up
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'wan' has link connectivity
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jun  8 23:02:46 2017 daemon.info odhcpd[898]: Raising SIGUSR1 due to address change on br-lan
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Jun  8 23:02:46 2017 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Jun  8 23:02:46 2017 daemon.notice netifd: wan (1020): udhcpc: started, v1.25.1
Thu Jun  8 23:02:46 2017 daemon.notice netifd: wan (1020): udhcpc: sending discover
Thu Jun  8 23:02:46 2017 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Jun  8 23:02:46 2017 user.notice : 4+0 records in
Thu Jun  8 23:02:46 2017 user.notice : 4+0 records out
Thu Jun  8 23:02:46 2017 daemon.err odhcp6c[1033]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
Thu Jun  8 23:02:47 2017 user.notice : Generating a 2048 bit RSA private key
Thu Jun  8 23:02:47 2017 daemon.info odhcpd[898]: Using a RA lifetime of 0 seconds on br-lan
Thu Jun  8 23:02:47 2017 daemon.notice odhcpd[898]: Failed to send to ff02::1%br-lan (Address not available)
Thu Jun  8 23:02:47 2017 user.notice : .............................+++
Thu Jun  8 23:02:47 2017 user.notice : ..............+++
Thu Jun  8 23:02:47 2017 user.notice : writing new private key to '/etc/uhttpd.key.new'
Thu Jun  8 23:02:47 2017 user.notice : -----
Thu Jun  8 23:02:47 2017 user.notice : setting up led USB 1
Thu Jun  8 23:02:47 2017 user.notice : setting up led USB 2
Thu Jun  8 23:02:48 2017 user.notice : setting up led WAN
Thu Jun  8 23:02:48 2017 user.notice : setting up led eSATA
Thu Jun  8 23:02:48 2017 daemon.notice netifd: Network device 'eth1' link is up
Thu Jun  8 23:02:48 2017 kern.info kernel: [   24.398646] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Thu Jun  8 23:02:48 2017 kern.info kernel: [   24.398709] br-lan: port 1(eth1) entered forwarding state
Thu Jun  8 23:02:48 2017 kern.info kernel: [   24.406539] br-lan: port 1(eth1) entered forwarding state
Thu Jun  8 23:02:48 2017 daemon.notice netifd: bridge 'br-lan' link is up
Thu Jun  8 23:02:48 2017 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Jun  8 23:02:48 2017 daemon.info procd: - init complete -
Thu Jun  8 23:02:48 2017 kern.info kernel: [   24.435007] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Thu Jun  8 23:02:48 2017 kern.info kernel: [   24.456582] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Thu Jun  8 23:02:48 2017 daemon.info urandom_seed[1326]: Seed saved (/etc/urandom.seed)
Thu Jun  8 23:02:49 2017 daemon.info odhcpd[898]: Using a RA lifetime of 0 seconds on br-lan
Thu Jun  8 23:02:49 2017 daemon.notice odhcpd[898]: Failed to send to ff02::1%br-lan (Address not available)
Thu Jun  8 23:02:49 2017 daemon.notice netifd: wan (1020): udhcpc: sending discover
Thu Jun  8 23:02:50 2017 kern.info kernel: [   26.398856] br-lan: port 1(eth1) entered forwarding state
Thu Jun  8 23:02:51 2017 authpriv.info dropbear[1471]: Not backgrounding
Thu Jun  8 23:02:52 2017 daemon.notice netifd: wan (1020): udhcpc: sending discover
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: started, version 2.77 cachesize 150
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: DNS service limited to local subnets
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: 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 no-ID loop-detect inotify
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq-dhcp[1541]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: using local addresses only for domain lan
Thu Jun  8 23:02:53 2017 daemon.warn dnsmasq[1541]: no servers found in /tmp/resolv.conf.auto, will retry
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: read /etc/hosts - 4 addresses
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: read /tmp/hosts/odhcpd - 0 addresses
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq-dhcp[1541]: read /etc/ethers - 0 addresses
Thu Jun  8 23:02:53 2017 daemon.notice netifd: wan (1020): udhcpc: sending select for 10.76.0.153
Thu Jun  8 23:02:53 2017 daemon.notice netifd: wan (1020): udhcpc: lease of 10.76.0.153 obtained, lease time 300
Thu Jun  8 23:02:53 2017 daemon.notice netifd: Interface 'wan' is now up
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: reading /tmp/resolv.conf.auto
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: using local addresses only for domain lan
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: using nameserver 89.108.195.20#53
Thu Jun  8 23:02:53 2017 daemon.info dnsmasq[1541]: using nameserver 185.89.185.1#53
Thu Jun  8 23:02:54 2017 daemon.info odhcpd[898]: Using a RA lifetime of 0 seconds on br-lan
Thu Jun  8 23:02:54 2017 daemon.info dnsmasq-dhcp[1541]: DHCPINFORM(br-lan) 192.168.1.182 70:5a:b6:5a:b6:64
Thu Jun  8 23:02:54 2017 daemon.info dnsmasq-dhcp[1541]: DHCPACK(br-lan) 192.168.1.182 70:5a:b6:5a:b6:64 Tolek-Komputer
Thu Jun  8 23:02:54 2017 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Thu Jun  8 23:02:55 2017 user.notice ddns-scripts[1651]: myddns_ipv4: PID '1651' started at 2017-06-08 23:02
Thu Jun  8 23:02:55 2017 user.warn ddns-scripts[1651]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Jun  8 23:02:55 2017 user.warn ddns-scripts[1651]: myddns_ipv4: PID '1651' exit WITH ERROR '1' at 2017-06-08 23:02
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq-dhcp[1541]: DHCPDISCOVER(br-lan) a8:60:b6:0f:11:63
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq-dhcp[1541]: DHCPOFFER(br-lan) 192.168.1.119 a8:60:b6:0f:11:63
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1541]: exiting on receipt of SIGTERM
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: started, version 2.77 cachesize 150
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: DNS service limited to local subnets
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: 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 no-ID loop-detect inotify
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq-dhcp[1780]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: using local addresses only for domain lan
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: reading /tmp/resolv.conf.auto
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: using local addresses only for domain lan
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: using nameserver 89.108.195.20#53
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: using nameserver 185.89.185.1#53
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: read /etc/hosts - 4 addresses
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: read /tmp/hosts/odhcpd - 0 addresses
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq[1780]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Thu Jun  8 23:02:59 2017 daemon.info dnsmasq-dhcp[1780]: read /etc/ethers - 0 addresses
Thu Jun  8 23:03:00 2017 daemon.info dnsmasq-dhcp[1780]: DHCPREQUEST(br-lan) 192.168.1.119 a8:60:b6:0f:11:63
Thu Jun  8 23:03:00 2017 daemon.info dnsmasq-dhcp[1780]: DHCPACK(br-lan) 192.168.1.119 a8:60:b6:0f:11:63 MBP-Andrzej
Thu Jun  8 23:03:02 2017 kern.info kernel: [   38.525833] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Thu Jun  8 23:05:23 2017 daemon.notice netifd: wan (1020): udhcpc: sending renew
Thu Jun  8 23:05:23 2017 daemon.notice netifd: wan (1020): udhcpc: lease of 10.76.0.153 obtained, lease time 300
Thu Jun  8 23:07:21 2017 authpriv.info dropbear[2233]: Child connection from 192.168.1.119:52623
Thu Jun  8 23:07:22 2017 authpriv.info dropbear[2233]: Exit before auth: Exited normally
Thu Jun  8 23:07:40 2017 daemon.info dnsmasq-dhcp[1780]: DHCPDISCOVER(br-lan) 02:0f:b5:28:28:a9
Thu Jun  8 23:07:40 2017 daemon.info dnsmasq-dhcp[1780]: DHCPOFFER(br-lan) 192.168.1.193 02:0f:b5:28:28:a9
Thu Jun  8 23:07:41 2017 authpriv.info dropbear[2564]: Child connection from 192.168.1.119:52624
Thu Jun  8 23:07:41 2017 authpriv.info dropbear[2564]: Exit before auth: Exited normally
Thu Jun  8 23:07:44 2017 daemon.info odhcpd[898]: Using a RA lifetime of 0 seconds on br-lan
Thu Jun  8 23:07:53 2017 daemon.notice netifd: wan (1020): udhcpc: sending renew
Thu Jun  8 23:07:53 2017 daemon.notice netifd: wan (1020): udhcpc: lease of 10.76.0.153 obtained, lease time 300
Thu Jun  8 23:08:19 2017 authpriv.info dropbear[3221]: Child connection from 192.168.1.119:52625
Thu Jun  8 23:08:22 2017 authpriv.notice dropbear[3221]: Auth succeeded with blank password for 'root' from 192.168.1.119:52625

Moja sieć domowa: LTE-A od PLAY -> Huawei B715 + antena ALL-ANT L4G MIMO -> Netgear R7800 (OpenWrt 18.06-SNAPSHOT od Cezarego) -> Netgear S8000 -> 2 x D-Link GO-SW-8G -> Netgear EX7300 -> Netgear WN3100RPv2 -> QNAP TS-251+ (2 x 4TB WD RED, RAID 1) -> APC Back BX700U-FR
Pozdrawiam!

Cezary · 2017-06-17 06:34:40

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 115,839

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Adres jest, dnsy są. SIM ma jakiś pin?

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

andrzej.k · 2017-06-17 09:25:12

andrzej.k
Użytkownik
Nieaktywny

Skąd: Zduńska Wola
Zarejestrowany: 2017-06-16
Posty: 44

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Nie, nie ma. Karta nie ma ustawionego kodu pin, a przynajmniej nigdy takiego nie podawałem. Gdy modem nie jest w trybie bridge to działa. Mogę żyć z tym podwójnym NATem - wyłączam wtedy na modemie serwer DHCP ustawiam DMZ na router itp., ale wydaje mi się to średnio właściwe dlatego dążę do pozbycia się NATu w modemie.

Podczas testów z trybem bridge modemu, zauważyłem, że po dłuższej pracy routera, na interfejsie WAN TX jest znacząco wyższy od RX, RX w zasadzie nic nie odbiera.

Pozdrawiam.

Moja sieć domowa: LTE-A od PLAY -> Huawei B715 + antena ALL-ANT L4G MIMO -> Netgear R7800 (OpenWrt 18.06-SNAPSHOT od Cezarego) -> Netgear S8000 -> 2 x D-Link GO-SW-8G -> Netgear EX7300 -> Netgear WN3100RPv2 -> QNAP TS-251+ (2 x 4TB WD RED, RAID 1) -> APC Back BX700U-FR
Pozdrawiam!

Cezary · 2017-06-17 09:43:13

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 115,839

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Nie, nie ma problemów z podwójnym natem - możesz używać czegoś takiego, ideologicznie w niczym Ci to nie przeszkadza.

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

andrzej.k · 2017-06-17 10:24:14

andrzej.k
Użytkownik
Nieaktywny

Skąd: Zduńska Wola
Zarejestrowany: 2017-06-16
Posty: 44

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Dziękuję za odpowiedź.
Nie będę już zakładać nowego tematu, chciałbym jeszcze zapytać o te błędy:

Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.786590] blk_update_request: I/O error, dev mtdblock0, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.789764] blk_update_request: I/O error, dev mtdblock0, sector 8
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.795922] blk_update_request: I/O error, dev mtdblock0, sector 16
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.802278] blk_update_request: I/O error, dev mtdblock0, sector 24
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.808351] blk_update_request: I/O error, dev mtdblock0, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.814074] Buffer I/O error on dev mtdblock0, logical block 0, async page read
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.821806] blk_update_request: I/O error, dev mtdblock1, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.827951] blk_update_request: I/O error, dev mtdblock1, sector 8
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.834332] blk_update_request: I/O error, dev mtdblock1, sector 16
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.840470] blk_update_request: I/O error, dev mtdblock1, sector 24
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.846578] blk_update_request: I/O error, dev mtdblock1, sector 0
Thu Jun  8 23:02:43 2017 kern.err kernel: [   10.852354] Buffer I/O error on dev mtdblock1, logical block 0, async page read

Możecie coś więcej powiedzieć na ich temat? To coś poważnego? Błędy na partycji? Pojawiają się na wszystkich kompilacjach LEDE, które do tej pory używałem z R7800. Z tego co widzę pojawiają się tylko podczas startu systemu. Pomimo tych błędów system startuje i działa prawidłowo.

Moja sieć domowa: LTE-A od PLAY -> Huawei B715 + antena ALL-ANT L4G MIMO -> Netgear R7800 (OpenWrt 18.06-SNAPSHOT od Cezarego) -> Netgear S8000 -> 2 x D-Link GO-SW-8G -> Netgear EX7300 -> Netgear WN3100RPv2 -> QNAP TS-251+ (2 x 4TB WD RED, RAID 1) -> APC Back BX700U-FR
Pozdrawiam!

Cezary · 2017-06-17 10:30:05

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 115,839

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Błędy systemu plików na partycji, tak. Czy jest mtdblock1? u ciebie?

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

andrzej.k · 2017-06-17 13:20:53

andrzej.k
Użytkownik
Nieaktywny

Skąd: Zduńska Wola
Zarejestrowany: 2017-06-16
Posty: 44

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Nie wiem o co dokładnie pytasz. Ja nic przy systemach plików, partycjach, exroot itp nie robiłem. Nigdy nawet nie podłączałem do routera żadnej pamięci usb czy esata. Jeśli chodzi o partycje, to wszystko jest domyślnie z Twoich obrazów.

Moja sieć domowa: LTE-A od PLAY -> Huawei B715 + antena ALL-ANT L4G MIMO -> Netgear R7800 (OpenWrt 18.06-SNAPSHOT od Cezarego) -> Netgear S8000 -> 2 x D-Link GO-SW-8G -> Netgear EX7300 -> Netgear WN3100RPv2 -> QNAP TS-251+ (2 x 4TB WD RED, RAID 1) -> APC Back BX700U-FR
Pozdrawiam!

Cezary · 2017-06-17 13:32:30

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 115,839

Odp: Połączenie modemu w trybie bridge do routera z LEDE

cat /proc/mtd pokaż

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

andrzej.k · 2017-06-17 17:10:51

andrzej.k
Użytkownik
Nieaktywny

Skąd: Zduńska Wola
Zarejestrowany: 2017-06-16
Posty: 44

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Czyli co do połączenia z modemem w trybie bridge nie widać rozwiązania? Zostawiam tak jak jest na podwójnym NATcie i się nie przejmuję. Dziękuję za zainteresowanie w tym temacie.

cat /proc/mtd:

dev:    size   erasesize  name
mtd0: 00c80000 00020000 "qcadata"
mtd1: 00500000 00020000 "APPSBL"
mtd2: 00080000 00020000 "APPSBLENV"
mtd3: 00140000 00020000 "art"
mtd4: 00140000 00020000 "artbak"
mtd5: 00200000 00020000 "kernel"
mtd6: 06280000 00020000 "ubi"
mtd7: 00700000 00020000 "reserve"
mtd8: 06480000 00020000 "firmware"

Moja sieć domowa: LTE-A od PLAY -> Huawei B715 + antena ALL-ANT L4G MIMO -> Netgear R7800 (OpenWrt 18.06-SNAPSHOT od Cezarego) -> Netgear S8000 -> 2 x D-Link GO-SW-8G -> Netgear EX7300 -> Netgear WN3100RPv2 -> QNAP TS-251+ (2 x 4TB WD RED, RAID 1) -> APC Back BX700U-FR
Pozdrawiam!

Cezary · 2017-06-17 17:15:07

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 115,839

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Ciekawe że nie może tego odczytać. Na razie zignoruj, lede i tak nie korzysta z tych partycji.

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

andrzej.k · 2017-06-17 17:19:35

andrzej.k
Użytkownik
Nieaktywny

Skąd: Zduńska Wola
Zarejestrowany: 2017-06-16
Posty: 44

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Chodzi o mtd0 i mtd1? Możesz napisać do czego są przewidziane te partycje oraz pozostałe? Tak jak mówiłem oprócz historii z modem w trybie bridge to router działa wzorowo przy moich zastosowaniach na Twoich obrazach. Przed Twoimi obrazami używałem oryginalnego obrazu LEDE gdzie partycja na programy była mała, a potem zaktualizowałem do Twoich obrazów z nieoficjalnym wsparciem większej partycji na dane. Może tu leży przyczyna?

Moja sieć domowa: LTE-A od PLAY -> Huawei B715 + antena ALL-ANT L4G MIMO -> Netgear R7800 (OpenWrt 18.06-SNAPSHOT od Cezarego) -> Netgear S8000 -> 2 x D-Link GO-SW-8G -> Netgear EX7300 -> Netgear WN3100RPv2 -> QNAP TS-251+ (2 x 4TB WD RED, RAID 1) -> APC Back BX700U-FR
Pozdrawiam!

Cezary · 2017-06-17 17:22:11

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 115,839

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Oryginalny soft do czego wykorzystuje te partycje. Do czego - nie wiem, tu już się do producenta zgłoś.

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

FAQ o OpenWrt | Sprzedam różne routery | Oddam

Połączenie modemu w trybie bridge do routera z LEDE

Posty: 14

1 Temat przez andrzej.k 2017-06-16 15:11:45 (edytowany przez andrzej.k 2017-06-16 16:00:21)

Temat: Połączenie modemu w trybie bridge do routera z LEDE

2 Odpowiedź przez Cezary 2017-06-16 15:22:22

Odp: Połączenie modemu w trybie bridge do routera z LEDE

3 Odpowiedź przez andrzej.k 2017-06-16 15:31:49 (edytowany przez andrzej.k 2017-06-16 15:34:10)

Odp: Połączenie modemu w trybie bridge do routera z LEDE

4 Odpowiedź przez Cezary 2017-06-17 06:34:40

Odp: Połączenie modemu w trybie bridge do routera z LEDE

5 Odpowiedź przez andrzej.k 2017-06-17 09:25:12 (edytowany przez andrzej.k 2017-06-17 09:26:05)

Odp: Połączenie modemu w trybie bridge do routera z LEDE

6 Odpowiedź przez Cezary 2017-06-17 09:43:13

Odp: Połączenie modemu w trybie bridge do routera z LEDE

7 Odpowiedź przez andrzej.k 2017-06-17 10:24:14 (edytowany przez andrzej.k 2017-06-17 10:24:43)

Odp: Połączenie modemu w trybie bridge do routera z LEDE

8 Odpowiedź przez Cezary 2017-06-17 10:30:05

Odp: Połączenie modemu w trybie bridge do routera z LEDE

9 Odpowiedź przez andrzej.k 2017-06-17 13:20:53

Odp: Połączenie modemu w trybie bridge do routera z LEDE

10 Odpowiedź przez Cezary 2017-06-17 13:32:30

Odp: Połączenie modemu w trybie bridge do routera z LEDE

11 Odpowiedź przez andrzej.k 2017-06-17 17:10:51 (edytowany przez andrzej.k 2017-06-17 17:13:48)

Odp: Połączenie modemu w trybie bridge do routera z LEDE

12 Odpowiedź przez Cezary 2017-06-17 17:15:07

Odp: Połączenie modemu w trybie bridge do routera z LEDE

13 Odpowiedź przez andrzej.k 2017-06-17 17:19:35

Odp: Połączenie modemu w trybie bridge do routera z LEDE

14 Odpowiedź przez Cezary 2017-06-17 17:22:11

Odp: Połączenie modemu w trybie bridge do routera z LEDE

Posty: 14