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

marek645.1987 · 2018-01-09 12:57:23

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Temat: TP-Link Archer C50 + E3372 nie HiLink

Witam,
mam zainstalowany Lede 17.01.4 (archer c50) + e3372h nie hilink wg instrukcji : https://eko.one.pl/?p=openwrt-3g
Modem jest widoczny w systemie, tworzy się interfejs wwan0 z mac adresem modemu, dioda na modemie sygnalizuje połączenie LTE jednak nie mam adresu IP na tym interfejsie -> brak internetu.
Modem nowy z t-mobile działa bez problemu pod Fedora/Centos, ktoś może podrzucić działającą instrukcję instalacji tego modemu pod lede, probowałem obrazu z eko jaki ze strony lede -project wersji snapshot i stable. Ktoś może pomóc?

Marek

Cezary · 2018-01-09 13:42:03

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Pokaż wyniki poleceń: (tekst nie screenshoty)

cat /sys/kernel/debug/usb/devices
uci show network
logread
ifstatus wan

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

marek645.1987 · 2018-01-09 15:07:17

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

Witam,

root@LEDE:~# cat /sys/kernel/debug/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 4.04
S:  Manufacturer=Linux 4.4.92 ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=101c0000.ehci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1506 Rev= 1.02
S:  Manufacturer=HUAWEI_MOBILE
S:  Product=HUAWEI_MOBILE
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=12 Driver=option
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=option
E:  Ad=84(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:  If#= 2 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_cdc_ncm
E:  Ad=86(I) Atr=03(Int.) MxPS=  16 Ivl=2ms
I:* If#= 2 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_cdc_ncm
E:  Ad=86(I) Atr=03(Int.) MxPS=  16 Ivl=2ms
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=125us

root@LEDE:~# 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='fd07:bc29:dec7::/48'
network.lan=interface
network.lan.type='bridge'
network.lan.ifname='eth0.1'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.lan_dev=device
network.lan_dev.name='eth0.1'
network.lan_dev.macaddr='18:d6:c7:ba:8f:15'
network.wan=interface
network.wan.ifname='eth0.2'
network.wan.proto='ncm'
network.wan.device='/dev/ttyUSB0'
network.wan.pincode='2787'
network.wan.apn='internet'
network.wan.mode='lte'
network.wan_dev=device
network.wan_dev.name='eth0.2'
network.wan_dev.macaddr='18:d6:c7:ba:8f:16'
network.wan6=interface
network.wan6.ifname='eth0.2'
network.wan6.proto='dhcpv6'
network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device='switch0'
network.@switch_vlan[0].vlan='1'
network.@switch_vlan[0].ports='1 2 3 4 6t'
network.@switch_vlan[1]=switch_vlan
network.@switch_vlan[1].device='switch0'
network.@switch_vlan[1].vlan='2'
network.@switch_vlan[1].ports='0 6t'
network.wwan=interface
network.wwan.proto='dhcp'

root@LEDE:~# logread
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    0.000000] Linux version 4.4.92 (buildbot@debian8) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3557-a5e1f7f) ) #0 Mon Oct 16 22:57:05 2017
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Board has DDR2
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Analog PMU set to hw control
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Digital PMU set to hw control
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] SoC Type: MediaTek MT7620A ver:2 eco:6
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] bootconsole [early0] enabled
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] CPU0 revision is: 00019650 (MIPS 24KEc)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] MIPS: machine is TP-Link Archer C50
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Determined physical RAM map:
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000]  memory: 04000000 @ 00000000 (usable)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Initrd not found or empty - disabling initrd
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Zone ranges:
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000]   Normal   [mem 0x0000000000000000-0x0000000003ffffff]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Movable zone start for each node
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Early memory node ranges
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003ffffff]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.000000] On node 0 totalpages: 16384
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat 8035c4b0, node_mem_map 81000000
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.000000]   Normal zone: 128 pages used for memmap
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.000000]   Normal zone: 16384 pages, LIFO batch:3
Tue Jan  9 12:56:37 2018 kern.warn kernel: [    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Tue Jan  9 12:56:37 2018 kern.warn kernel: [    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    0.000000] Kernel command line: console=ttyS0,115200 rootfstype=squashfs,jffs2
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Writing ErrCtl register=0002dee0
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Readback ErrCtl register=0002dee0
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] Memory: 60944K/65536K available (3017K kernel code, 147K rwdata, 384K rodata, 156K init, 208K bss, 4592K reserved, 0K cma-reserved)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] NR_IRQS:256
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] CPU Clock: 580MHz
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] clocksource: systick: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 583261500 ns
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] systick: enable autosleep mode
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] systick: running - mult: 214748, shift: 32
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6590553264 ns
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.000012] sched_clock: 32 bits at 290MHz, resolution 3ns, wraps every 7405115902ns
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.007576] Calibrating delay loop... 385.84 BogoMIPS (lpj=1929216)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.070068] pid_max: default: 32768 minimum: 301
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.074693] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.081063] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.094746] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.104293] futex hash table entries: 256 (order: -1, 3072 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.110248] pinctrl core: initialized pinctrl subsystem
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.116578] NET: Registered protocol family 16
Tue Jan  9 12:56:37 2018 kern.warn kernel: [    0.126393] Can't analyze schedule() prologue at 8000acdc
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.386421] PCI host bridge /pcie@10140000 ranges:
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.391028]  MEM 0x0000000020000000..0x000000002fffffff
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.396100]   IO 0x0000000010160000..0x000000001016ffff
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.412583] rt2880_gpio 10000600.gpio: registering 24 gpios
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.418026] rt2880_gpio 10000600.gpio: registering 24 irq handlers
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.424193] rt2880_gpio 10000638.gpio: registering 16 gpios
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.429596] rt2880_gpio 10000638.gpio: registering 16 irq handlers
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.435713] rt2880_gpio 10000660.gpio: registering 32 gpios
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.441111] rt2880_gpio 10000660.gpio: registering 32 irq handlers
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.447230] rt2880_gpio 10000688.gpio: registering 1 gpios
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.452541] rt2880_gpio 10000688.gpio: registering 1 irq handlers
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.459186] PCI host bridge to bus 0000:00
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.463155] pci_bus 0000:00: root bus resource [mem 0x20000000-0x2fffffff]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.469779] pci_bus 0000:00: root bus resource [io  0xffffffff]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.475540] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.482121] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.489864] pci 0000:00:00.0: [1814:0801] type 01 class 0x060400
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.489913] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.489937] pci 0000:00:00.0: reg 0x14: [mem 0x20200000-0x2020ffff]
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.490012] pci 0000:00:00.0: supports D1
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.490031] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.490537] pci 0000:01:00.0: [14c3:7662] type 00 class 0x028000
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.490613] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit]
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.490676] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.490774] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.491031] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.491063] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.491117] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.497481] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.504294] pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x200fffff]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.510838] pci 0000:00:00.0: BAR 9: assigned [mem 0x20100000-0x201fffff pref]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.517867] pci 0000:00:00.0: BAR 1: assigned [mem 0x20200000-0x2020ffff]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.524453] pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x200fffff 64bit]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.531577] pci 0000:01:00.0: BAR 6: assigned [mem 0x20100000-0x2010ffff pref]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.538560] pci 0000:00:00.0: PCI bridge to [bus 01]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.543392] pci 0000:00:00.0:   bridge window [mem 0x20000000-0x200fffff]
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.549972] pci 0000:00:00.0:   bridge window [mem 0x20100000-0x201fffff pref]
Tue Jan  9 12:56:37 2018 kern.err kernel: [    0.557013] pci 0000:00:00.0: card - bus=0x0, slot = 0x0 irq=0
Tue Jan  9 12:56:37 2018 kern.err kernel: [    0.562654] pci 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.569203] clocksource: Switched to clocksource systick
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.575565] NET: Registered protocol family 2
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.580853] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.587582] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.593802] TCP: Hash tables configured (established 1024 bind 1024)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.600027] UDP hash table entries: 256 (order: 0, 4096 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.605652] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.612011] NET: Registered protocol family 1
Tue Jan  9 12:56:37 2018 kern.debug kernel: [    0.616231] PCI: CLS 80 bytes, default 32
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.621054] rt-timer 10000100.timer: maximum frequency is 1220Hz
Tue Jan  9 12:56:37 2018 kern.warn kernel: [    0.627695] Crashlog allocated RAM at address 0x3f00000
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.649006] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.654673] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.666767] io scheduler noop registered
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.670573] io scheduler deadline registered (default)
Tue Jan  9 12:56:37 2018 kern.err kernel: [    0.675750] ralink-usb-phy usbphy: invalid resource
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.681109] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.690938] console [ttyS0] disabled
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.694386] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000) is a Palmchip BK-3103
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.704061] console [ttyS0] enabled
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.711091] bootconsole [early0] disabled
Tue Jan  9 12:56:37 2018 kern.warn kernel: [    0.725805] spi spi0.0: force spi mode3
Tue Jan  9 12:56:37 2018 kern.info kernel: [    0.730366] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    0.735396] 6 ofpart partitions found on MTD device spi0.0
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    0.741042] Creating 6 MTD partitions on "spi0.0":
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    0.745935] 0x000000000000-0x000000020000 : "u-boot"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    0.752832] 0x000000020000-0x0000007c0000 : "firmware"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.724482] 2 tplink-fw partitions found on MTD device firmware
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.730571] 0x000000020000-0x0000001489e4 : "kernel"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.737207] 0x0000001489e4-0x0000007c0000 : "rootfs"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.744120] mtd: device 3 (rootfs) set to be root filesystem
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.750113] 1 squashfs-split partitions found on MTD device rootfs
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.756434] 0x000000379000-0x0000007c0000 : "rootfs_data"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.763800] 0x0000007c0000-0x0000007d0000 : "config"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.770736] 0x0000007d0000-0x0000007e0000 : "rom"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.777338] 0x0000007e0000-0x0000007f0000 : "romfile"
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    1.784406] 0x0000007f0000-0x000000800000 : "radio"
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.794266] gsw: setting port4 to ephy mode
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.798587] mtk_soc_eth 10100000.ethernet eth0 (uninitialized): port 3 link up (100Mbps/Full duplex)
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.808174] mtk_soc_eth 10100000.ethernet: loaded mt7620 driver
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.815058] mtk_soc_eth 10100000.ethernet eth0: mediatek frame engine at 0xb0100000, irq 5
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.824089] rt2880_wdt 10000120.watchdog: Initialized
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.830761] NET: Registered protocol family 10
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.839474] NET: Registered protocol family 17
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.844100] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.857002] 8021q: 802.1Q VLAN Support v1.8
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.875831] VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Tue Jan  9 12:56:37 2018 kern.info kernel: [    1.883942] Freeing unused kernel memory: 156K
Tue Jan  9 12:56:37 2018 user.info kernel: [    3.988038] init: Console is alive
Tue Jan  9 12:56:37 2018 user.info kernel: [    3.991879] init: - watchdog -
Tue Jan  9 12:56:37 2018 user.info kernel: [    5.443621] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Tue Jan  9 12:56:37 2018 user.info kernel: [    5.535938] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Tue Jan  9 12:56:37 2018 user.info kernel: [    5.547395] init: - preinit -
Tue Jan  9 12:56:37 2018 kern.info kernel: [    6.528679] 8021q: adding VLAN 0 to HW filter on device eth0
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    6.685144] random: procd: uninitialized urandom read (4 bytes read, 10 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    8.592965] jffs2: notice: (357) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Tue Jan  9 12:56:37 2018 user.info kernel: [    8.622829] mount_root: switching to jffs2 overlay
Tue Jan  9 12:56:37 2018 user.warn kernel: [    8.652395] urandom-seed: Seeding with /etc/urandom.seed
Tue Jan  9 12:56:37 2018 user.info kernel: [    8.712996] procd: - early -
Tue Jan  9 12:56:37 2018 user.info kernel: [    8.716138] procd: - watchdog -
Tue Jan  9 12:56:37 2018 user.info kernel: [    9.375745] procd: - watchdog -
Tue Jan  9 12:56:37 2018 user.info kernel: [    9.379307] procd: - ubus -
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    9.580030] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    9.776224] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    9.938944] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    9.958239] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [    9.978998] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [   10.007492] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [   10.024805] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [   10.040757] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 kern.notice kernel: [   10.055335] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
Tue Jan  9 12:56:37 2018 user.info kernel: [   10.067614] procd: - init -
Tue Jan  9 12:56:37 2018 user.info kernel: [   11.655098] kmodloader: loading kernel modules from /etc/modules.d/*
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.871928] usbcore: registered new interface driver usbfs
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.877744] usbcore: registered new interface driver hub
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.883283] usbcore: registered new device driver usb
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.938948] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.947225] ehci-platform: EHCI generic platform driver
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.962924] phy phy-usbphy.0: remote usb device wakeup disabled
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.968999] phy phy-usbphy.0: UTMI 16bit 30MHz
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.973571] ehci-platform 101c0000.ehci: EHCI Host Controller
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.979493] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus number 1
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.987713] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
Tue Jan  9 12:56:37 2018 kern.info kernel: [   11.999259] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.008176] hub 1-0:1.0: USB hub found
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.019567] hub 1-0:1.0: 1 port detected
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.035272] ip6_tables: (C) 2000-2006 Netfilter Core Team
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.058567] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.066825] Backport generated by backports.git backports-20160324-13-g24da7d3c
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.200862] mt76x2e 0000:01:00.0: ASIC revision: 76120044
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.276495] mt76x2e 0000:01:00.0: ROM patch already applied
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.623586] usb 1-1: new high-speed USB device number 2 using ehci-platform
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.658570] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.664252] mt76x2e 0000:01:00.0: Build: 1
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.668433] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Tue Jan  9 12:56:37 2018 kern.info kernel: [   12.861803] mt76x2e 0000:01:00.0: Firmware running!
Tue Jan  9 12:56:37 2018 kern.debug kernel: [   12.867920] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.051383] usbcore: registered new interface driver cdc_wdm
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.082059] ip_tables: (C) 2000-2006 Netfilter Core Team
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.113549] nf_conntrack version 0.5.0 (954 buckets, 3816 max)
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.241201] usbcore: registered new interface driver usbserial
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.247266] usbcore: registered new interface driver usbserial_generic
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.254110] usbserial: USB Serial support registered for generic
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.358645] xt_time: kernel timezone is -0000
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.386985] usbcore: registered new interface driver cdc_ncm
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.470540] usbcore: registered new interface driver huawei_cdc_ncm
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.502374] PPP generic driver version 2.4.2
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.521134] NET: Registered protocol family 24
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.574181] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "radio"
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.581467] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.589475] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
Tue Jan  9 12:56:37 2018 kern.debug kernel: [   13.597198] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.674363] usbcore: registered new interface driver option
Tue Jan  9 12:56:37 2018 kern.info kernel: [   13.680276] usbserial: USB Serial support registered for GSM modem (1-port)
Tue Jan  9 12:56:37 2018 user.info kernel: [   13.739742] kmodloader: done loading kernel modules from /etc/modules.d/*
Tue Jan  9 12:56:37 2018 kern.info kernel: [   14.038864] usb 1-1: USB disconnect, device number 2
Tue Jan  9 12:56:37 2018 kern.info kernel: [   14.899573] usb 1-1: new high-speed USB device number 3 using ehci-platform
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.212973] option 1-1:1.0: GSM modem (1-port) converter detected
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.219668] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.227105] option 1-1:1.1: GSM modem (1-port) converter detected
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.233752] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.434033] huawei_cdc_ncm 1-1:1.2: MAC-Address: 00:1e:10:1f:00:00
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.440416] huawei_cdc_ncm 1-1:1.2: setting rx_max = 16384
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.496560] huawei_cdc_ncm 1-1:1.2: NDP will be placed at end of frame for this device.
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.505112] huawei_cdc_ncm 1-1:1.2: cdc-wdm0: USB WDM device
Tue Jan  9 12:56:37 2018 kern.info kernel: [   15.512198] huawei_cdc_ncm 1-1:1.2 wwan0: register 'huawei_cdc_ncm' at usb-101c0000.ehci-1, Huawei CDC NCM device, 00:1e:10:1f:00:00
Tue Jan  9 12:56:41 2018 user.notice : Added device handler type: 8021ad
Tue Jan  9 12:56:41 2018 user.notice : Added device handler type: 8021q
Tue Jan  9 12:56:41 2018 user.notice : Added device handler type: macvlan
Tue Jan  9 12:56:41 2018 user.notice : Added device handler type: bridge
Tue Jan  9 12:56:41 2018 user.notice : Added device handler type: Network device
Tue Jan  9 12:56:41 2018 user.notice : Added device handler type: tunnel
Tue Jan  9 12:56:41 2018 daemon.notice procd: /etc/init.d/network: 'radio0' is disabled
Tue Jan  9 12:56:41 2018 daemon.notice procd: /etc/init.d/network: 'radio0' is disabled
Tue Jan  9 12:56:43 2018 authpriv.info dropbear[1141]: Not backgrounding
Tue Jan  9 12:56:44 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led lan
Tue Jan  9 12:56:44 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led wan
Tue Jan  9 12:56:44 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led USB
Tue Jan  9 12:56:44 2018 daemon.notice procd: /etc/rc.d/S96led: /etc/rc.common: eval: line 1: can't create /sys/class/leds/c50:green:usb/ports/usb1-port1: nonexistent directory
Tue Jan  9 12:56:44 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led wlan2g
Tue Jan  9 12:56:44 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led wifi
Tue Jan  9 12:56:46 2018 kern.info kernel: [   24.626915] 8021q: adding VLAN 0 to HW filter on device eth0
Tue Jan  9 12:56:46 2018 kern.info kernel: [   24.653977] device eth0.1 entered promiscuous mode
Tue Jan  9 12:56:46 2018 kern.info kernel: [   24.658887] device eth0 entered promiscuous mode
Tue Jan  9 12:56:46 2018 kern.info kernel: [   24.673308] br-lan: port 1(eth0.1) entered forwarding state
Tue Jan  9 12:56:46 2018 kern.info kernel: [   24.679041] br-lan: port 1(eth0.1) entered forwarding state
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'lan' is enabled
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'lan' is setting up now
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'lan' is now up
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'loopback' is enabled
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'loopback' is setting up now
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'loopback' is now up
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'wan' is setting up now
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'wan6' is enabled
Tue Jan  9 12:56:46 2018 daemon.info odhcpd[1104]: Raising SIGUSR1 due to address change on br-lan
Tue Jan  9 12:56:46 2018 daemon.notice netifd: bridge 'br-lan' link is up
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'lan' has link connectivity 
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Network device 'eth0' link is up
Tue Jan  9 12:56:46 2018 daemon.notice netifd: VLAN 'eth0.1' link is up
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Network device 'lo' link is up
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'loopback' has link connectivity 
Tue Jan  9 12:56:46 2018 daemon.notice netifd: VLAN 'eth0.2' link is up
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'wan6' has link connectivity 
Tue Jan  9 12:56:46 2018 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Jan  9 12:56:46 2018 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Tue Jan  9 12:56:47 2018 daemon.info odhcpd[1104]: Using a RA lifetime of 0 seconds on br-lan
Tue Jan  9 12:56:47 2018 daemon.notice odhcpd[1104]: Failed to send to ff02::1%br-lan (Address not available)
Tue Jan  9 12:56:47 2018 daemon.info odhcpd[1104]: Using a RA lifetime of 0 seconds on br-lan
Tue Jan  9 12:56:47 2018 daemon.notice odhcpd[1104]: Got DHCPv6 request
Tue Jan  9 12:56:47 2018 daemon.warn odhcpd[1104]: DHCPV6 CONFIRM IA_NA from 000441c7ba8f06df78879101231d2b2a7ddb on br-lan: not on-link 
Tue Jan  9 12:56:47 2018 daemon.notice netifd: radio1 (1245): command failed: Not supported (-122)
Tue Jan  9 12:56:47 2018 daemon.info procd: - init complete -
Tue Jan  9 12:56:48 2018 daemon.notice odhcpd[1104]: Got DHCPv6 request
Tue Jan  9 12:56:48 2018 daemon.warn odhcpd[1104]: DHCPV6 SOLICIT IA_NA from 000441c7ba8f06df78879101231d2b2a7ddb on br-lan: ok fd07:bc29:dec7::ff9/128 
Tue Jan  9 12:56:48 2018 kern.info kernel: [   26.669273] br-lan: port 1(eth0.1) entered forwarding state
Tue Jan  9 12:56:49 2018 daemon.notice odhcpd[1104]: Got DHCPv6 request
Tue Jan  9 12:56:49 2018 daemon.warn odhcpd[1104]: DHCPV6 REQUEST IA_NA from 000441c7ba8f06df78879101231d2b2a7ddb on br-lan: ok fd07:bc29:dec7::ff9/128 
Tue Jan  9 12:56:49 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Tue Jan  9 12:56:50 2018 kern.info kernel: [   28.588324] IPv6: ADDRCONF(NETDEV_UP): wlan1-1: link is not ready
Tue Jan  9 12:56:50 2018 daemon.notice netifd: wan (1242): sending -> AT
Tue Jan  9 12:56:50 2018 kern.info kernel: [   28.616411] device wlan1-1 entered promiscuous mode
Tue Jan  9 12:56:50 2018 daemon.notice hostapd: wlan1-1: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Jan  9 12:56:50 2018 daemon.err hostapd: Using interface wlan1-1 with hwaddr 18:d6:c7:ba:8f:12 and ssid "LEDE"
Tue Jan  9 12:56:50 2018 daemon.notice hostapd: wlan1-1: interface state COUNTRY_UPDATE->ENABLED
Tue Jan  9 12:56:50 2018 daemon.notice hostapd: wlan1-1: AP-ENABLED 
Tue Jan  9 12:56:50 2018 kern.info kernel: [   28.735487] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Tue Jan  9 12:56:50 2018 daemon.notice netifd: radio1 (1245): Successfully initialized wpa_supplicant
Tue Jan  9 12:56:50 2018 daemon.notice netifd: wan (1242): sending -> ATZ
Tue Jan  9 12:56:51 2018 daemon.notice netifd: Interface 'wwan' is enabled
Tue Jan  9 12:56:51 2018 daemon.notice netifd: wan (1242): sending -> ATQ0
Tue Jan  9 12:56:51 2018 daemon.notice netifd: wan (1242): sending -> ATV1
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.813074] wlan1: authenticate with 44:78:3e:5b:16:da
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.827831] wlan1: send auth to 44:78:3e:5b:16:da (try 1/3)
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.835135] wlan1: authenticated
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.840803] wlan1: associate with 44:78:3e:5b:16:da (try 1/3)
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.847927] wlan1: RX AssocResp from 44:78:3e:5b:16:da (capab=0x411 status=0 aid=2)
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.855959] wlan1: associated
Tue Jan  9 12:56:52 2018 daemon.notice netifd: Network device 'wlan1' link is up
Tue Jan  9 12:56:52 2018 daemon.notice netifd: Interface 'wwan' has link connectivity 
Tue Jan  9 12:56:52 2018 daemon.notice netifd: Interface 'wwan' is setting up now
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.859507] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.883729] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.890649] br-lan: port 2(wlan1-1) entered forwarding state
Tue Jan  9 12:56:52 2018 kern.info kernel: [   29.896497] br-lan: port 2(wlan1-1) entered forwarding state
Tue Jan  9 12:56:52 2018 daemon.notice netifd: Network device 'wlan1-1' link is up
Tue Jan  9 12:56:52 2018 daemon.notice netifd: wwan (1516): udhcpc: started, v1.25.1
Tue Jan  9 12:56:52 2018 daemon.notice netifd: wwan (1516): udhcpc: sending discover
Tue Jan  9 12:56:52 2018 daemon.notice netifd: wwan (1516): udhcpc: sending select for 192.168.43.235
Tue Jan  9 12:56:52 2018 daemon.notice netifd: wan (1242): sending -> ATE1
Tue Jan  9 12:56:52 2018 daemon.notice netifd: wwan (1516): udhcpc: lease of 192.168.43.235 obtained, lease time 3600
Tue Jan  9 12:56:52 2018 daemon.notice netifd: Interface 'wwan' is now up
Tue Jan  9 12:56:52 2018 user.notice firewall: Reloading firewall due to ifup of wwan (wlan1)
Tue Jan  9 12:56:53 2018 daemon.notice netifd: wan (1242): sending -> ATS0=0
Tue Jan  9 12:56:53 2018 daemon.info odhcpd[1104]: Using a RA lifetime of 0 seconds on br-lan
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: started, version 2.78 cachesize 150
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: DNS service limited to local subnets
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: 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
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq-dhcp[1564]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: using local addresses only for domain lan
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: reading /tmp/resolv.conf.auto
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: using local addresses only for domain lan
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: using nameserver 192.168.43.1#53
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: read /etc/hosts - 4 addresses
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: read /tmp/hosts/odhcpd - 0 addresses
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq[1564]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Tue Jan  9 12:56:53 2018 daemon.info dnsmasq-dhcp[1564]: read /etc/ethers - 0 addresses
Tue Jan  9 12:56:53 2018 daemon.notice netifd: wan (1242): sending -> AT+CGDCONT=1,"IP","internet"
Tue Jan  9 12:56:54 2018 kern.info kernel: [   31.433837] br-lan: port 2(wlan1-1) entered forwarding state
Tue Jan  9 12:56:56 2018 daemon.notice netifd: wan (1242): SIM ready
Tue Jan  9 12:56:56 2018 daemon.notice netifd: wan (1242): PIN set successfully
Tue Jan  9 12:56:56 2018 daemon.notice netifd: wan (1242): sending -> AT^SYSCFGEX="03",3fffffff,2,4,7fffffffffffffff,,
Tue Jan  9 12:56:57 2018 daemon.notice netifd: wan (1242): Starting network wan
Tue Jan  9 12:56:58 2018 daemon.notice netifd: wan (1242): sending -> AT^NDISDUP=1,1,"internet"
Tue Jan  9 12:56:58 2018 daemon.notice netifd: wan (1242): Setting up wwan0
Tue Jan  9 12:56:58 2018 daemon.notice netifd: Interface 'wan' is now up
Tue Jan  9 12:56:58 2018 daemon.notice netifd: Network device 'wwan0' link is up
Tue Jan  9 12:56:58 2018 daemon.notice netifd: Network alias 'wwan0' link is up
Tue Jan  9 12:56:58 2018 daemon.notice netifd: Interface 'wan_4' is enabled
Tue Jan  9 12:56:58 2018 daemon.notice netifd: Interface 'wan_4' has link connectivity 
Tue Jan  9 12:56:58 2018 daemon.notice netifd: Interface 'wan_4' is setting up now
Tue Jan  9 12:56:58 2018 daemon.notice netifd: wan (1242): Command failed: Unknown error
Tue Jan  9 12:56:58 2018 daemon.notice netifd: wan_4 (1656): udhcpc: started, v1.25.1
Tue Jan  9 12:56:59 2018 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Tue Jan  9 12:56:59 2018 daemon.notice netifd: wan_4 (1656): udhcpc: sending discover
Tue Jan  9 12:58:24 2018 daemon.info dnsmasq-dhcp[1564]: DHCPDISCOVER(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b 
Tue Jan  9 12:58:24 2018 daemon.info dnsmasq-dhcp[1564]: DHCPOFFER(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b 
Tue Jan  9 12:58:24 2018 daemon.info dnsmasq-dhcp[1564]: DHCPREQUEST(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b 
Tue Jan  9 12:58:24 2018 daemon.info dnsmasq-dhcp[1564]: DHCPACK(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b luq
Tue Jan  9 12:58:24 2018 daemon.info odhcpd[1104]: Using a RA lifetime of 0 seconds on br-lan
Tue Jan  9 12:58:27 2018 daemon.notice netifd: wan_4 (1656): udhcpc: sending discover
Tue Jan  9 12:58:28 2018 authpriv.info dropbear[1740]: Child connection from 192.168.1.100:58232
Tue Jan  9 12:58:29 2018 authpriv.notice dropbear[1740]: Auth succeeded with blank password for 'root' from 192.168.1.100:58232
Tue Jan  9 12:58:30 2018 daemon.notice netifd: wan_4 (1656): udhcpc: sending discover
Tue Jan  9 12:58:31 2018 kern.notice kernel: [   38.816682] random: nonblocking pool is initialized
Tue Jan  9 12:58:56 2018 daemon.info dnsmasq[1564]: read /etc/hosts - 4 addresses
Tue Jan  9 12:58:56 2018 daemon.info dnsmasq[1564]: read /tmp/hosts/odhcpd - 0 addresses
Tue Jan  9 12:58:56 2018 daemon.info dnsmasq[1564]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Tue Jan  9 12:58:56 2018 daemon.info dnsmasq-dhcp[1564]: read /etc/ethers - 0 addresses

root@LEDE:~#  ifstatus wan
{
    "up": true,
    "pending": false,
    "available": true,
    "autostart": true,
    "dynamic": false,
    "uptime": 200,
    "l3_device": "wwan0",
    "proto": "ncm",
    "updated": [
        "data"
    ],
    "metric": 0,
    "dns_metric": 0,
    "delegation": true,
    "ipv4-address": [
        
    ],
    "ipv6-address": [
        
    ],
    "ipv6-prefix": [
        
    ],
    "ipv6-prefix-assignment": [
        
    ],
    "route": [
        
    ],
    "dns-server": [
        
    ],
    "dns-search": [
        
    ],
    "inactive": {
        "ipv4-address": [
            
        ],
        "ipv6-address": [
            
        ],
        "route": [
            
        ],
        "dns-server": [
            
        ],
        "dns-search": [
            
        ]
    },
    "data": {
        "manufacturer": "huawei"
    }
}

dziekuję za szybka reakcję

Marek

Cezary · 2018-01-09 15:13:54

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Możesz zrobić ifstatus wan_4 ale raczej masz up:false.

Konfig masz ok (zbędna jest opcja ifname i sekcja wwan), połączenie doszło do skutku ale nie dostałeś adresu ip od operatora.
Możesz wykonać dwie sprawy:
- sprawdź czy połączy się jak zmienisz na pozostałe interfejsy: /dev/ttyUSB1 lub /dev/cdc-wdm0, po zmianie zrób reboot routera
- ustaw proto 3g zamiast proto ncm i sprawdź czy się w ogóle połączy na tym interfejsie który masz podany.

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

marek645.1987 · 2018-01-09 18:04:41

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

Witam,
zmiana urządzenia i/lub protokołu nie przyniosła efektu(próbowałem różne kombinację):

/dev/cdc-wdm0

Tue Jan  9 14:45:08 2018 daemon.notice netifd: wan (1178): timeout checking for PIN.Unable to verify PIN
Tue Jan  9 14:45:08 2018 daemon.notice netifd: wan (1464): Stopping network wan
Tue Jan  9 14:45:09 2018 daemon.notice netifd: wan (1464): sending -> 
Tue Jan  9 14:45:11 2018 kern.notice kernel: [   35.051971] random: nonblocking pool is initialized
Tue Jan  9 14:45:13 2018 daemon.notice netifd: Interface 'wan' is now down


Tue Jan  9 15:16:03 2018 daemon.notice netifd: wan (1176): Timeout running AT-command
Tue Jan  9 15:16:03 2018 daemon.notice netifd: wan (1176): Failed to set operating mode
Tue Jan  9 15:16:04 2018 daemon.notice netifd: wan (1486): Stopping network wan
Tue Jan  9 15:16:04 2018 daemon.notice netifd: wan (1486): sending -> 
Tue Jan  9 15:16:06 2018 daemon.info dnsmasq-dhcp[1471]: DHCPDISCOVER(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b 
Tue Jan  9 15:16:06 2018 daemon.info dnsmasq-dhcp[1471]: DHCPOFFER(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b 
Tue Jan  9 15:16:06 2018 daemon.info dnsmasq-dhcp[1471]: DHCPREQUEST(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b 
Tue Jan  9 15:16:06 2018 daemon.info dnsmasq-dhcp[1471]: DHCPACK(br-lan) 192.168.1.100 f8:ca:b8:36:c3:0b luq
Tue Jan  9 15:16:07 2018 kern.notice kernel: [   37.720170] random: nonblocking pool is initialized
Tue Jan  9 15:16:09 2018 daemon.notice netifd: Interface 'wan' is now down
Tue Jan  9 15:16:09 2018 daemon.notice netifd: Interface 'wan' is setting up now

3g usb0
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: AT&F^M^M
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: OK
Tue Jan  9 14:37:40 2018 local2.info chat[1449]:  -- got it
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: send (ATE1^M)
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: expect (OK)
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: ^M
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: A^M
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: ^MODE: 5,4^M
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: TE1^M^M
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: OK
Tue Jan  9 14:37:40 2018 local2.info chat[1449]:  -- got it
Tue Jan  9 14:37:40 2018 local2.info chat[1449]: send (AT+CGDCONT=1,"IP","internet"^M)
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: timeout set to 30 seconds
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: expect (OK)
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: ^M
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: AT+CGDCONT=1,"IP","internet"^M^M
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: OK
Tue Jan  9 14:37:41 2018 local2.info chat[1449]:  -- got it
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: send (ATD*99***1#^M)
Tue Jan  9 14:37:41 2018 kern.info kernel: [   29.676907] br-lan: port 2(wlan1-1) entered forwarding state
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: expect (CONNECT)
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: ^M
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: ATD*99***1#^M^M
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: CONNECT
Tue Jan  9 14:37:41 2018 local2.info chat[1449]:  -- got it
Tue Jan  9 14:37:41 2018 local2.info chat[1449]: send ( ^M)
Tue Jan  9 14:37:41 2018 daemon.info pppd[1447]: Serial connection established.
Tue Jan  9 14:37:41 2018 kern.info kernel: [   29.732443] 3g-wan: renamed from ppp0
Tue Jan  9 14:37:41 2018 daemon.info pppd[1447]: Using interface 3g-wan
Tue Jan  9 14:37:41 2018 daemon.notice pppd[1447]: Connect: 3g-wan <--> /dev/ttyUSB0
Tue Jan  9 14:38:03 2018 kern.notice kernel: [   37.438269] random: nonblocking pool is initialized
Tue Jan  9 14:38:12 2018 daemon.warn pppd[1447]: LCP: timeout sending Config-Requests
Tue Jan  9 14:38:12 2018 daemon.notice pppd[1447]: Connection terminated.
Tue Jan  9 14:38:13 2018 daemon.notice pppd[1447]: Modem hangup
Tue Jan  9 14:38:13 2018 daemon.info pppd[1447]: Exit.
Tue Jan  9 14:38:13 2018 daemon.notice netifd: Interface 'wan' is now down
Tue Jan  9 14:38:13 2018 daemon.notice netifd: Interface 'wan' is setting up now
Tue Jan  9 14:38:31 2018 daemon.notice netifd: Interface 'wan' is now down

Cezary · 2018-01-09 19:13:50

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Nie dostajesz danych od operatora. proto=3g powinno bez problemu ruszyć a masz to samo - problem z uzyskaniem adresu ip od operatora.

Wróć tak jak było na /dev/ttyUSB0 i ncm.

PS. Weź weź router i podłącz go w tym samym miejscu gdzie chodzi na normalnym linuksie.

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

marek645.1987 · 2018-01-09 19:33:46

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

nie rozumiem, co gdzie mam podłączyć

Cezary · 2018-01-09 19:37:10

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Pisałeś że testowałeś modem na fedorze i działało. W miejscu gdzie testowałeś postaw router, podłącz modem i sprawdź czy się łączy.

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

marek645.1987 · 2018-01-09 20:24:09

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

AA ok, działa, teraz z niego korzystam:
to z lapka poniżej niby ten sam sterownik, NetworkManagera odpaliłem z logowaniem debug ale nie widać chyba duzo...

T:  Bus=02 Lev=02 Prnt=05 Port=00 Cnt=01 Dev#=  8 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1506 Rev= 1.02
S:  Manufacturer=HUAWEI_MOBILE
S:  Product=HUAWEI_MOBILE
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=12 Driver=option
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=option
E:  Ad=84(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:  If#= 2 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_cdc_ncm
E:  Ad=86(I) Atr=03(Int.) MxPS=  16 Ivl=2ms
I:* If#= 2 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_cdc_ncm
E:  Ad=86(I) Atr=03(Int.) MxPS=  16 Ivl=2ms
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=125us

Cezary · 2018-01-09 20:26:53

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

To działa w końcu z routerem czy nie?

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

marek645.1987 · 2018-01-09 20:39:06

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

działa tylko z lapka, żeby sie z netem połączyć przepinam modem do lapka, na routerze nie działa, ten log wyżej jest z lapka

grze11 · 2018-01-15 17:41:39

grze11
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-15
Posty: 3

Odp: TP-Link Archer C50 + E3372 nie HiLink

Witam,
mam identyczną sytuację: ten sam modem (E3372 nie HiLink), inny router (WR1043ND v4, najnowsze zmodyfikowane LEDE). Modem łączy się prawidłowo (LED w trybie LTE), powtórzyłem wszystkie powyższe instrukcje. Wniosek wydaje się identyczny - problem z uzyskaniem adresu ip od operatora.
Modem działa prawidłowo na laptopie z oprogramowaniem Internet Manager. Jak uzyskać połączenie na routerze?

Cezary · 2018-01-15 17:45:09

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Zmień soft na modemie na hlinkowy.

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

marek645.1987 · 2018-01-17 23:47:22

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

Cześć,
co ciekawe adres ip zdaje sie, że modem dostaje po wysłaniau komendy AT^DHCP? dostahe ip,maskę,dns itd (w hex) - niestety jak zapodam adres , maskę, broadcast do interfejsu wwan0 (taki u mnie ncm robi) to niestety i tak nie mam komunikacji ze światem znaczy pingi nie wychodzą. Wyłączyłem firewall'a ustawiłem tablicę rutingu i nic, co najwyzej pinguje sie na swoj adres. HiLink to ostateczność. ktoś może pomóc jak to zdebugować?
ten sam modem pod Fedorą śmiga na lapku, ponoc to jest ten sam moduł co w openwrt (huawei_cdc_ncm). Nie jestem pewien.
@Cezary na forum pisałeś że na modemie trzeba jakieś porty ustawić(AT) na modemie i że e3372 wymaga specjalnego traktowania, możesz rozwinąć?

Marek

Cezary · 2018-01-17 23:49:13

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Polecenie at^setport ale raczej masz włączony.

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

marek645.1987 · 2018-01-17 23:51:10

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

Co ono włącza?
może fedora coś właśnie dodatkowo wysyła (AT) do modemu ...?

Cezary · 2018-01-17 23:52:11

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Możesz sterować ilością (typem) dostępnych portów, wirtualnym modemem i kartą SD.

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

marek645.1987 · 2018-01-17 23:58:09

marek645.1987
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-09
Posty: 9

Odp: TP-Link Archer C50 + E3372 nie HiLink

https://gist.github.com/artizirk/20acc2ab07fe6cad9fcc
jeszcze z tymi portami powalcze

grze11 · 2018-02-06 17:53:41

grze11
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-15
Posty: 3

Odp: TP-Link Archer C50 + E3372 nie HiLink

Cezary napisał/a:

Zmień soft na modemie na hlinkowy.

Po zmianie softu na HiLink działa bez problemu:) Co było powodem poprzedniej sytuacji? Problem ze sterownikami?

Cezary · 2018-02-06 17:54:48

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Nie. Ja mam dużo zwykłych modemów i bez problemów działają.

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

grze11 · 2018-02-09 22:22:52

grze11
Użytkownik
Nieaktywny

Zarejestrowany: 2018-01-15
Posty: 3

Odp: TP-Link Archer C50 + E3372 nie HiLink

Przetestowałem 3 różne typy modemów Huawei na 2 różnych typach routerów (z różnymi wersjami OpenWRT): 2 zwykłe (w tym ten E3372) i jeden HiLink. E3372 nie-HiLink nie działał na żadnym z nich. Coś Huawei namieszał w firmware?

Cezary · 2018-02-09 22:29:35

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

Podłącz zwykły, zrób ^setport i pokaż jak masz interfejsy ustawione.

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

pierunie · 2018-03-30 22:54:26

pierunie
Użytkownik
Nieaktywny

Zarejestrowany: 2018-03-30
Posty: 8

Odp: TP-Link Archer C50 + E3372 nie HiLink

Hej,

mam identyczny problem na TL-MR3420v1 + LEDE 17.01 snapshot z eko.one.pl + extroot + E3372h-153 (nie hilink)
Modem działa normalnie pod fabrycznym fw na TL-MR3420v2.
Pod LEDE modem przedstawia się tak:

root@LEDE:cat /sys/kernel/debug/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  1, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 4.04
S:  Manufacturer=Linux 4.4.120 ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=ehci-platform
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=05e3 ProdID=0608 Rev= 7.02
S:  Product=USB2.0 Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1506 Rev= 1.02
S:  Manufacturer=HUAWEI_MOBILE
S:  Product=HUAWEI_MOBILE
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=12 Driver=option
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=option
E:  Ad=84(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:  If#= 2 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_cdc_ncm
E:  Ad=86(I) Atr=03(Int.) MxPS=  16 Ivl=2ms
I:* If#= 2 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_cdc_ncm
E:  Ad=86(I) Atr=03(Int.) MxPS=  16 Ivl=2ms
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=125us

Próbowałem łączyć się na różne sposoby (ncm/3g) i na różnych dev (ttyUSB0/ttyUSB1/cdc-wdm0). Zawsze wychodzi jakiś błąd.
Przykładowe zrzuty:

3g:

Fri Mar 30 21:47:34 2018 daemon.notice netifd: Interface 'wan' is setting up now
Fri Mar 30 21:47:38 2018 daemon.notice netifd: wan (1896): SIM ready
Fri Mar 30 21:47:38 2018 daemon.notice netifd: wan (1896): PIN set successfully
Fri Mar 30 21:47:38 2018 daemon.notice pppd[1912]: pppd 2.4.7 started by root, uid 0
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: abort on (BUSY)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: abort on (NO CARRIER)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: abort on (ERROR)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: report (CONNECT)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: timeout set to 10 seconds
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: send (AT&F^M)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: expect (OK)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: AT&F^M^M
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: OK
Fri Mar 30 21:47:39 2018 local2.info chat[1914]:  -- got it
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: send (ATE1^M)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: expect (OK)
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: ^M
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: ATE1^M^M
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: OK
Fri Mar 30 21:47:39 2018 local2.info chat[1914]:  -- got it
Fri Mar 30 21:47:39 2018 local2.info chat[1914]: send (AT+CGDCONT=1,"IP","internet"^M)
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: timeout set to 30 seconds
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: expect (OK)
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: ^M
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: AT+CGDCONT=1,"IP","internet"^M^M
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: OK
Fri Mar 30 21:47:40 2018 local2.info chat[1914]:  -- got it
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: send (ATD*99***1#^M)
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: expect (CONNECT)
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: ^M
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: ATD*99***1#^M^M
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: ERROR
Fri Mar 30 21:47:40 2018 local2.info chat[1914]:  -- failed
Fri Mar 30 21:47:40 2018 local2.info chat[1914]: Failed (ERROR)
Fri Mar 30 21:47:40 2018 daemon.err pppd[1912]: Connect script failed
Fri Mar 30 21:47:41 2018 daemon.info pppd[1912]: Exit.
Fri Mar 30 21:47:41 2018 daemon.notice netifd: Interface 'wan' is now down

ncm/cdc-wdm0:

Fri Mar 30 21:59:16 2018 daemon.notice netifd: Interface 'wan' is setting up now
Fri Mar 30 21:59:18 2018 daemon.notice netifd: wan (1403): Starting network wan
Fri Mar 30 21:59:18 2018 daemon.notice netifd: wan (1403): sending ->
Fri Mar 30 21:59:33 2018 daemon.notice netifd: wan (1403): Timeout running AT-command
Fri Mar 30 21:59:33 2018 daemon.notice netifd: wan (1403): Failed to connect
Fri Mar 30 21:59:33 2018 daemon.notice netifd: wan (1430): Stopping network wan
Fri Mar 30 21:59:34 2018 daemon.notice netifd: wan (1430): sending ->
Fri Mar 30 21:59:38 2018 daemon.notice netifd: Interface 'wan' is now down

ncm/ttyUSB1:

Fri Mar 30 22:00:24 2018 daemon.notice netifd: Interface 'wan' is setting up now
Fri Mar 30 22:00:27 2018 daemon.notice netifd: wan (1107): sending -> AT
Fri Mar 30 22:00:28 2018 daemon.notice netifd: wan (1107): sending -> ATZ
Fri Mar 30 22:00:29 2018 daemon.notice netifd: wan (1107): sending -> ATQ0
Fri Mar 30 22:00:29 2018 daemon.notice netifd: wan (1107): sending -> ATV1
Fri Mar 30 22:00:30 2018 daemon.notice netifd: wan (1107): sending -> ATE1
Fri Mar 30 22:00:30 2018 daemon.notice netifd: wan (1107): sending -> ATS0=0
Fri Mar 30 22:00:31 2018 daemon.notice netifd: wan (1107): sending -> AT+CGDCONT=1,"IP","internet"
Fri Mar 30 22:00:32 2018 daemon.notice netifd: wan (1107): Starting network wan
Fri Mar 30 22:00:32 2018 daemon.notice netifd: wan (1107): sending -> AT^NDISDUP=1,1,"internet"
Fri Mar 30 22:00:33 2018 daemon.notice netifd: wan (1107): Setting up wwan0
Fri Mar 30 22:00:33 2018 daemon.notice netifd: Interface 'wan' is now up
Fri Mar 30 22:00:33 2018 daemon.notice netifd: Network device 'wwan0' link is up
Fri Mar 30 22:00:33 2018 daemon.notice netifd: Network alias 'wwan0' link is up
Fri Mar 30 22:00:33 2018 daemon.notice netifd: Interface 'wan_4' is enabled
Fri Mar 30 22:00:33 2018 daemon.notice netifd: Interface 'wan_4' has link connectivity
Fri Mar 30 22:00:33 2018 daemon.notice netifd: Interface 'wan_4' is setting up now
Fri Mar 30 22:00:33 2018 daemon.notice netifd: wan (1107): Command failed: Unknown error
Fri Mar 30 22:00:33 2018 daemon.notice netifd: wan_4 (1294): udhcpc: started, v1.25.1
Fri Mar 30 22:00:33 2018 user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
Fri Mar 30 22:00:34 2018 daemon.notice netifd: wan_4 (1294): udhcpc: sending discover
Fri Mar 30 22:00:37 2018 daemon.notice netifd: wan_4 (1294): udhcpc: sending discover
Fri Mar 30 22:00:40 2018 daemon.notice netifd: wan_4 (1294): udhcpc: sending discover

Ciekawostka, po wysłaniu picocomem komendy AT+SETPORT="A1,A2;10,16,12,1,A1,A2" otrzymuję odpowiedź: COMMAND NOT SUPPORT.

Cezary · 2018-03-30 22:58:47

Cezary
...
Aktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 106,455

Odp: TP-Link Archer C50 + E3372 nie HiLink

AT^SETPORT a nie AT+SETPORT

Parę razy na forum było też że pomogła zmiana firmware na inny.

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

pierunie · 2018-03-31 00:24:23

pierunie
Użytkownik
Nieaktywny

Zarejestrowany: 2018-03-30
Posty: 8

Odp: TP-Link Archer C50 + E3372 nie HiLink

AT^SETPORT="A1,A2;10,16,12,1,A1,A2"
ERROR

W takim razie spróbuję zmienić firmware.

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

TP-Link Archer C50 + E3372 nie HiLink (Strona 1 z 2)

Posty: 1 do 25 z 30

1 Temat przez marek645.1987 2018-01-09 12:57:23

Temat: TP-Link Archer C50 + E3372 nie HiLink

2 Odpowiedź przez Cezary 2018-01-09 13:42:03

Odp: TP-Link Archer C50 + E3372 nie HiLink

3 Odpowiedź przez marek645.1987 2018-01-09 15:07:17

Odp: TP-Link Archer C50 + E3372 nie HiLink

4 Odpowiedź przez Cezary 2018-01-09 15:13:54

Odp: TP-Link Archer C50 + E3372 nie HiLink

5 Odpowiedź przez marek645.1987 2018-01-09 18:04:41

Odp: TP-Link Archer C50 + E3372 nie HiLink

6 Odpowiedź przez Cezary 2018-01-09 19:13:50

Odp: TP-Link Archer C50 + E3372 nie HiLink

7 Odpowiedź przez marek645.1987 2018-01-09 19:33:46

Odp: TP-Link Archer C50 + E3372 nie HiLink

8 Odpowiedź przez Cezary 2018-01-09 19:37:10

Odp: TP-Link Archer C50 + E3372 nie HiLink

9 Odpowiedź przez marek645.1987 2018-01-09 20:24:09

Odp: TP-Link Archer C50 + E3372 nie HiLink

10 Odpowiedź przez Cezary 2018-01-09 20:26:53

Odp: TP-Link Archer C50 + E3372 nie HiLink

11 Odpowiedź przez marek645.1987 2018-01-09 20:39:06

Odp: TP-Link Archer C50 + E3372 nie HiLink

12 Odpowiedź przez grze11 2018-01-15 17:41:39

Odp: TP-Link Archer C50 + E3372 nie HiLink

13 Odpowiedź przez Cezary 2018-01-15 17:45:09

Odp: TP-Link Archer C50 + E3372 nie HiLink

14 Odpowiedź przez marek645.1987 2018-01-17 23:47:22

Odp: TP-Link Archer C50 + E3372 nie HiLink

15 Odpowiedź przez Cezary 2018-01-17 23:49:13

Odp: TP-Link Archer C50 + E3372 nie HiLink

16 Odpowiedź przez marek645.1987 2018-01-17 23:51:10 (edytowany przez marek645.1987 2018-01-17 23:52:32)

Odp: TP-Link Archer C50 + E3372 nie HiLink

17 Odpowiedź przez Cezary 2018-01-17 23:52:11

Odp: TP-Link Archer C50 + E3372 nie HiLink

18 Odpowiedź przez marek645.1987 2018-01-17 23:58:09

Odp: TP-Link Archer C50 + E3372 nie HiLink

19 Odpowiedź przez grze11 2018-02-06 17:53:41

Odp: TP-Link Archer C50 + E3372 nie HiLink

20 Odpowiedź przez Cezary 2018-02-06 17:54:48

Odp: TP-Link Archer C50 + E3372 nie HiLink

21 Odpowiedź przez grze11 2018-02-09 22:22:52

Odp: TP-Link Archer C50 + E3372 nie HiLink

22 Odpowiedź przez Cezary 2018-02-09 22:29:35

Odp: TP-Link Archer C50 + E3372 nie HiLink

23 Odpowiedź przez pierunie 2018-03-30 22:54:26

Odp: TP-Link Archer C50 + E3372 nie HiLink

24 Odpowiedź przez Cezary 2018-03-30 22:58:47

Odp: TP-Link Archer C50 + E3372 nie HiLink

25 Odpowiedź przez pierunie 2018-03-31 00:24:23

Odp: TP-Link Archer C50 + E3372 nie HiLink

Posty: 1 do 25 z 30