• Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Temat: ZyXEL Armor Z2 - NBG6817

W końcu wróciłem do domu i wziąłem się za router. Niestety napotkałem już pierwszy problem sad Router ma teoretycznie 4 GB pamięci eMMC ale pierwszym zalogowaniu moim oczom ukazał się taki oto przykry widok.

login as: root


BusyBox v1.28.3 () built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------------------------------
 |                                                                           |
 | OpenWrt 18.06-SNAPSHOT, r6984-fa0275b                                     |
 |                                                                           |
 | Build time: 2018-05-30 18:32 CEST                                         |
 | Cezary Jackiewicz (obsy), http://eko.one.pl                               |
 |                                                                           |
 -----------------------------------------------------------------------------
 | Machine: ZyXEL NBG6817                                                    |
 | Uptime: 0d, 00:03:27                                                      |
 | Load: 0.18 0.26 0.11                                                      |
 | Flash: total: 52.9MB, free: 47.5MB, used: 3%                              |
 | Memory: total: 468.2MB, free: 433.8MB, used: 7%                           |
 | WAN:                                                                      |
 | LAN: 192.168.1.1, leases: 1                                               |
 -----------------------------------------------------------------------------

Niestety do 4 GB sporo brakuje.

Logi:

Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] Booting Linux on physical CPU 0x0
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000] Linux version 4.14.43 (cezary@eko.one.pl) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r6984-fa0275b)) #0 SMP Thu May 24 15:24:31 2018
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5787d
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] CPU: div instructions available: patching division code
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] OF: fdt: Machine model: ZyXEL NBG6817
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] Memory policy: Data cache writealloc
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.000000] On node 0 totalpages: 122880
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat c0b27b00, node_mem_map ddc39000
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.000000]   Normal zone: 960 pages used for memmap
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.000000]   Normal zone: 122880 pages, LIFO batch:31
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x88/0x40c with crng_init=0
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] percpu: Embedded 15 pages/cpu @ddc03000 s29324 r8192 d23924 u61440
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.000000] pcpu-alloc: s29324 r8192 d23924 u61440 alloc=15*4096
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 121920
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000] Kernel command line: rootfstype=squashfs,ext4 rootwait noinitrd root=/dev/mmcblk0p5
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000] Bootloader command line (ignored): board=NBG6817 root=/dev/mmcblk0p5 rootwait zld_ver=2.05 console=ttyHSL1,115200n8 mtdparts=m25p80:0xC0000(SBL)ro,0x40000(TZ)ro,0x40000(RPM)ro,0x80000(u-boot)ro,0x10000(env)ro,0x10000(ART)ro,0x10000(dualflag),0x210000(reserved)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] Memory: 478392K/491520K available (4867K kernel code, 161K rwdata, 1284K rodata, 1024K init, 251K bss, 13128K reserved, 0K cma-reserved, 0K highmem)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000] Virtual kernel memory layout:
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]     vmalloc : 0xde800000 - 0xff800000   ( 528 MB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xde000000   ( 480 MB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]       .text : 0xc0208000 - 0xc07c0e08   (5860 kB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]       .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]       .data : 0xc0b00000 - 0xc0b28400   ( 161 kB)
Thu May 24 17:25:34 2018 kern.notice kernel: [    0.000000]        .bss : 0xc0b2a000 - 0xc0b68c34   ( 252 kB)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] Hierarchical RCU implementation.
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000]     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000000] clocksource: dg_timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 305801671480 ns
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000006] sched_clock: 32 bits at 6MHz, resolution 160ns, wraps every 343597383600ns
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000018] Switching to timer-based delay loop, resolution 160ns
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000195] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.50 BogoMIPS (lpj=62500)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000215] pid_max: default: 32768 minimum: 301
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000325] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000341] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.000800] CPU: Testing write buffer coherency: ok
Thu May 24 17:25:34 2018 kern.info kernel: [    0.001472] Setting up static identity map for 0x42300000 - 0x42300060
Thu May 24 17:25:34 2018 kern.info kernel: [    0.001608] Hierarchical SRCU implementation.
Thu May 24 17:25:34 2018 kern.info kernel: [    0.002272] smp: Bringing up secondary CPUs ...
Thu May 24 17:25:34 2018 kern.info kernel: [    0.003960] smp: Brought up 1 node, 2 CPUs
Thu May 24 17:25:34 2018 kern.info kernel: [    0.003973] SMP: Total of 2 processors activated (25.00 BogoMIPS).
Thu May 24 17:25:34 2018 kern.info kernel: [    0.003982] CPU: All CPU(s) started in SVC mode.
Thu May 24 17:25:34 2018 kern.info kernel: [    0.013314] VFP support v0.3: implementor 51 architecture 64 part 4d variant 2 rev 0
Thu May 24 17:25:34 2018 kern.info kernel: [    0.013451] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Thu May 24 17:25:34 2018 kern.info kernel: [    0.013473] futex hash table entries: 512 (order: 3, 32768 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.013577] pinctrl core: initialized pinctrl subsystem
Thu May 24 17:25:34 2018 kern.info kernel: [    0.014445] NET: Registered protocol family 16
Thu May 24 17:25:34 2018 kern.info kernel: [    0.014722] DMA: preallocated 256 KiB pool for atomic coherent allocations
Thu May 24 17:25:34 2018 kern.info kernel: [    0.015916] cpuidle: using governor ladder
Thu May 24 17:25:34 2018 kern.info kernel: [    0.015975] cpuidle: using governor menu
Thu May 24 17:25:34 2018 kern.err kernel: [    0.036395] msm_bus_fabric_init_driver
Thu May 24 17:25:34 2018 kern.info kernel: [    0.037605] usbcore: registered new interface driver usbfs
Thu May 24 17:25:34 2018 kern.info kernel: [    0.037679] usbcore: registered new interface driver hub
Thu May 24 17:25:34 2018 kern.info kernel: [    0.037758] usbcore: registered new device driver usb
Thu May 24 17:25:34 2018 kern.info kernel: [    0.037816] pps_core: LinuxPPS API ver. 1 registered
Thu May 24 17:25:34 2018 kern.info kernel: [    0.037827] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Thu May 24 17:25:34 2018 kern.info kernel: [    0.037857] PTP clock support registered
Thu May 24 17:25:34 2018 kern.info kernel: [    0.039364] clocksource: Switched to clocksource dg_timer
Thu May 24 17:25:34 2018 kern.info kernel: [    0.042391] NET: Registered protocol family 2
Thu May 24 17:25:34 2018 kern.info kernel: [    0.042941] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.042980] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.043032] TCP: Hash tables configured (established 4096 bind 4096)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.043112] UDP hash table entries: 256 (order: 1, 8192 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.043137] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
Thu May 24 17:25:34 2018 kern.info kernel: [    0.043305] NET: Registered protocol family 1
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.043348] PCI: CLS 0 bytes, default 64
Thu May 24 17:25:34 2018 kern.warn kernel: [    0.044407] No memory allocated for crashlog
Thu May 24 17:25:34 2018 kern.info kernel: [    0.044553] workingset: timestamp_bits=30 max_order=17 bucket_order=0
Thu May 24 17:25:34 2018 kern.info kernel: [    0.048670] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Thu May 24 17:25:34 2018 kern.info kernel: [    0.048683] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Thu May 24 17:25:34 2018 kern.info kernel: [    0.055239] io scheduler noop registered
Thu May 24 17:25:34 2018 kern.info kernel: [    0.055253] io scheduler deadline registered (default)
Thu May 24 17:25:34 2018 kern.warn kernel: [    0.056646] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda not found, using dummy regulator
Thu May 24 17:25:34 2018 kern.warn kernel: [    0.056740] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda_phy not found, using dummy regulator
Thu May 24 17:25:34 2018 kern.warn kernel: [    0.056819] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda_refclk not found, using dummy regulator
Thu May 24 17:25:34 2018 kern.info kernel: [    0.057535] OF: PCI: host bridge /soc/pci@1b500000 ranges:
Thu May 24 17:25:34 2018 kern.info kernel: [    0.057573] OF: PCI:    IO 0x0fe00000..0x0fefffff -> 0x0fe00000
Thu May 24 17:25:34 2018 kern.info kernel: [    0.057595] OF: PCI:   MEM 0x08000000..0x0fdfffff -> 0x08000000
Thu May 24 17:25:34 2018 kern.info kernel: [    0.165059] qcom-pcie 1b500000.pci: link up
Thu May 24 17:25:34 2018 kern.info kernel: [    0.165198] qcom-pcie 1b500000.pci: PCI host bridge to bus 0000:00
Thu May 24 17:25:34 2018 kern.info kernel: [    0.165218] pci_bus 0000:00: root bus resource [bus 00-ff]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.165234] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfe00000-0xfefffff])
Thu May 24 17:25:34 2018 kern.info kernel: [    0.165248] pci_bus 0000:00: root bus resource [mem 0x08000000-0x0fdfffff]
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165262] pci_bus 0000:00: scanning bus
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165303] pci 0000:00:00.0: [17cb:0101] type 01 class 0x060400
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165387] pci 0000:00:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165448] pci 0000:00:00.0: supports D1
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165458] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165470] pci 0000:00:00.0: PME# disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165692] pci_bus 0000:00: fixups for bus
Thu May 24 17:25:34 2018 kern.info kernel: [    0.165711] PCI: bus0: Fast back to back transfers disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165729] pci 0000:00:00.0: scanning [bus 01-ff] behind bridge, pass 0
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.165839] pci_bus 0000:01: scanning bus
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.166014] pci 0000:01:00.0: [168c:0046] type 00 class 0x028000
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.166360] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.166827] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.167468] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.167508] pci 0000:01:00.0: PME# disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.167819] pci_bus 0000:01: fixups for bus
Thu May 24 17:25:34 2018 kern.info kernel: [    0.167890] PCI: bus1: Fast back to back transfers disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.167904] pci_bus 0000:01: bus scan returning with max=01
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.167919] pci 0000:00:00.0: scanning [bus 01-ff] behind bridge, pass 1
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.167935] pci_bus 0000:00: bus scan returning with max=ff
Thu May 24 17:25:34 2018 kern.info kernel: [    0.167977] pci 0000:00:00.0: BAR 8: assigned [mem 0x08000000-0x081fffff]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.167999] pci 0000:01:00.0: BAR 0: assigned [mem 0x08000000-0x081fffff 64bit]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.168123] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.168143] pci 0000:00:00.0:   bridge window [mem 0x08000000-0x081fffff]
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.168176] pci 0000:00:00.0: calling qcom_pcie_fixup_final+0x0/0x94
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.168339] pcieport 0000:00:00.0: assign IRQ: got 67
Thu May 24 17:25:34 2018 kern.info kernel: [    0.168620] pcieport 0000:00:00.0: AER enabled with IRQ 35
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.168731] pci 0000:01:00.0: calling qcom_pcie_fixup_final+0x0/0x94
Thu May 24 17:25:34 2018 kern.warn kernel: [    0.169105] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda not found, using dummy regulator
Thu May 24 17:25:34 2018 kern.warn kernel: [    0.169206] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda_phy not found, using dummy regulator
Thu May 24 17:25:34 2018 kern.warn kernel: [    0.169285] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda_refclk not found, using dummy regulator
Thu May 24 17:25:34 2018 kern.info kernel: [    0.170085] OF: PCI: host bridge /soc/pci@1b700000 ranges:
Thu May 24 17:25:34 2018 kern.info kernel: [    0.170120] OF: PCI:    IO 0x31e00000..0x31efffff -> 0x31e00000
Thu May 24 17:25:34 2018 kern.info kernel: [    0.170141] OF: PCI:   MEM 0x2e000000..0x31dfffff -> 0x2e000000
Thu May 24 17:25:34 2018 kern.info kernel: [    0.279928] qcom-pcie 1b700000.pci: link up
Thu May 24 17:25:34 2018 kern.info kernel: [    0.280065] qcom-pcie 1b700000.pci: PCI host bridge to bus 0001:00
Thu May 24 17:25:34 2018 kern.info kernel: [    0.280084] pci_bus 0001:00: root bus resource [bus 00-ff]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.280097] pci_bus 0001:00: root bus resource [mem 0x2e000000-0x31dfffff]
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280110] pci_bus 0001:00: scanning bus
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280148] pci 0001:00:00.0: [17cb:0101] type 01 class 0x060400
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280222] pci 0001:00:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280282] pci 0001:00:00.0: supports D1
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280291] pci 0001:00:00.0: PME# supported from D0 D1 D3hot
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280303] pci 0001:00:00.0: PME# disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280510] pci_bus 0001:00: fixups for bus
Thu May 24 17:25:34 2018 kern.info kernel: [    0.280529] PCI: bus0: Fast back to back transfers disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280546] pci 0001:00:00.0: scanning [bus 01-ff] behind bridge, pass 0
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280663] pci_bus 0001:01: scanning bus
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.280848] pci 0001:01:00.0: [168c:0046] type 00 class 0x028000
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.281218] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.281719] pci 0001:01:00.0: calling pci_fixup_ide_bases+0x0/0x44
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.282408] pci 0001:01:00.0: PME# supported from D0 D3hot D3cold
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.282450] pci 0001:01:00.0: PME# disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.282766] pci_bus 0001:01: fixups for bus
Thu May 24 17:25:34 2018 kern.info kernel: [    0.282841] PCI: bus1: Fast back to back transfers disabled
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.282856] pci_bus 0001:01: bus scan returning with max=01
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.282871] pci 0001:00:00.0: scanning [bus 01-ff] behind bridge, pass 1
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.282887] pci_bus 0001:00: bus scan returning with max=ff
Thu May 24 17:25:34 2018 kern.info kernel: [    0.282922] pci 0001:00:00.0: BAR 8: assigned [mem 0x2e000000-0x2e1fffff]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.282945] pci 0001:01:00.0: BAR 0: assigned [mem 0x2e000000-0x2e1fffff 64bit]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.283075] pci 0001:00:00.0: PCI bridge to [bus 01-ff]
Thu May 24 17:25:34 2018 kern.info kernel: [    0.283094] pci 0001:00:00.0:   bridge window [mem 0x2e000000-0x2e1fffff]
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.283125] pci 0001:00:00.0: calling qcom_pcie_fixup_final+0x0/0x94
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.283289] pcieport 0001:00:00.0: assign IRQ: got 100
Thu May 24 17:25:34 2018 kern.info kernel: [    0.283563] pcieport 0001:00:00.0: AER enabled with IRQ 68
Thu May 24 17:25:34 2018 kern.debug kernel: [    0.283671] pci 0001:01:00.0: calling qcom_pcie_fixup_final+0x0/0x94
Thu May 24 17:25:34 2018 kern.info kernel: [    0.285666] L2 @ QSB rate. Forcing new rate.
Thu May 24 17:25:34 2018 kern.info kernel: [    0.285861] L2 @ 384000 KHz
Thu May 24 17:25:34 2018 kern.info kernel: [    0.286026] CPU0 @ 800000 KHz
Thu May 24 17:25:34 2018 kern.info kernel: [    0.286038] CPU1 @ QSB rate. Forcing new rate.
Thu May 24 17:25:34 2018 kern.info kernel: [    0.286153] CPU1 @ 384000 KHz
Thu May 24 17:25:34 2018 kern.info kernel: [    0.289815] gsbi 16300000.gsbi: GSBI port protocol: 6 crci: 0
Thu May 24 17:25:34 2018 kern.info kernel: [    0.291162] gsbi 1a200000.gsbi: GSBI port protocol: 3 crci: 0
Thu May 24 17:25:34 2018 kern.info kernel: [    0.292523] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Thu May 24 17:25:34 2018 kern.info kernel: [    0.294830] msm_serial 16340000.serial: msm_serial: detected port #0
Thu May 24 17:25:34 2018 kern.info kernel: [    0.294921] msm_serial 16340000.serial: uartclk = 7372800
Thu May 24 17:25:34 2018 kern.info kernel: [    0.294994] 16340000.serial: ttyMSM0 at MMIO 0x16340000 (irq = 101, base_baud = 460800) is a MSM
Thu May 24 17:25:34 2018 kern.info kernel: [    0.295027] msm_serial: console setup on port #0
Thu May 24 17:25:34 2018 kern.info kernel: [    1.056604] console [ttyMSM0] enabled
Thu May 24 17:25:34 2018 kern.info kernel: [    1.061356] msm_serial: driver initialized
Thu May 24 17:25:34 2018 kern.info kernel: [    1.069215] loop: module loaded
Thu May 24 17:25:34 2018 kern.info kernel: [    1.070582] spi_qup 1a280000.spi: IN:block:16, fifo:64, OUT:block:16, fifo:64
Thu May 24 17:25:34 2018 kern.info kernel: [    1.073109] m25p80 spi0.0: mx25u3235f (4096 Kbytes)
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.079034] 13 qcom-smem partitions found on MTD device spi0.0
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.083738] Creating 13 MTD partitions on "spi0.0":
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.089641] 0x000000000000-0x000000020000 : "0:SBL1"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.095056] 0x000000020000-0x000000040000 : "0:MIBIB"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.100254] 0x000000040000-0x000000060000 : "0:SBL2"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.105141] 0x000000060000-0x0000000a0000 : "0:SBL3"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.110258] 0x0000000a0000-0x0000000b0000 : "0:DDRCONFIG"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.115121] 0x0000000b0000-0x0000000c0000 : "0:SSD"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.120497] 0x0000000c0000-0x000000100000 : "0:TZ"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.125103] 0x000000100000-0x000000140000 : "0:RPM"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.130030] 0x000000140000-0x0000001c0000 : "0:APPSBL"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.134732] 0x0000001c0000-0x0000001d0000 : "0:APPSBLENV"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.140011] 0x0000001d0000-0x0000001e0000 : "0:ART"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.145411] 0x0000001e0000-0x0000001f0000 : "0:DUAL_FLAG"
Thu May 24 17:25:34 2018 kern.notice kernel: [    1.150185] 0x0000001f0000-0x000000400000 : "0:RESERVED"
Thu May 24 17:25:34 2018 kern.info kernel: [    1.156481] libphy: GPIO Bitbanged MDIO: probed
Thu May 24 17:25:34 2018 kern.info kernel: [    1.182072] switch0: Atheros AR8337 rev. 2 switch registered on gpio-0
Thu May 24 17:25:34 2018 kern.info kernel: [    2.069355] libphy: Fixed MDIO Bus: probed
Thu May 24 17:25:34 2018 kern.warn kernel: [    2.070818] ipq806x-gmac-dwmac 37200000.ethernet: PTP uses main clock
Thu May 24 17:25:34 2018 kern.info kernel: [    2.072612] stmmac - user ID: 0x10, Synopsys ID: 0x37
Thu May 24 17:25:34 2018 kern.info kernel: [    2.078856] ipq806x-gmac-dwmac 37200000.ethernet: Ring mode enabled
Thu May 24 17:25:34 2018 kern.info kernel: [    2.083982] ipq806x-gmac-dwmac 37200000.ethernet: DMA HW capability register supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.090050] ipq806x-gmac-dwmac 37200000.ethernet: Enhanced/Alternate descriptors
Thu May 24 17:25:34 2018 kern.info kernel: [    2.097953] ipq806x-gmac-dwmac 37200000.ethernet: Enabled extended descriptors
Thu May 24 17:25:34 2018 kern.info kernel: [    2.105592] ipq806x-gmac-dwmac 37200000.ethernet: RX Checksum Offload Engine supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.112622] ipq806x-gmac-dwmac 37200000.ethernet: COE Type 2
Thu May 24 17:25:34 2018 kern.info kernel: [    2.120493] ipq806x-gmac-dwmac 37200000.ethernet: TX Checksum insertion supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.126252] ipq806x-gmac-dwmac 37200000.ethernet: Wake-Up On Lan supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.133710] ipq806x-gmac-dwmac 37200000.ethernet: Enable RX Mitigation via HW Watchdog Timer
Thu May 24 17:25:34 2018 kern.warn kernel: [    2.141816] ipq806x-gmac-dwmac 37400000.ethernet: PTP uses main clock
Thu May 24 17:25:34 2018 kern.info kernel: [    2.149160] stmmac - user ID: 0x10, Synopsys ID: 0x37
Thu May 24 17:25:34 2018 kern.info kernel: [    2.155400] ipq806x-gmac-dwmac 37400000.ethernet: Ring mode enabled
Thu May 24 17:25:34 2018 kern.info kernel: [    2.160450] ipq806x-gmac-dwmac 37400000.ethernet: DMA HW capability register supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.166444] ipq806x-gmac-dwmac 37400000.ethernet: Enhanced/Alternate descriptors
Thu May 24 17:25:34 2018 kern.info kernel: [    2.174507] ipq806x-gmac-dwmac 37400000.ethernet: Enabled extended descriptors
Thu May 24 17:25:34 2018 kern.info kernel: [    2.182067] ipq806x-gmac-dwmac 37400000.ethernet: RX Checksum Offload Engine supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.189014] ipq806x-gmac-dwmac 37400000.ethernet: COE Type 2
Thu May 24 17:25:34 2018 kern.info kernel: [    2.196969] ipq806x-gmac-dwmac 37400000.ethernet: TX Checksum insertion supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.202811] ipq806x-gmac-dwmac 37400000.ethernet: Wake-Up On Lan supported
Thu May 24 17:25:34 2018 kern.info kernel: [    2.210184] ipq806x-gmac-dwmac 37400000.ethernet: Enable RX Mitigation via HW Watchdog Timer
Thu May 24 17:25:34 2018 kern.info kernel: [    2.217445] i2c /dev entries driver
Thu May 24 17:25:34 2018 kern.err kernel: [    2.226265] Calibration not found.
Thu May 24 17:25:34 2018 kern.err kernel: [    2.228678] qcom-tsens 900000.thermal-sensor: tsens calibration failed
Thu May 24 17:25:34 2018 kern.info kernel: [    2.233205] Speed bin: 0
Thu May 24 17:25:34 2018 kern.info kernel: [    2.238654] PVS bin: 5
Thu May 24 17:25:34 2018 kern.notice kernel: [    2.242522] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations
Thu May 24 17:25:34 2018 kern.notice kernel: [    2.243585] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations
Thu May 24 17:25:34 2018 kern.info kernel: [    2.251623] mmci-pl18x 12400000.sdcc: mmc0: PL180 manf 51 rev0 at 0x12400000 irq 34,0 (pio)
Thu May 24 17:25:34 2018 kern.info kernel: [    2.258179] mmci-pl18x 12400000.sdcc: DMA channels RX dma0chan1, TX dma0chan2
Thu May 24 17:25:34 2018 kern.info kernel: [    2.330342] sdhci: Secure Digital Host Controller Interface driver
Thu May 24 17:25:34 2018 kern.info kernel: [    2.330369] sdhci: Copyright(c) Pierre Ossman
Thu May 24 17:25:34 2018 kern.info kernel: [    2.335409] sdhci-pltfm: SDHCI platform and OF driver helper
Thu May 24 17:25:34 2018 kern.info kernel: [    2.341381] NET: Registered protocol family 10
Thu May 24 17:25:34 2018 kern.info kernel: [    2.347083] Segment Routing with IPv6
Thu May 24 17:25:34 2018 kern.info kernel: [    2.349963] NET: Registered protocol family 17
Thu May 24 17:25:34 2018 kern.info kernel: [    2.353603] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Thu May 24 17:25:34 2018 kern.info kernel: [    2.358338] 8021q: 802.1Q VLAN Support v1.8
Thu May 24 17:25:34 2018 kern.notice kernel: [    2.371148] Registering SWP/SWPB emulation handler
Thu May 24 17:25:34 2018 kern.info kernel: [    2.389115] qcom_rpm 108000.rpm: RPM firmware 3.0.16777364
Thu May 24 17:25:34 2018 kern.info kernel: [    2.403667] s1a: supplied by regulator-dummy
Thu May 24 17:25:34 2018 kern.info kernel: [    2.403759] s1a: Bringing 0uV into 1050000-1050000uV
Thu May 24 17:25:34 2018 kern.info kernel: [    2.407234] s1b: supplied by regulator-dummy
Thu May 24 17:25:34 2018 kern.info kernel: [    2.412084] s1b: Bringing 0uV into 1050000-1050000uV
Thu May 24 17:25:34 2018 kern.info kernel: [    2.416426] s2a: supplied by regulator-dummy
Thu May 24 17:25:34 2018 kern.info kernel: [    2.421267] s2a: Bringing 0uV into 775000-775000uV
Thu May 24 17:25:34 2018 kern.info kernel: [    2.425655] s2b: supplied by regulator-dummy
Thu May 24 17:25:34 2018 kern.info kernel: [    2.430129] s2b: Bringing 0uV into 775000-775000uV
Thu May 24 17:25:34 2018 kern.info kernel: [    2.438377] hctosys: unable to open rtc device (rtc0)
Thu May 24 17:25:34 2018 kern.info kernel: [    2.440009] Waiting for root device /dev/mmcblk0p5...
Thu May 24 17:25:34 2018 kern.info kernel: [    2.463616] mmc0: new high speed MMC card at address 0001
Thu May 24 17:25:34 2018 kern.info kernel: [    2.464156] mmcblk0: mmc0:0001 S10004 3.56 GiB
Thu May 24 17:25:34 2018 kern.info kernel: [    2.468279] mmcblk0boot0: mmc0:0001 S10004 partition 1 4.00 MiB
Thu May 24 17:25:34 2018 kern.info kernel: [    2.472674] mmcblk0boot1: mmc0:0001 S10004 partition 2 4.00 MiB
Thu May 24 17:25:34 2018 kern.info kernel: [    2.478491] mmcblk0rpmb: mmc0:0001 S10004 partition 3 4.00 MiB
Thu May 24 17:25:34 2018 kern.info kernel: [    2.486374]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
Thu May 24 17:25:34 2018 kern.info kernel: [    2.501683] VFS: Mounted root (squashfs filesystem) readonly on device 179:5.
Thu May 24 17:25:34 2018 kern.info kernel: [    2.502327] Freeing unused kernel memory: 1024K
Thu May 24 17:25:34 2018 kern.notice kernel: [    2.718285] random: fast init done
Thu May 24 17:25:34 2018 user.info kernel: [    2.769233] init: Console is alive
Thu May 24 17:25:34 2018 user.info kernel: [    2.769343] init: - watchdog -
Thu May 24 17:25:34 2018 user.info kernel: [    3.116696] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Thu May 24 17:25:34 2018 kern.info kernel: [    3.158305] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu May 24 17:25:34 2018 kern.notice kernel: [    3.160021] SCSI subsystem initialized
Thu May 24 17:25:34 2018 kern.debug kernel: [    3.165737] libata version 3.00 loaded.
Thu May 24 17:25:34 2018 kern.info kernel: [    3.168148] ehci-platform: EHCI generic platform driver
Thu May 24 17:25:34 2018 kern.info kernel: [    3.170308] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Thu May 24 17:25:34 2018 kern.info kernel: [    3.172915] ohci-platform: OHCI generic platform driver
Thu May 24 17:25:34 2018 kern.info kernel: [    3.308154] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
Thu May 24 17:25:34 2018 kern.info kernel: [    3.308232] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
Thu May 24 17:25:34 2018 kern.info kernel: [    3.312921] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x02010010
Thu May 24 17:25:34 2018 kern.info kernel: [    3.320256] xhci-hcd xhci-hcd.0.auto: irq 106, io mem 0x11000000
Thu May 24 17:25:34 2018 kern.info kernel: [    3.329376] hub 1-0:1.0: USB hub found
Thu May 24 17:25:34 2018 kern.info kernel: [    3.335170] hub 1-0:1.0: 1 port detected
Thu May 24 17:25:34 2018 kern.info kernel: [    3.338744] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
Thu May 24 17:25:34 2018 kern.info kernel: [    3.342735] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
Thu May 24 17:25:34 2018 kern.info kernel: [    3.348041] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Thu May 24 17:25:34 2018 kern.info kernel: [    3.355884] hub 2-0:1.0: USB hub found
Thu May 24 17:25:34 2018 kern.info kernel: [    3.363924] hub 2-0:1.0: 1 port detected
Thu May 24 17:25:34 2018 kern.info kernel: [    3.367602] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
Thu May 24 17:25:34 2018 kern.info kernel: [    3.371531] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
Thu May 24 17:25:34 2018 kern.info kernel: [    3.376897] xhci-hcd xhci-hcd.1.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x02010010
Thu May 24 17:25:34 2018 kern.info kernel: [    3.384420] xhci-hcd xhci-hcd.1.auto: irq 107, io mem 0x10000000
Thu May 24 17:25:34 2018 kern.info kernel: [    3.393420] hub 3-0:1.0: USB hub found
Thu May 24 17:25:34 2018 kern.info kernel: [    3.399272] hub 3-0:1.0: 1 port detected
Thu May 24 17:25:34 2018 kern.info kernel: [    3.403018] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
Thu May 24 17:25:34 2018 kern.info kernel: [    3.406894] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
Thu May 24 17:25:34 2018 kern.info kernel: [    3.412347] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Thu May 24 17:25:34 2018 kern.info kernel: [    3.420096] hub 4-0:1.0: USB hub found
Thu May 24 17:25:34 2018 kern.info kernel: [    3.428091] hub 4-0:1.0: 1 port detected
Thu May 24 17:25:34 2018 kern.info kernel: [    3.433678] usbcore: registered new interface driver usb-storage
Thu May 24 17:25:34 2018 kern.info kernel: [    3.436162] usbcore: registered new interface driver uas
Thu May 24 17:25:34 2018 user.info kernel: [    3.441904] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Thu May 24 17:25:34 2018 user.info kernel: [    3.453026] init: - preinit -
Thu May 24 17:25:34 2018 kern.notice kernel: [    3.698853] random: jshn: uninitialized urandom read (4 bytes read)
Thu May 24 17:25:34 2018 kern.notice kernel: [    3.753963] random: jshn: uninitialized urandom read (4 bytes read)
Thu May 24 17:25:34 2018 kern.notice kernel: [    3.954087] random: jshn: uninitialized urandom read (4 bytes read)
Thu May 24 17:25:34 2018 kern.info kernel: [    5.108800] ipq806x-gmac-dwmac 37400000.ethernet eth1: device MAC address 72:de:b2:3d:e6:90
Thu May 24 17:25:34 2018 kern.info kernel: [    5.108908] Generic PHY fixed-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:01, irq=POLL)
Thu May 24 17:25:34 2018 kern.info kernel: [    5.116638] dwmac1000: Master AXI performs any burst length
Thu May 24 17:25:34 2018 kern.info kernel: [    5.126091] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
Thu May 24 17:25:34 2018 kern.info kernel: [    5.131538] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock
Thu May 24 17:25:34 2018 kern.info kernel: [    5.140944] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Thu May 24 17:25:34 2018 kern.warn kernel: [    5.181510] urandom_read: 2 callbacks suppressed
Thu May 24 17:25:34 2018 kern.notice kernel: [    5.181513] random: procd: uninitialized urandom read (4 bytes read)
Thu May 24 17:25:34 2018 kern.info kernel: [    6.169750] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Thu May 24 17:25:34 2018 kern.info kernel: [    6.235408] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Thu May 24 17:25:34 2018 user.info kernel: [    8.305215] mount_root: loading kmods from internal overlay
Thu May 24 17:25:34 2018 user.info kernel: [    8.316367] kmodloader: loading kernel modules from //etc/modules-boot.d/*
Thu May 24 17:25:34 2018 user.info kernel: [    8.317598] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
Thu May 24 17:25:34 2018 kern.notice kernel: [    8.678122] random: crng init done
Thu May 24 17:25:34 2018 user.info kernel: [    9.762748] block: attempting to load /etc/config/fstab
Thu May 24 17:25:34 2018 user.err kernel: [    9.765809] block: unable to load configuration (fstab: Entry not found)
Thu May 24 17:25:34 2018 user.err kernel: [    9.766849] block: no usable configuration
Thu May 24 17:25:34 2018 kern.info kernel: [    9.915483] EXT4-fs (loop0): recovery complete
Thu May 24 17:25:34 2018 kern.info kernel: [    9.916503] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Thu May 24 17:25:34 2018 user.info kernel: [    9.919058] mount_root: loading kmods from internal overlay
Thu May 24 17:25:34 2018 user.info kernel: [    9.948569] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
Thu May 24 17:25:34 2018 user.info kernel: [    9.949439] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
Thu May 24 17:25:34 2018 kern.err kernel: [   10.500095] print_req_error: I/O error, dev loop0, sector 568
Thu May 24 17:25:34 2018 user.info kernel: [   11.557879] block: attempting to load /etc/config/fstab
Thu May 24 17:25:34 2018 user.err kernel: [   11.557975] block: unable to load configuration (fstab: Entry not found)
Thu May 24 17:25:34 2018 user.err kernel: [   11.562011] block: no usable configuration
Thu May 24 17:25:34 2018 user.info kernel: [   11.569560] mount_root: switching to ext4 overlay
Thu May 24 17:25:34 2018 user.warn kernel: [   11.603944] urandom-seed: Seeding with /etc/urandom.seed
Thu May 24 17:25:34 2018 user.info kernel: [   11.708959] procd: - early -
Thu May 24 17:25:34 2018 user.info kernel: [   11.709122] procd: - watchdog -
Thu May 24 17:25:34 2018 user.info kernel: [   12.381547] procd: - watchdog -
Thu May 24 17:25:34 2018 user.info kernel: [   12.381896] procd: - ubus -
Thu May 24 17:25:34 2018 user.info kernel: [   12.566953] procd: - init -
Thu May 24 17:25:34 2018 user.info kernel: [   12.726101] kmodloader: loading kernel modules from /etc/modules.d/*
Thu May 24 17:25:34 2018 kern.info kernel: [   12.733241] tun: Universal TUN/TAP device driver, 1.6
Thu May 24 17:25:34 2018 kern.info kernel: [   12.735844] ip6_tables: (C) 2000-2006 Netfilter Core Team
Thu May 24 17:25:34 2018 kern.info kernel: [   13.055174] fuse init (API version 7.26)
Thu May 24 17:25:34 2018 kern.info kernel: [   13.060636] usbcore: registered new interface driver cdc_acm
Thu May 24 17:25:34 2018 kern.info kernel: [   13.060664] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Thu May 24 17:25:34 2018 kern.info kernel: [   13.066266] usbcore: registered new interface driver cdc_wdm
Thu May 24 17:25:34 2018 kern.info kernel: [   13.073700] Loading modules backported from Linux version wt-2017-11-01-0-gfe248fc2c180
Thu May 24 17:25:34 2018 kern.info kernel: [   13.078997] Backport generated by backports.git v4.14-rc2-1-31-g86cf0e5d
Thu May 24 17:25:34 2018 kern.info kernel: [   13.088361] ip_tables: (C) 2000-2006 Netfilter Core Team
Thu May 24 17:25:34 2018 kern.info kernel: [   13.475584] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
Thu May 24 17:25:34 2018 kern.info kernel: [   13.687160] usbcore: registered new interface driver usblp
Thu May 24 17:25:34 2018 kern.info kernel: [   13.690281] usbcore: registered new interface driver usbserial
Thu May 24 17:25:34 2018 kern.info kernel: [   13.691571] usbcore: registered new interface driver usbserial_generic
Thu May 24 17:25:34 2018 kern.info kernel: [   13.697469] usbserial: USB Serial support registered for generic
Thu May 24 17:25:34 2018 kern.info kernel: [   13.708998] xt_time: kernel timezone is -0000
Thu May 24 17:25:34 2018 kern.info kernel: [   13.710901] usbcore: registered new interface driver cdc_ether
Thu May 24 17:25:34 2018 kern.info kernel: [   13.715100] usbcore: registered new interface driver cdc_ncm
Thu May 24 17:25:34 2018 kern.info kernel: [   13.727088] usbcore: registered new interface driver huawei_cdc_ncm
Thu May 24 17:25:34 2018 kern.info kernel: [   13.886845] PPP generic driver version 2.4.2
Thu May 24 17:25:35 2018 kern.info kernel: [   13.888043] NET: Registered protocol family 24
Thu May 24 17:25:35 2018 kern.info kernel: [   13.892230] usbcore: registered new interface driver qmi_wwan
Thu May 24 17:25:35 2018 kern.info kernel: [   13.896359] usbcore: registered new interface driver rndis_host
Thu May 24 17:25:35 2018 kern.info kernel: [   13.901356] usbcore: registered new interface driver sierra
Thu May 24 17:25:35 2018 kern.info kernel: [   13.906054] usbserial: USB Serial support registered for Sierra USB modem
Thu May 24 17:25:35 2018 kern.info kernel: [   13.913078] usbcore: registered new interface driver sierra_net
Thu May 24 17:25:35 2018 kern.debug kernel: [   13.928508] ath10k_pci 0000:01:00.0: assign IRQ: got 67
Thu May 24 17:25:35 2018 kern.info kernel: [   13.929083] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
Thu May 24 17:25:35 2018 kern.debug kernel: [   13.929195] ath10k_pci 0000:01:00.0: enabling bus mastering
Thu May 24 17:25:35 2018 kern.info kernel: [   13.929820] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Thu May 24 17:25:35 2018 kern.warn kernel: [   14.103487] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
Thu May 24 17:25:35 2018 kern.warn kernel: [   14.103524] ath10k_pci 0000:01:00.0: Falling back to user helper
Thu May 24 17:25:35 2018 kern.err kernel: [   20.036939] firmware ath10k!QCA9984!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
Thu May 24 17:25:35 2018 kern.info kernel: [   20.173030] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
Thu May 24 17:25:35 2018 kern.info kernel: [   20.173082] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Thu May 24 17:25:35 2018 kern.info kernel: [   20.186908] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.5.3-00053 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 4c56a386
Thu May 24 17:25:35 2018 kern.info kernel: [   22.466272] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:1 crc32 dd6d039c
Thu May 24 17:25:35 2018 kern.info kernel: [   28.339246] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.432489] ath: EEPROM regdomain: 0x0
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.432498] ath: EEPROM indicates default country code should be used
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.432505] ath: doing EEPROM country->regdmn map search
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.432517] ath: country maps to regdmn code: 0x3a
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.432525] ath: Country alpha2 being used: US
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.432532] ath: Regpair used: 0x3a
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.435924] ath10k_pci 0001:01:00.0: assign IRQ: got 100
Thu May 24 17:25:35 2018 kern.info kernel: [   28.436665] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
Thu May 24 17:25:35 2018 kern.debug kernel: [   28.436797] ath10k_pci 0001:01:00.0: enabling bus mastering
Thu May 24 17:25:35 2018 kern.info kernel: [   28.437413] ath10k_pci 0001:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Thu May 24 17:25:35 2018 kern.warn kernel: [   28.611839] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
Thu May 24 17:25:35 2018 kern.warn kernel: [   28.611889] ath10k_pci 0001:01:00.0: Falling back to user helper
Thu May 24 17:25:35 2018 kern.err kernel: [   28.942334] firmware ath10k!QCA9984!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
Thu May 24 17:25:35 2018 kern.info kernel: [   28.942545] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
Thu May 24 17:25:35 2018 kern.info kernel: [   28.950346] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Thu May 24 17:25:35 2018 kern.info kernel: [   28.963475] ath10k_pci 0001:01:00.0: firmware ver 10.4-3.5.3-00053 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 4c56a386
Thu May 24 17:25:35 2018 kern.info kernel: [   31.233764] ath10k_pci 0001:01:00.0: board_file api 2 bmi_id 0:2 crc32 dd6d039c
Thu May 24 17:25:35 2018 kern.info kernel: [   37.109078] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
Thu May 24 17:25:35 2018 kern.debug kernel: [   37.202528] ath: EEPROM regdomain: 0x0
Thu May 24 17:25:35 2018 kern.debug kernel: [   37.202537] ath: EEPROM indicates default country code should be used
Thu May 24 17:25:35 2018 kern.debug kernel: [   37.202544] ath: doing EEPROM country->regdmn map search
Thu May 24 17:25:35 2018 kern.debug kernel: [   37.202556] ath: country maps to regdmn code: 0x3a
Thu May 24 17:25:35 2018 kern.debug kernel: [   37.202564] ath: Country alpha2 being used: US
Thu May 24 17:25:35 2018 kern.debug kernel: [   37.202571] ath: Regpair used: 0x3a
Thu May 24 17:25:35 2018 kern.info kernel: [   37.209333] usbcore: registered new interface driver cdc_mbim
Thu May 24 17:25:35 2018 kern.info kernel: [   37.211074] usbcore: registered new interface driver option
Thu May 24 17:25:35 2018 kern.info kernel: [   37.214209] usbserial: USB Serial support registered for GSM modem (1-port)
Thu May 24 17:25:35 2018 kern.info kernel: [   37.232586] usbcore: registered new interface driver qcserial
Thu May 24 17:25:35 2018 kern.info kernel: [   37.232674] usbserial: USB Serial support registered for Qualcomm USB modem
Thu May 24 17:25:35 2018 user.info kernel: [   37.237659] kmodloader: done loading kernel modules from /etc/modules.d/*
Thu May 24 17:25:37 2018 user.notice : Added device handler type: tunnel
Thu May 24 17:25:37 2018 user.notice : Added device handler type: Network device
Thu May 24 17:25:37 2018 user.notice : Added device handler type: bridge
Thu May 24 17:25:37 2018 user.notice : Added device handler type: veth
Thu May 24 17:25:37 2018 user.notice : Added device handler type: macvlan
Thu May 24 17:25:37 2018 user.notice : Added device handler type: 8021ad
Thu May 24 17:25:37 2018 user.notice : Added device handler type: 8021q
Thu May 24 17:25:37 2018 daemon.notice procd: /etc/init.d/network: 'radio0' is disabled
Thu May 24 17:25:37 2018 daemon.notice procd: /etc/init.d/network: 'radio1' is disabled
Thu May 24 17:25:37 2018 daemon.notice procd: /etc/init.d/network: 'radio0' is disabled
Thu May 24 17:25:37 2018 daemon.notice procd: /etc/init.d/network: 'radio1' is disabled
Thu May 24 17:25:39 2018 kern.info kernel: [   41.911459] Generic PHY fixed-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:01, irq=POLL)
Thu May 24 17:25:39 2018 kern.info kernel: [   41.912406] dwmac1000: Master AXI performs any burst length
Thu May 24 17:25:39 2018 kern.info kernel: [   41.920485] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
Thu May 24 17:25:39 2018 kern.info kernel: [   41.925852] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock
Thu May 24 17:25:39 2018 kern.info kernel: [   41.934979] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Thu May 24 17:25:39 2018 kern.info kernel: [   41.951448] br-lan: port 1(eth1.1) entered blocking state
Thu May 24 17:25:39 2018 kern.info kernel: [   41.951477] br-lan: port 1(eth1.1) entered disabled state
Thu May 24 17:25:39 2018 kern.info kernel: [   41.956102] device eth1.1 entered promiscuous mode
Thu May 24 17:25:39 2018 kern.info kernel: [   41.961316] device eth1 entered promiscuous mode
Thu May 24 17:25:39 2018 kern.info kernel: [   41.967858] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'lan' is enabled
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'lan' is setting up now
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'lan' is now up
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'loopback' is enabled
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'loopback' is setting up now
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'loopback' is now up
Thu May 24 17:25:39 2018 kern.info kernel: [   41.981713] ipq806x-gmac-dwmac 37200000.ethernet eth0: device MAC address da:b6:53:b2:cf:3c
Thu May 24 17:25:39 2018 kern.info kernel: [   41.981918] Generic PHY fixed-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:00, irq=POLL)
Thu May 24 17:25:39 2018 kern.info kernel: [   41.989878] dwmac1000: Master AXI performs any burst length
Thu May 24 17:25:39 2018 kern.info kernel: [   41.998950] ipq806x-gmac-dwmac 37200000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
Thu May 24 17:25:39 2018 kern.info kernel: [   42.004678] ipq806x-gmac-dwmac 37200000.ethernet eth0: registered PTP clock
Thu May 24 17:25:39 2018 kern.info kernel: [   42.014072] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'wan' is enabled
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'wan6' is enabled
Thu May 24 17:25:39 2018 kern.info kernel: [   42.026591] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Thu May 24 17:25:39 2018 daemon.notice netifd: Network device 'lo' link is up
Thu May 24 17:25:39 2018 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu May 24 17:25:39 2018 daemon.err block: /dev/loop0 is already mounted on /overlay
Thu May 24 17:25:39 2018 daemon.err block: /dev/mmcblk0p5 is already mounted on /rom
Thu May 24 17:25:39 2018 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu May 24 17:25:39 2018 authpriv.info dropbear[1152]: Not backgrounding
Thu May 24 17:25:40 2018 kern.info kernel: [   42.982316] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Thu May 24 17:25:40 2018 kern.info kernel: [   42.985382] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Thu May 24 17:25:40 2018 daemon.notice netifd: Network device 'eth1' link is up
Thu May 24 17:25:40 2018 kern.info kernel: [   42.992759] br-lan: port 1(eth1.1) entered blocking state
Thu May 24 17:25:40 2018 kern.info kernel: [   42.996248] br-lan: port 1(eth1.1) entered forwarding state
Thu May 24 17:25:40 2018 daemon.notice netifd: VLAN 'eth1.1' link is up
Thu May 24 17:25:40 2018 daemon.notice netifd: bridge 'br-lan' link is up
Thu May 24 17:25:40 2018 daemon.notice netifd: Interface 'lan' has link connectivity
Thu May 24 17:25:40 2018 kern.info kernel: [   43.002774] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Thu May 24 17:25:40 2018 kern.info kernel: [   43.067233] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Thu May 24 17:25:40 2018 kern.info kernel: [   43.067305] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu May 24 17:25:40 2018 daemon.notice netifd: Network device 'eth0' link is up
Thu May 24 17:25:40 2018 kern.info kernel: [   43.076579] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Thu May 24 17:25:40 2018 daemon.notice netifd: VLAN 'eth0.2' link is up
Thu May 24 17:25:40 2018 daemon.notice netifd: Interface 'wan' has link connectivity
Thu May 24 17:25:40 2018 daemon.notice netifd: Interface 'wan' is setting up now
Thu May 24 17:25:40 2018 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu May 24 17:25:40 2018 daemon.notice netifd: Interface 'wan6' is setting up now
Thu May 24 17:25:40 2018 daemon.err odhcp6c[1404]: Failed to send RS (Address not available)
Thu May 24 17:25:40 2018 daemon.notice netifd: wan (1418): udhcpc: started, v1.28.3
Thu May 24 17:25:40 2018 daemon.notice netifd: wan (1418): udhcpc: sending discover
Thu May 24 17:25:40 2018 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Thu May 24 17:25:40 2018 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Thu May 24 17:25:40 2018 user.notice dnsmasq: Allowing RFC1918 responses for domain free.aero2.net.pl
Thu May 24 17:25:41 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led WLAN2G
Thu May 24 17:25:41 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led WLAN5G
Thu May 24 17:25:41 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led WAN
Thu May 24 17:25:41 2018 daemon.err odhcp6c[1404]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
Thu May 24 17:25:41 2018 daemon.info procd: - init complete -
Thu May 24 17:25:43 2018 daemon.notice netifd: wan (1418): udhcpc: sending discover
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: started, version 2.80test2 cachesize 150
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: DNS service limited to local subnets
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: 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 dumpfile
Thu May 24 17:25:44 2018 daemon.info dnsmasq-dhcp[1638]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: using local addresses only for domain test
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: using local addresses only for domain onion
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: using local addresses only for domain localhost
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: using local addresses only for domain local
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: using local addresses only for domain invalid
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: using local addresses only for domain bind
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: using local addresses only for domain lan
Thu May 24 17:25:44 2018 daemon.warn dnsmasq[1638]: no servers found in /tmp/resolv.conf.auto, will retry
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: read /etc/hosts - 4 addresses
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Thu May 24 17:25:44 2018 daemon.info dnsmasq-dhcp[1638]: read /etc/ethers - 0 addresses
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: read /etc/hosts - 4 addresses
Thu May 24 17:25:44 2018 daemon.info dnsmasq[1638]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Thu May 24 17:25:44 2018 daemon.info dnsmasq-dhcp[1638]: read /etc/ethers - 0 addresses
Thu May 24 17:25:44 2018 daemon.info dnsmasq-dhcp[1638]: DHCPREQUEST(br-lan) 192.168.1.72 f8:a9:63:2f:97:e7
Thu May 24 17:25:44 2018 daemon.info dnsmasq-dhcp[1638]: DHCPNAK(br-lan) 192.168.1.72 f8:a9:63:2f:97:e7 address not available
Thu May 24 17:25:46 2018 daemon.notice netifd: wan (1418): udhcpc: sending discover
Thu May 24 17:25:48 2018 daemon.info dnsmasq-dhcp[1638]: DHCPDISCOVER(br-lan) f8:a9:63:2f:97:e7
Thu May 24 17:25:48 2018 daemon.info dnsmasq-dhcp[1638]: DHCPOFFER(br-lan) 192.168.1.181 f8:a9:63:2f:97:e7
Thu May 24 17:25:48 2018 daemon.info dnsmasq[1638]: read /etc/hosts - 4 addresses
Thu May 24 17:25:48 2018 daemon.info dnsmasq[1638]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Thu May 24 17:25:48 2018 daemon.info dnsmasq-dhcp[1638]: read /etc/ethers - 0 addresses
Thu May 24 17:25:48 2018 daemon.info dnsmasq-dhcp[1638]: DHCPREQUEST(br-lan) 192.168.1.181 f8:a9:63:2f:97:e7
Thu May 24 17:25:48 2018 daemon.info dnsmasq-dhcp[1638]: DHCPACK(br-lan) 192.168.1.181 f8:a9:63:2f:97:e7 Laptop
Thu May 24 17:25:49 2018 authpriv.info dropbear[1799]: Child connection from 192.168.1.181:12859
Thu May 24 17:25:52 2018 authpriv.notice dropbear[1799]: Auth succeeded with blank password for 'root' from 192.168.1.181:12859
Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

2 Odpowiedź przez Cezary

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

Odp: ZyXEL Armor Z2 - NBG6817

Tak to jest się nie czyta i ma się zbyt wysokie wymagania smile

https://openwrt.org/toh/zyxel/nbg6817#flash_layout

Tak, masz tam 4GB tyle że partycja rootfs ma 64MB. Te pozostałe GB to jakieś bu1/bu2. To już sam musisz zobaczyć co tam jest i czy możesz to wykorzystać.

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

Cezary's Strona

3 Odpowiedź przez Gruberek

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: ZyXEL Armor Z2 - NBG6817

Wykorzystać mogę. Bez problemu da się to zamontować. Dziwię się tylko, że OpenWrt nie wykorzystuje tego jako /overlay tak jak to miało miejsce w NBG6716. Tam cały nand był wykorzystany.

root@OpenWrt:~# mount
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/loop0 on /overlay type ext4 (rw,noatime,data=ordered)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
/dev/mmcblk0p10 on /nand type ext4 (rw,relatime,data=ordered)
root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 5.3M      5.3M         0 100% /rom
tmpfs                   234.1M    848.0K    233.3M   0% /tmp
/dev/loop0               52.9M      1.4M     47.5M   3% /overlay
overlayfs:/overlay       52.9M      1.4M     47.5M   3% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mmcblk0p10           3.1G      5.6M      2.9G   0% /nand
root@OpenWrt:~#

Druga sprawa... Po ustawieniu VHT160 radio się nie podnosi. Dlaczego?

Thu May 24 18:14:43 2018 daemon.notice hostapd: wlan0: interface state ENABLED->DISABLED
Thu May 24 18:14:43 2018 daemon.notice hostapd: wlan0: AP-DISABLED
Thu May 24 18:14:43 2018 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Thu May 24 18:14:43 2018 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Thu May 24 18:14:43 2018 kern.info kernel: [ 2985.810008] device wlan0 left promiscuous mode
Thu May 24 18:14:43 2018 kern.info kernel: [ 2985.810103] br-lan: port 3(wlan0) entered disabled state
Thu May 24 18:14:43 2018 daemon.notice netifd: Network device 'wlan0' link is down
Thu May 24 18:14:43 2018 daemon.info dnsmasq[10835]: read /etc/hosts - 4 addresses
Thu May 24 18:14:43 2018 daemon.info dnsmasq[10835]: read /tmp/hosts/odhcpd - 1 addresses
Thu May 24 18:14:43 2018 daemon.info dnsmasq[10835]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Thu May 24 18:14:43 2018 daemon.info dnsmasq-dhcp[10835]: read /etc/ethers - 0 addresses
Thu May 24 18:14:43 2018 kern.warn kernel: [ 2986.560250] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Thu May 24 18:14:44 2018 daemon.notice netifd: radio0 (15340): command failed: Not supported (-95)
Thu May 24 18:14:44 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Thu May 24 18:14:50 2018 kern.info kernel: [ 2993.291573] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Thu May 24 18:14:50 2018 kern.info kernel: [ 2993.307664] br-lan: port 3(wlan0) entered blocking state
Thu May 24 18:14:50 2018 kern.info kernel: [ 2993.307741] br-lan: port 3(wlan0) entered disabled state
Thu May 24 18:14:50 2018 kern.info kernel: [ 2993.312694] device wlan0 entered promiscuous mode
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: interface state HT_SCAN->DFS
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: DFS-CAC-START freq=5200 chan=40 sec_chan=-1, width=2, seg0=50, seg1=0, cac_time=60s
Thu May 24 18:14:50 2018 daemon.err hostapd: DFS start_dfs_cac() failed, -1
Thu May 24 18:14:50 2018 daemon.err hostapd: Interface initialization failed
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: interface state DFS->DISABLED
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: AP-DISABLED
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: interface state DISABLED->DISABLED
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: AP-DISABLED
Thu May 24 18:14:50 2018 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Thu May 24 18:14:50 2018 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Thu May 24 18:14:50 2018 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Thu May 24 18:14:51 2018 kern.info kernel: [ 2993.680139] device wlan0 left promiscuous mode
Thu May 24 18:14:51 2018 kern.info kernel: [ 2993.680280] br-lan: port 3(wlan0) entered disabled state
Thu May 24 18:14:51 2018 kern.warn kernel: [ 2993.730190] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Thu May 24 18:14:51 2018 daemon.notice hostapd: ELOOP: remaining socket: sock=22 eloop_data=0xb6f45810 user_data=0 handler=0x370d4
Thu May 24 18:14:51 2018 daemon.notice netifd: radio0 (15340): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 14822 path ()
Thu May 24 18:14:57 2018 kern.info kernel: [ 2999.901083] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

4 Odpowiedź przez Cezary

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

Odp: ZyXEL Armor Z2 - NBG6817

Wg logów - ustawiłeś kanał na auto lub na jeden z DFS. Poczytaj forum lede, tam w wątkach o Z2 coś było z tym 160.

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

Cezary's Strona

5 Odpowiedź przez Gruberek

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: ZyXEL Armor Z2 - NBG6817

Na forum nic nie znalazłem. Wszystkie wątki dotyczą R7800. Czy ktoś może potwierdzić, że na R7800 też nie działa VHT160? Sprawdziłem na różnych kanałach i dupa.

Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

6 Odpowiedź przez andrzej.k (edytowany przez andrzej.k 2018-06-02 22:06:45)

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

Odp: ZyXEL Armor Z2 - NBG6817

Gruberek napisał/a:

Na forum nic nie znalazłem. Wszystkie wątki dotyczą R7800. Czy ktoś może potwierdzić, że na R7800 też nie działa VHT160? Sprawdziłem na różnych kanałach i dupa.

Na R7800 również nie działa, radio nie wstaje na 160. Nie działało również na LEDE 17.01 więc zignorowałem to myśląc, że sterownik jeszcze tego nie obsługuje.

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!

7 Odpowiedź przez Cezary

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

Odp: ZyXEL Armor Z2 - NBG6817

Może nie obsługuje. Zróbcie iw info pokażcie wynik.

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

Cezary's Strona

8 Odpowiedź przez andrzej.k (edytowany przez andrzej.k 2018-06-03 08:28:57)

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

Odp: ZyXEL Armor Z2 - NBG6817

iw phy0 info

iw phy0 info
Wiphy phy0
    max # scan SSIDs: 16
    max scan IEs length: 199 bytes
    max # sched scan SSIDs: 0
    max # match sets: 0
    max # scan plans: 1
    max scan plan interval: -1
    max scan plan iterations: 0
    Retry short limit: 7
    Retry long limit: 4
    Coverage class: 0 (up to 0m)
    Device supports AP-side u-APSD.
    Available Antennas: TX 0xf RX 0xf
    Configured Antennas: TX 0xf RX 0xf
    Supported interface modes:
         * managed
         * AP
         * AP/VLAN
         * monitor
         * mesh point
    Band 2:
        Capabilities: 0x19ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-31
        VHT Capabilities (0x339b79fa):
            Max MPDU length: 11454
            Supported Channel Width: 160 MHz, 80+80 MHz
            RX LDPC
            short GI (80 MHz)
            short GI (160/80+80 MHz)
            TX STBC
            SU Beamformer
            SU Beamformee
            MU Beamformer
            MU Beamformee
            RX antenna pattern consistency
            TX antenna pattern consistency
        VHT RX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: MCS 0-9
            4 streams: MCS 0-9
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT RX highest supported: 1560 Mbps
        VHT TX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: MCS 0-9
            4 streams: MCS 0-9
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT TX highest supported: 1560 Mbps
        Frequencies:
            * 5180 MHz [36] (20.0 dBm)
            * 5200 MHz [40] (20.0 dBm)
            * 5220 MHz [44] (20.0 dBm)
            * 5240 MHz [48] (20.0 dBm)
            * 5260 MHz [52] (20.0 dBm) (radar detection)
            * 5280 MHz [56] (20.0 dBm) (radar detection)
            * 5300 MHz [60] (20.0 dBm) (radar detection)
            * 5320 MHz [64] (20.0 dBm) (radar detection)
            * 5500 MHz [100] (27.0 dBm) (radar detection)
            * 5520 MHz [104] (27.0 dBm) (radar detection)
            * 5540 MHz [108] (27.0 dBm) (radar detection)
            * 5560 MHz [112] (27.0 dBm) (radar detection)
            * 5580 MHz [116] (27.0 dBm) (radar detection)
            * 5600 MHz [120] (27.0 dBm) (radar detection)
            * 5620 MHz [124] (27.0 dBm) (radar detection)
            * 5640 MHz [128] (27.0 dBm) (radar detection)
            * 5660 MHz [132] (27.0 dBm) (radar detection)
            * 5680 MHz [136] (27.0 dBm) (radar detection)
            * 5700 MHz [140] (27.0 dBm) (radar detection)
            * 5720 MHz [144] (disabled)
            * 5745 MHz [149] (disabled)
            * 5765 MHz [153] (disabled)
            * 5785 MHz [157] (disabled)
            * 5805 MHz [161] (disabled)
            * 5825 MHz [165] (disabled)
            * 5845 MHz [169] (disabled)
    valid interface combinations:
         * #{ managed } <= 1, #{ AP, mesh point } <= 16,
           total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

    HT Capability overrides:
         * MCS: ff ff ff ff ff ff ff ff ff ff
         * maximum A-MSDU length
         * supported channel width
         * short GI for 40 MHz
         * max A-MPDU length exponent
         * min MPDU start spacing
    Device supports VHT-IBSS.

iw wlan0 info

Interface wlan0
    ifindex 11
    wdev 0x2
    addr b.................5
    ssid F..................z
    type AP
    wiphy 0
    channel 40 (5200 MHz), width: 80 MHz, center1: 5210 MHz
    txpower 20.00 dBm

Czyli sterownik wspiera szerokość kanału 160 MHz?

Supported Channel Width: 160 MHz, 80+80 MHz

Przy okazji zapytam, czy na kanałach 100 - 140 można uzyskać większą moc nadawania?

5540 MHz [108] (27.0 dBm) (radar detection)
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!

9 Odpowiedź przez Gruberek

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: ZyXEL Armor Z2 - NBG6817

Wygląda na to, że niepotrzebnie czekałem na 18.06. Zainstalowałem stare dobre LEDE i problemy się skończyły. Co prawda nadal nie działa VHT160 ale prędkość zwiększyła się o ponad 50% do 400-420 mbps. NAT też działa dużo lepiej. Na 18.06 podczas speedtestu prędkość dochodziła max do 570 mbps przy rdzeniach obciążonych na 100%. Na LEDE bez problemu wyciągnąłem 600 mbps, a htop pokazał jedynie 33% smile Jak widać nie zawsze nowsze jest lepsze smile

Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

10 Odpowiedź przez andrzej.k

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

Odp: ZyXEL Armor Z2 - NBG6817

Cezary, jakieś pomysły na ustawienie szerokości kanału na 160 MHz na R7800?

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!

11 Odpowiedź przez Cezary

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

Odp: ZyXEL Armor Z2 - NBG6817

https://www.compex.com.sg/forum/t/5#Post87 itd. często przewija się informacja że ath10k tego po prostu nie obsługuje.

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

Cezary's Strona

12 Odpowiedź przez andrzej.k

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

Odp: ZyXEL Armor Z2 - NBG6817

https://git.openwrt.org/?p=openwrt/open … fc3b59c754

Wygląda na to, że w następnych obrazach Cezarego będzie działać szerokości kanału 160 MHz dla urządzeń obsługiwanych przez ath10k.

Wygląda również, że faktycznie 18.06 ostatnio ma problemy z wydajnością sieci, przynajmniej na R7800:

https://forum.lede-project.org/t/netgea … ca9984/285 (posty dodane w ostatnim czasie).

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!

13 Odpowiedź przez Gruberek

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: ZyXEL Armor Z2 - NBG6817

Mam nadzieję, że coś poprawią. Ja aktualnie używam LEDE i zastanawiam się czy nie przeprosić się z NBG6716, bo ma szybsze wifi ac i radzi sobie z moim łączem podobnie do NBG6817. Jedyna różnica to taka, że aby NBG6716 wyciągnął max z mojego łącza to musi obciążyć procek na 100%. NBG6817 nawet połowy nie wykorzystuje.

Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

14 Odpowiedź przez andrzej.k

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

Odp: ZyXEL Armor Z2 - NBG6817

Z tego co wyczytałem na forum pod wskazanym linkiem, to problem ma rozwiązać aktualizacja kernela do wersji 4.14.51, której jeszcze nie ma w 18.06 ani w master.

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!

15 Odpowiedź przez stefano

  • Zarejestrowany: 2018-12-29
  • Posty: 22

Odp: ZyXEL Armor Z2 - NBG6817

Witam..
Posiadam aktualne firmware producenta. Udało mi się zalogować przez ssh i mam problem z optware robiąc opkg update pokazuje mi się błąd:
root@NBG6817:~# opkg update
Downloading http://downloads.openwrt.org/attitude_a … ckages.gz.
Collected errors:
* opkg_download: Failed to download http://downloads.openwrt.org/attitude_a … ckages.gz: Error.

czy mógł by mi ktoś podać aktualny adres do pakietów "attitude_adjustment" do Armor Z2 ?

16 Odpowiedź przez Cezary

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

Odp: ZyXEL Armor Z2 - NBG6817

Złe forum. To jest forum o openwrt. Na openrouter.info zapraszam.

Dla AA takie repozytoria nie istnieją. QSDK na którym opiera się oryginalny soft ma szereg modyfikacji których jeszcze w tamtych czasach nie było w OpenWrt, m.in obsługę ipq.

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

Cezary's Strona

17 Odpowiedź przez stefano

  • Zarejestrowany: 2018-12-29
  • Posty: 22

Odp: ZyXEL Armor Z2 - NBG6817

Cezary dziękuje za informacje.
Rozumiem że z orginalnym softem nic  nie jestem w stanie zrobić. Mam jeszcze jedno pytanie czy istnieje możliwość zrobienia sysubgrade do wersiji openwrt np LEDE z luCi z mozliwością powrtotu do softu producenta. ?

18 Odpowiedź przez Cezary

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

Odp: ZyXEL Armor Z2 - NBG6817

Oryginał do openwrt: https://oldwiki.archive.openwrt.org/toh … stallation
Powrót do oryginału: https://forum.openwrt.org/t/how-do-i-ge … ware/14314

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

Cezary's Strona

19 Odpowiedź przez Gruberek

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: ZyXEL Armor Z2 - NBG6817

Udało mi się dzisiaj uruchomić VHT160. Najnowsze oprogramowanie od Candela Technologies + kmod-ath10k-ct. Co prawda prędkość pozostawia wiele do życzenia ( stabilne 370 Mbps ) ale zawsze to jakiś postęp. Testowane z kartą Intel 9560. Jak przyjdzie mi Intel AX200 to zrobię kolejne testy.
https://clip2net.com/clip/m351575/96194-clip-20kb.png

Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

20 Odpowiedź przez ambrozy5 (edytowany przez ambrozy5 2019-10-19 12:02:06)

  • Zarejestrowany: 2015-01-27
  • Posty: 2,419

Odp: ZyXEL Armor Z2 - NBG6817

z ciekawości jaki masz sirq przy przesyłaniu z taką prędkością ? wan -wlan  / lan-wlan , jeśli masz na nasie iperf to możesz też na lapku odpalić iperfa z parametrami  -P x  gdzie x to masz ilość równoczesnych połączeń , ja wtedy daje 8 /32/128 i 256 jak  obsłuży karta - wtedy obiciążam na maksa procka i sterownik karty ma też co robić

Dom : router https://i.imgur.com/IuB6Zwy.png | TP-LINK T1700G-28TQ |Zyxel XGS-1210-12 | 6x Ruckus r310 unleashed  + Ruckus icx7150-c12p | Truenas scale 124TB 25Gb| Xpenology 12TB | apc smart ups 750 lcd smile 100Mb/s - 25Gb/s
Podróżne : GL.Inet MT3000  +1TB hdd
Działka : rb260gs 1j wdm 1Gb+ ruckus r310 + nb m5 + kilka kamer ip  + panel 285Wp + lifepo4 12v 60Ah .

21 Odpowiedź przez Gruberek (edytowany przez Gruberek 2019-10-19 13:52:37)

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: ZyXEL Armor Z2 - NBG6817

https://pastebin.com/NwrE0r5b

Dziwne te wyniki. Najwięcej iperf pokazał prawie gigabit. Przy kopiowaniu plików po sambie przeważnie mam 46,7 MB/s ale zdarzają się wyniki takie jak poniżej:
https://clip2net.com/clip/m351575/15959-clip-22kb.png


https://pastebin.com/zEXvCgFx

Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

22 Odpowiedź przez ambrozy5

  • Zarejestrowany: 2015-01-27
  • Posty: 2,419

Odp: ZyXEL Armor Z2 - NBG6817

ciekawe, próbowałeś może smb multichannel ? wpinasz drugi lan w hp i konfigurujesz na inne ip np 1.3 , bez lacp/bond ,wtedy masz dwa połączenia o różnych ip i powinno śmigać do 2x szybciej , działa bodaj od win8.

Dom : router https://i.imgur.com/IuB6Zwy.png | TP-LINK T1700G-28TQ |Zyxel XGS-1210-12 | 6x Ruckus r310 unleashed  + Ruckus icx7150-c12p | Truenas scale 124TB 25Gb| Xpenology 12TB | apc smart ups 750 lcd smile 100Mb/s - 25Gb/s
Podróżne : GL.Inet MT3000  +1TB hdd
Działka : rb260gs 1j wdm 1Gb+ ruckus r310 + nb m5 + kilka kamer ip  + panel 285Wp + lifepo4 12v 60Ah .

23 Odpowiedź przez Gruberek

  • Skąd: Piotrków Tryb.
  • Zarejestrowany: 2013-08-04
  • Posty: 712

Odp: ZyXEL Armor Z2 - NBG6817

Nie mam wolnych portów w routerze.

Home: ZyXEL NBG6817 (OpenWrt)
NAS: HP ProLiant MicroServer Gen8 E3-1265L V2, 16 GB (PVE)

Gruberek's Strona

24 Odpowiedź przez stefano (edytowany przez stefano 2020-03-28 18:08:06)

  • Zarejestrowany: 2018-12-29
  • Posty: 22

Odp: ZyXEL Armor Z2 - NBG6817

Witam..
W końcu udało mi się zainstalować OpenWRT lluci na moim roterze. Posiadam własną domenę i tunel ipv6 z he.net kiedyś z niego korzystałem jak miałem tomato i wszystko działało bez problemu. teraz chciałbym ten tunel przerzucić na openwrt. tylko wtedy miałem stałe ip teraz mam zmienne. W luci prubowałem ustawić ddns z he i niby coś tam działa ale nie mogę połączyć się z luci od strony wan. jak sprawdzam dns to wychodzi mi "Using domain server:
Name:
127.0.0.1

Address:
127.0.0.1#53
Aliases:

Host v6.brucki.org not found: 2(SERVFAIL)"

I tak naprawde nie wiem czy teraz dobrze przekierowałem subdomene czy nie gdzie jest błąd.

Na hostingu ustawiłem rekordy NS na he.net a w he.net ustawiłem ddns i hasło  i na luci mi sie odpala scrypt myddns_ipv4 ale nie moge połonczyć się zdalnie z luci.

25 Odpowiedź przez Cezary

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

Odp: ZyXEL Armor Z2 - NBG6817

Żeby połączyć się z luci od wanu musisz odblokować wan na firewallu, zrobiłeś to?
Druga sprawa - w końcu ustawiłeś ddns czy nie? Zaloguj się do HE i zobacz czy masz aktualny adres tam ustawiony.

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

Cezary's Strona