Novi Asus router ali ne kužim baš

[Neo-ST]

I sad prva nejasnoća. Ona je postavljena na 192.168.1.1
Asus je na 192.168.50.1 (to su mu tvorničke postavke).
Teltonici sam pokušao isključit DHCP server, jer šta će joj kada je Asus DHCP server ? No, kada to napravim, više ništa ne radi, pa sam vratio ovako.
Ne kužim zašto ništa ne radi ako joj to isključim, pogotovo jer je ona na .1.1, a Asus na .50.1 ?

Ovo je network map od Asusa:

Šta je sad ovaj WAN IP ?

DHCP server postavke Asusa:

Jel ovdje sve u redu ?

WAN postavke Asusa:

Jel ovdje sve u redu ?

I sada općenito pitanje, Teltonika nije u bridge modu. Tu se po forumu spominjalo da nije dobro imati dva routera u mreži, a sada je to tako postavljeno (i doduše radi).
Da je prebacim u bridge mode?
Da li mi za to trebaju oni PPoE podaci od ISP-a i da li uopće da je prebacujem ili ostavim ovako ?

Hvala

[xlr]

Modem baci u bridge. Ako ne ugasi automatski, ugasi mu ti rucno DHCP i wifi.

Asusa za pocetak factory resetiraj na defaultne postavke, spoji Teltoniku na WAN, odaberi automatic IP za WAN kod inicijalnog setupa i to je u principu ti. Tmobile 4G ne treba PPPoE podatke.

Double NAT i kemijanje s dva DHCP servera/rutera ti zbilja nije potrebno. Ako si kupio Asusa da ti bude mozak mreze, Teltonika mora ici u bridge.

[Nikky]

@Neo-ST
Sve šta opisuješ je logično, da sad ne idem stavku po stavku.
Kako si sam zaključio, najbolje je da Teltoniku prekonfiguriraš u Bridge mode i usput joj ugasi WiFi.
Pogledaj naljepnicu pa ovdje napiši koji je model Teltonike (RUTXXX)?

Asusu odradi factory reset da kreneš iz početka,
nakon toga mu na Lan strani promijeni IP adresu sa defaultnih 192.168.50.1 na 192.168.2.1 + Reboot,
tako ćeš lakše pratiti šta se dešava i kasnije organizirati svoju mrežu,
također neka ostane (kako mu je po defaultu) WAN - Automatic IP.

Prije prčkanja po Teltonici slikaj / zapiši sve šta mijenjaš da se možeš vratiti ako negdje pogriješiš.
Ako imaš RUT950 ovo su upute za prebacivanje u Bridge mode > https://www.solwise.co.uk/downloads/...ging-guide.pdf
Ako imaš RUT240 ovo su upute za prebacivanje u Bridge / passthrough mode > https://community.teltonika-networks...gh-to-wan-port
https://wiki.teltonika-networks.com/...240_Interfaces

Ako sve dobro odradiš onda će:
- PC spojen na Lan Asusa izaći na Internet
- u slikovnici Asusa pod WAN IP će biti javna IP adresa a ne nešto iz 192.168.1.x ranga

Naknadno možeš /mo složiti da vidiš status Teltonike "kroz" Asusa.

[Neo-ST]

Model je Teltonika RUTX09 (nema wifi).
Probat ću kasnije sve ovo pa javim kako je prošlo.
Ova Teltonika je dosta drugačija od "običnih" routera, bridge mode radim na mob1sa1 interfaceu i zahtijeva da se upiše hardverska MAC adresa routera (Asusa)...

[Nikky]

Da, mob1sa1 interface je WWAN tj. 4g,
mijenjaš mu Mode = NAT na Mode = Bridge ili Passthrough,
MAC kojeg spominješ je od WAN porta na Asusu.
Info > https://wiki.teltonika-networks.com/view/RUTX09_WAN

[Neo-ST]

Ma kakvi.
Jebem se zadnja 3 sata i ništa ne funkcionira dobro osim kada su postavljeni ovako u double NAT, odnosno kad Teltonika nije u bridge modu.

Postavim je u bridge mode po uputstvima, upišem MAC adresu od Asusa, ugasim joj DHCP server na LANu, i nema spoja na net. Asus prijavljuje grešku:





Nakon sat ipo skužim da jedino (jedva) radi kada uključim DHCP server na LANu u Teltonici, onda Asus izbaci vanjski IP od WANa, međutim to traje par minuta pa veza pukne i počne izbacivat sljedeće poruke:

[Nikky]

Ostavi DHCP Server upaljen na Teltonici.

[xlr]

Sta kaze Asusov system log? On bi trebao malo vise info baciti. Ove poruke su dosta opcenite, ne pomazu. Takodjer i Teltonica ako ima logova, ne bi skodilo.

Iskopcaj WAN sa Asusa, ugasi wifi na Asusu ako imas spojenih klijenata (da smanjis broj nebitnih logova), obrisi kompletan log, pa ukopcaj WAN kabel. Pejstaj nam taj cisti log. I to mozes ponoviti za oba scenarija, sa bridgeom i bez njega

[Cuky]

Ovo ti je sve ok podeseno.

Na ovo bih samo upalio dmz na teltonici za asusovu ip adresu (sa prilozene slike je to 192.168.1.139) te rezervirao tu ip adresu na njenom dhcp serveru tako da ne skoci na neku drugu.

Bridge nemas potrebe paliti.

I normalno je da imas dhcp server na oba rutera. Kada asusa spojis na teltoniku nesto mu mora dat adresu (osim ako je nisi fizicki fiksirao na asus ruteru). I isto tako asusov ruter dijeli adrese uredajima koji se spoje na njega sa svog dhcp servera. Najnormalnije ponasanje.

[Neo-ST]

Dec  6 22:26:57 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:26:57 WAN(0) Connection: WAN(0) link up.
Dec  6 22:26:57 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:27:06 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:27:09 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:27:12 WAN(0) Connection: WAN(0) link up.
Dec  6 22:27:12 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:27:30 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:27:33 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:27:33 WAN(0) Connection: WAN(0) link up.
Dec  6 22:27:33 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:27:35 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:27:37 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:27:39 WAN(0) Connection: WAN(0) link up.
Dec  6 22:27:39 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:27:48 wan: finish adding multi routes
Dec  6 22:27:48 WAN(0) Connection: WAN was restored.
Dec  6 22:27:50 BWDPI: force to flush flowcache entries
Dec  6 22:27:50 kernel: udb_core lock_num = 7
Dec  6 22:27:51 BWDPI: rollback fc
Dec  6 22:27:53 kernel: SHN Release Version: 2.0.7 371dd35_RELS_8
Dec  6 22:27:53 kernel: UDB Core Version: 0.2.20
Dec  6 22:27:53 kernel: Registered DNS Req parsing
Dec  6 22:27:53 kernel: sizeof forward pkt param = 280
Dec  6 22:27:53 BWDPI: fun bitmap = 4bf
Dec  6 22:27:53 A.QoS: qos_count=0, qos_check=0
Dec  6 22:27:53 kernel: ERR[qos_start:4068] qos_ops is not registered!
Dec  6 22:27:53 kernel: ioctl_iqos_op_switch(1) fail!
Dec  6 22:27:53 A.QoS: set_qos_on fails
Dec  6 22:27:53 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Dec  6 22:27:54 A.QoS: qos_count=0, qos_check=1
Dec  6 22:27:55 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:27:57 rc_service: udhcpc_wan 1086:notify_rc stop_samba
Dec  6 22:27:57 Samba Server: smb daemon is stopped
Dec  6 22:27:58 rc_service: udhcpc_wan 1086:notify_rc start_samba
Dec  6 22:27:59 dhcp client: bound 192.168.1.139/255.255.255.0 via 192.168.1.1 for 43200 seconds.
Dec  6 22:28:00 WAN(0) Connection: WAN(0) link down.
Dec  6 22:28:02 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:28:03 WAN(0) Connection: WAN(0) link up.
Dec  6 22:28:03 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:28:05 wan: finish adding multi routes
Dec  6 22:28:06 WAN(0) Connection: WAN was restored.
Dec  6 22:28:08 BWDPI: force to flush flowcache entries
Dec  6 22:28:08 kernel: udb_core lock_num = 1
Dec  6 22:28:08 BWDPI: rollback fc
Dec  6 22:28:10 kernel: SHN Release Version: 2.0.7 371dd35_RELS_8
Dec  6 22:28:10 kernel: UDB Core Version: 0.2.20
Dec  6 22:28:10 kernel: Registered DNS Req parsing
Dec  6 22:28:10 kernel: sizeof forward pkt param = 280
Dec  6 22:28:10 BWDPI: fun bitmap = 4bf
Dec  6 22:28:10 A.QoS: qos_count=0, qos_check=0
Dec  6 22:28:13 rc_service: udhcpc_wan 1906:notify_rc stop_samba
Dec  6 22:28:13 Samba Server: smb daemon is stopped
Dec  6 22:28:14 rc_service: udhcpc_wan 1906:notify_rc start_samba
Dec  6 22:28:15 dhcp client: bound 10.240.14.247/255.255.255.240 via 10.240.14.248 for 3600 seconds.
Dec  6 22:33:11 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:33:14 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:33:18 WAN(0) Connection: WAN(0) link up.
Dec  6 22:33:18 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:33:23 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:33:26 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:33:28 WAN(0) Connection: WAN(0) link up.
Dec  6 22:33:28 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:33:48 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:33:50 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:33:51 WAN(0) Connection: WAN(0) link up.
Dec  6 22:33:51 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:33:52 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:33:54 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:34:13 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Dec  6 22:34:18 WAN(0) Connection: WAN(0) link down.
Dec  6 22:34:19 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Dec  6 22:34:21 WAN(0) Connection: WAN(0) link up.
Dec  6 22:34:21 rc_service: wanduck 1526:notify_rc restart_wan_if 0
Dec  6 22:34:27 wan: finish adding multi routes
Dec  6 22:34:27 WAN(0) Connection: WAN was restored.
Dec  6 22:34:29 BWDPI: force to flush flowcache entries
Dec  6 22:34:29 kernel: udb_core lock_num = 1
Dec  6 22:34:30 BWDPI: rollback fc
Dec  6 22:34:33 kernel: SHN Release Version: 2.0.7 371dd35_RELS_8
Dec  6 22:34:33 kernel: UDB Core Version: 0.2.20
Dec  6 22:34:33 kernel: Registered DNS Req parsing
Dec  6 22:34:33 kernel: sizeof forward pkt param = 280
Dec  6 22:34:33 BWDPI: fun bitmap = 4bf
Dec  6 22:34:33 A.QoS: qos_count=0, qos_check=0
Dec  6 22:34:36 rc_service: udhcpc_wan 3982:notify_rc stop_samba
Dec  6 22:34:36 Samba Server: smb daemon is stopped
Dec  6 22:34:37 rc_service: udhcpc_wan 3982:notify_rc start_samba
Dec  6 22:34:38 dhcp client: bound 10.252.130.57/255.255.255.252 via 10.252.130.58 for 3600 seconds.

Pričekao sam da dva puta izgubi konekciju i počne brljat one poruke iz gornjeg posta, a to je vidljivo u logu svugdje di piše Link DOWN.


Log od Teltonike:

Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Booting Linux on physical CPU 0x0
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.000000] Linux version 5.10.188 (app@runner-wcht1mz7-project-352-concurrent-0) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 8.4.0 r16279-5cc0535800) 8.4.0, GNU ld (GNU Binutils) 2.34) #0 SMP Thu Oct 12 07:55:18 2023
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] CPU: div instructions available: patching division code
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] OF: fdt: Machine model: RUTX09 STM32
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Memory policy: Data cache writealloc
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Zone ranges:
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000]   Normal   [mem 0x0000000080000000-0x000000008fffffff]
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000]   HighMem  empty
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Movable zone start for each node
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Early memory node ranges
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000080000000-0x0000000087dfffff]
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000087e00000-0x0000000087ffffff]
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000088000000-0x000000008fffffff]
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x000000008fffffff]
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    0.000000] On node 0 totalpages: 65536
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    0.000000]   Normal zone: 576 pages used for memmap
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    0.000000]   Normal zone: 65536 pages, LIFO batch:15
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] percpu: Embedded 15 pages/cpu s30924 r8192 d22324 u61440
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    0.000000] pcpu-alloc: s30924 r8192 d22324 u61440 alloc=15*4096
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 64960
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.000000] Kernel command line: ubi.mtd=rootfs ubi.block=0,1 root=/dev/ubiblock0_1 rootfstype=squashfs console=ttyMSM0,115200n8 rootwait
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] Memory: 247168K/262144K available (6340K kernel code, 611K rwdata, 1612K rodata, 1024K init, 236K bss, 14976K reserved, 0K cma-reserved, 0K highmem)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] rcu: Hierarchical RCU implementation.
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] 	Tracing variant of Tasks RCU enabled.
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] arch_timer: cp15 timer(s) running at 48.00MHz (virt).
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb11fd3bfb, max_idle_ns: 440795203732 ns
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000008] sched_clock: 56 bits at 48MHz, resolution 20ns, wraps every 4398046511096ns
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000026] Switching to timer-based delay loop, resolution 20ns
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000358] Calibrating delay loop (skipped), value calculated using timer frequency.. 96.00 BogoMIPS (lpj=480000)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000384] pid_max: default: 32768 minimum: 301
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000569] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.000590] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.001606] CPU: Testing write buffer coherency: ok
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.002015] qcom_scm: convention: smc legacy
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.003035] Setting up static identity map for 0x80300000 - 0x8030003c
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.003212] rcu: Hierarchical SRCU implementation.
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.003493] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.003864] smp: Bringing up secondary CPUs ...
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.007576] smp: Brought up 1 node, 4 CPUs
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.007605] SMP: Total of 4 processors activated (384.00 BogoMIPS).
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.007615] CPU: All CPU(s) started in SVC mode.
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.013024] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.013207] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.013237] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.013478] pinctrl core: initialized pinctrl subsystem
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.015375] NET: Registered protocol family 16
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.015781] DMA: preallocated 256 KiB pool for atomic coherent allocations
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.016944] thermal_sys: Registered thermal governor 'step_wise'
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.017411] cpuidle: using governor ladder
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.017503] cpuidle: using governor menu
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.045656] cryptd: max_cpu_qlen set to 1000
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.050316] usbcore: registered new interface driver usbfs
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.050392] usbcore: registered new interface driver hub
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.050456] usbcore: registered new device driver usb
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.050509] pps_core: LinuxPPS API ver. 1 registered
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.050522] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.050550] PTP clock support registered
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.052432] clocksource: Switched to clocksource arch_sys_counter
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.053468] NET: Registered protocol family 2
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.053730] IP idents hash table entries: 4096 (order: 3, 32768 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.054671] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.054727] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.054773] TCP bind hash table entries: 2048 (order: 2, 16384 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.054823] TCP: Hash tables configured (established 2048 bind 2048)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.054951] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.054996] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.055356] NET: Registered protocol family 1
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.055415] PCI: CLS 0 bytes, default 64
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.058860] workingset: timestamp_bits=14 max_order=16 bucket_order=2
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.063546] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.063573] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Wed Dec  6 22:30:37 2023 kern.err kernel: [    0.207073] bam-dma-engine 8e04000.dma: num-channels unspecified in dt
Wed Dec  6 22:30:37 2023 kern.err kernel: [    0.207101] bam-dma-engine 8e04000.dma: num-ees unspecified in dt
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.207844] tcsr 194b000.tcsr: setting usb hs phy mode select = e700e7
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.207949] tcsr 1953000.ess_tcsr: setting ess interface select = 0
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.208040] tcsr 1949000.tcsr: setting wifi_glb_cfg = 41000000
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.208130] tcsr 1957000.tcsr: setting wifi_noc_memtype_m0_m2 = 2222222
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.208461] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.209079] msm_serial 78af000.serial: msm_serial: detected port #0
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.209127] msm_serial 78af000.serial: uartclk = 1843200
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.209198] 78af000.serial: ttyMSM0 at MMIO 0x78af000 (irq = 34, base_baud = 115200) is a MSM
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.209233] msm_serial: console setup on port #0
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.753532] printk: console [ttyMSM0] enabled
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.758686] msm_serial: driver initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.767721] loop: module loaded
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.768849] spi_qup 78b5000.spi: IN:block:16, fifo:64, OUT:block:16, fifo:64
Wed Dec  6 22:30:37 2023 kern.warn kernel: [    0.770859] spi-nor spi0.0: found xt25f128b, expected n25q128a11
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.777666] spi-nor spi0.0: xt25f128b (16384 Kbytes)
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.783117] 16 fixed-partitions partitions found on MTD device spi0.0
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.787907] Creating 16 MTD partitions on "spi0.0":
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.794271] 0x000000000000-0x000000040000 : "0:SBL1"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.799567] 0x000000040000-0x000000060000 : "0:MIBIB"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.804815] 0x000000060000-0x000000080000 : "0:BOOTCONFIG"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.809576] 0x000000080000-0x0000000a0000 : "0:BOOTCONFIG1"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.815035] 0x0000000a0000-0x000000100000 : "0:QSEE"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.820444] 0x000000100000-0x000000160000 : "0:QSEE_1"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.825659] 0x000000160000-0x000000170000 : "0:CDT"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.830570] 0x000000170000-0x000000180000 : "0:CDT_1"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.835425] 0x000000180000-0x000000190000 : "0:DDRPARAMS"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.840539] 0x000000190000-0x0000001a0000 : "0:APPSBLENV"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.846037] 0x0000001a0000-0x000000240000 : "0:APPSBL"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.851400] 0x000000240000-0x0000002e0000 : "0:APPSBL_1"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.856456] 0x0000002e0000-0x0000002f0000 : "0:ART"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.861836] 0x0000002f0000-0x000000300000 : "0:CONFIG"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.866484] 0x000000300000-0x000000310000 : "0:CONFIG_RW"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.871650] 0x000000310000-0x0000003a0000 : "0:EVENTSLOG"
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.883851] spi-nand spi0.1: XTX SPI NAND XT26G02A was found.
Wed Dec  6 22:30:37 2023 kern.info kernel: [    0.883901] spi-nand spi0.1: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 64
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.888940] 2 fixed-partitions partitions found on MTD device spi0.1
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.896799] Creating 2 MTD partitions on "spi0.1":
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    0.903110] 0x000000000000-0x000008000000 : "rootfs"
Wed Dec  6 22:30:37 2023 kern.info kernel: [    1.648249] mtd: setting mtd16 (rootfs) as root device
Wed Dec  6 22:30:37 2023 kern.alert kernel: [    1.649833] mtdsplit: no squashfs found in "rootfs"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    1.652315] 0x000008000000-0x000010000000 : "rootfs_1"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    1.652463] random: crng init done
Wed Dec  6 22:30:37 2023 kern.info kernel: [    2.431241] ESS reset ok!
Wed Dec  6 22:30:37 2023 kern.info kernel: [    2.505418] ESS reset ok!
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.259073] i2c /dev entries driver
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.262249] sdhci: Secure Digital Host Controller Interface driver
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.262287] sdhci: Copyright(c) Pierre Ossman
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.267718] sdhci-pltfm: SDHCI platform and OF driver helper
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.279075] NET: Registered protocol family 10
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.280672] Segment Routing with IPv6
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.282582] NET: Registered protocol family 17
Wed Dec  6 22:30:37 2023 kern.info kernel: [    3.286225] 8021q: 802.1Q VLAN Support v1.8
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    3.290617] Registering SWP/SWPB emulation handler
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    3.305871] ubi0: attaching mtd16
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    6.978887] ubi0: scanning is finished
Wed Dec  6 22:30:37 2023 kern.warn kernel: [    7.020094] ubi0 warning: ubi_eba_init: cannot reserve enough PEBs for bad PEB handling, reserved 10, need 37
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.021451] ubi0: attached mtd16 (name "rootfs", size 128 MiB)
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.029070] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.034754] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.041595] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.048493] ubi0: good PEBs: 1021, bad PEBs: 3, corrupted PEBs: 0
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.055246] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.061474] ubi0: max/mean erase counter: 7/4, WL threshold: 4096, image sequence number: 703414452
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.068620] ubi0: available PEBs: 0, total reserved PEBs: 1021, PEBs reserved for bad PEB handling: 10
Wed Dec  6 22:30:37 2023 kern.notice kernel: [    7.077591] ubi0: background thread "ubi_bgt0d" started, PID 143
Wed Dec  6 22:30:37 2023 kern.info kernel: [    7.078566] block ubiblock0_1: created from ubi0:1(rootfs)
Wed Dec  6 22:30:37 2023 kern.err kernel: [    7.094708] UBI error: block: can't add 'rootfs' volume, err=-17
Wed Dec  6 22:30:37 2023 kern.info kernel: [    7.121742] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
Wed Dec  6 22:30:37 2023 kern.info kernel: [    7.124062] Freeing unused kernel memory: 1024K
Wed Dec  6 22:30:37 2023 kern.info kernel: [    7.176401] Run /sbin/init as init process
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    7.176645]   with arguments:
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    7.176732]     /sbin/init
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    7.176804]   with environment:
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    7.176879]     HOME=/
Wed Dec  6 22:30:37 2023 kern.debug kernel: [    7.176957]     TERM=linux
Wed Dec  6 22:30:37 2023 user.info kernel: [    7.988096] init: Console is alive
Wed Dec  6 22:30:37 2023 user.info kernel: [    7.988399] init: - watchdog -
Wed Dec  6 22:30:37 2023 user.info kernel: [   11.670524] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   11.860303] genirq: irq_chip msmgpio did not update eff. affinity mask of irq 101
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   11.903582] STM32 supported protocol: 2
Wed Dec  6 22:30:37 2023 kern.info kernel: [   11.914180] r2ec 0-0074: probed
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   11.919145] SCSI subsystem initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   11.922828] uhci_hcd: USB Universal Host Controller Interface driver
Wed Dec  6 22:30:37 2023 kern.info kernel: [   11.926074] gpio-export soc:gpio-export: 5 gpio(s) exported
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.167587] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.167662] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.172466] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f665 hci version 0x100 quirks 0x0000000002010010
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.179624] xhci-hcd xhci-hcd.0.auto: irq 108, io mem 0x08a00000
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.189188] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.195213] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.200471] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.211488] hub 1-0:1.0: USB hub found
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.214699] hub 1-0:1.0: 1 port detected
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.218812] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.223070] hub 2-0:1.0: USB hub found
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.230545] hub 2-0:1.0: 1 port detected
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.234600] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.238150] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.243919] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220f665 hci version 0x100 quirks 0x0000000002010010
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.251052] xhci-hcd xhci-hcd.1.auto: irq 109, io mem 0x06000000
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.260575] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.266658] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.271909] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.281184] hub 3-0:1.0: USB hub found
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.286129] hub 3-0:1.0: 1 port detected
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.290249] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.294470] hub 4-0:1.0: USB hub found
Wed Dec  6 22:30:37 2023 kern.err kernel: [   12.301973] hub 4-0:1.0: config failed, hub doesn't have any ports! (err -19)
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.315545] usbcore: registered new interface driver usb-storage
Wed Dec  6 22:30:37 2023 user.info kernel: [   12.315886] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Wed Dec  6 22:30:37 2023 user.info kernel: [   12.324929] init: - preinit -
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.532527] usb 1-1: new high-speed USB device number 2 using xhci-hcd
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.752640] hub 1-1:1.0: USB hub found
Wed Dec  6 22:30:37 2023 kern.info kernel: [   12.753012] hub 1-1:1.0: 4 ports detected
Wed Dec  6 22:30:37 2023 user.info kernel: [   14.558003] mount_root: loading kmods from internal overlay
Wed Dec  6 22:30:37 2023 user.info kernel: [   14.614238] kmodloader: loading kernel modules from //etc/modules-boot.d/*
Wed Dec  6 22:30:37 2023 user.info kernel: [   14.624207] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   16.797022] UBIFS (ubi0:2): Mounting in unauthenticated mode
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   16.797337] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 277
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.010203] UBIFS (ubi0:2): recovery needed
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.478328] UBIFS (ubi0:2): recovery completed
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.478695] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.481742] UBIFS (ubi0:2): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.489774] UBIFS (ubi0:2): FS size: 103612416 bytes (98 MiB, 816 LEBs), journal size 5206016 bytes (4 MiB, 41 LEBs)
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.499612] UBIFS (ubi0:2): reserved for root: 4893869 bytes (4779 KiB)
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.510189] UBIFS (ubi0:2): media format: w5/r0 (latest is w5/r0), UUID 48C003A7-8233-4A55-B68D-A2315B3017D3, small LPT model
Wed Dec  6 22:30:37 2023 user.info kernel: [   17.529497] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Wed Dec  6 22:30:37 2023 user.info kernel: [   17.570186] block: extroot: not configured
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.570839] UBIFS (ubi0:2): un-mount UBI device 0
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.573454] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" stops
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.600395] UBIFS (ubi0:2): Mounting in unauthenticated mode
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   17.601890] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 278
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   18.012784] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   18.012893] UBIFS (ubi0:2): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   18.019681] UBIFS (ubi0:2): FS size: 103612416 bytes (98 MiB, 816 LEBs), journal size 5206016 bytes (4 MiB, 41 LEBs)
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   18.029678] UBIFS (ubi0:2): reserved for root: 4893869 bytes (4779 KiB)
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   18.040243] UBIFS (ubi0:2): media format: w5/r0 (latest is w5/r0), UUID 48C003A7-8233-4A55-B68D-A2315B3017D3, small LPT model
Wed Dec  6 22:30:37 2023 user.info kernel: [   19.915263] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Wed Dec  6 22:30:37 2023 user.info kernel: [   19.942574] block: extroot: not configured
Wed Dec  6 22:30:37 2023 user.info kernel: [   19.954334] mount_root: switching to ubifs overlay
Wed Dec  6 22:30:37 2023 user.warn kernel: [   20.060338] urandom-seed: Seeding with /etc/urandom.seed
Wed Dec  6 22:30:37 2023 user.info kernel: [   21.916841] procd: - early -
Wed Dec  6 22:30:37 2023 user.info kernel: [   21.916999] procd: - watchdog -
Wed Dec  6 22:30:37 2023 user.warn kernel: [   22.315381] [01-serial-symlink.sh] New device ttyS0 at /devices/platform/serial8250/tty/ttyS0 appeared!
Wed Dec  6 22:30:37 2023 user.warn kernel: [   22.449569] [01-serial-symlink.sh] New device ttyMSM0 at /devices/platform/soc/78af000.serial/tty/ttyMSM0 appeared!
Wed Dec  6 22:30:37 2023 user.warn kernel: [   22.564291] [01-serial-symlink.sh] New device ttyS1 at /devices/platform/serial8250/tty/ttyS1 appeared!
Wed Dec  6 22:30:37 2023 user.info kernel: [   22.613707] procd: - watchdog -
Wed Dec  6 22:30:37 2023 user.info kernel: [   22.620521] procd: - ubus -
Wed Dec  6 22:30:37 2023 user.info kernel: [   22.800415] procd: - init -
Wed Dec  6 22:30:37 2023 user.info kernel: [   24.825993] urngd: v1.0.2 started.
Wed Dec  6 22:30:37 2023 kern.notice kernel: [   25.000734] jffs2: notice: (554) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.272509] usb 3-1: new high-speed USB device number 2 using xhci-hcd
Wed Dec  6 22:30:37 2023 user.info kernel: [   25.449683] kmodloader: loading kernel modules from /etc/modules.d/*
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.515952] ntfs: driver 2.1.32 [Flags: R/O MODULE].
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.523027] NET: Registered protocol family 15
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.525573] Initializing XFRM netlink socket
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.528734] tun: Universal TUN/TAP device driver, 1.6
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.552142] l2tp_core: L2TP core driver, V2.0
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.553716] l2tp_netlink: L2TP netlink interface
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.557409] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.570365] l2tp_eth: L2TP ethernet pseudowire support (L2TPv3)
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.572155] l2tp_ip: L2TP IP encapsulation support (L2TPv3)
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.576614] l2tp_ip6: L2TP IP encapsulation support for IPv6 (L2TPv3)
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.583556] gre: GRE over IPv4 demultiplexor driver
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.589122] ip_gre: GRE over IPv4 tunneling driver
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.597951] ip6_gre: GRE over IPv6 tunneling driver
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.657350] hid: raw HID events driver (C) Jiri Kosina
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.658982] GACT probability on
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.663184] Mirror/redirect action on
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.673672] u32 classifier
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.673714]     input device check on
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.675296]     Actions configured
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.691011] fuse: init (API version 7.32)
Wed Dec  6 22:30:37 2023 kern.info kernel: [   25.720108] PPP generic driver version 2.4.2
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   25.980316] ess-switch dts node number: 1
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   25.980465] ess-switch DT exist!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   25.983443] switch_access_mode: local bus
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   25.986635] mac mode = 0x0
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   25.990537] mac mode1 doesn't exit!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   25.993239] mac mode2 doesn't exit!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   25.996662] ess-uniphy DT doesn't exist!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.000018] cannot find port_scheduler_resource node
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.004217] qcom,port_phyinfo DT doesn't exist!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.009151] mdio DT exist!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.013424] switchreg_base_addr: 0xc000000
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.016148] switchreg_size: 0x80000
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.020266] ess-psgmii DT exist!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.023663] current dts led_source_num is 0
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.090430] qca probe malibu phy driver succeeded!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.126140] Initializing DESS!!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.126477] Initializing DESS Done!!
Wed Dec  6 22:30:37 2023 kern.warn kernel: [   26.128180] qca-ssdk module init succeeded!
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.167755] usbcore: registered new interface driver usbserial_generic
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.167878] usbserial: USB Serial support registered for generic
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.175072] usbcore: registered new interface driver cypress_reconf
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.179529] usbcore: registered new interface driver cypress_serial
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.185553] usbserial: USB Serial support registered for CY7C65213
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.201895] usbcore: registered new interface driver ark3116
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.202034] usbserial: USB Serial support registered for ark3116
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.208665] usbcore: registered new interface driver belkin_sa
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.212918] usbserial: USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.285621] Bluetooth: Core ver 2.22
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.285812] NET: Registered protocol family 31
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.288302] Bluetooth: HCI device and connection manager initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.292609] Bluetooth: HCI socket layer initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.299076] Bluetooth: L2CAP socket layer initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.303752] Bluetooth: SCO socket layer initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.310576] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.313632] Bluetooth: BNEP filters: protocol multicast
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.319146] Bluetooth: BNEP socket layer initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.329590] usbcore: registered new interface driver btusb
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.331772] usbcore: registered new interface driver cdc_acm
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.334632] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.342056] usbcore: registered new interface driver cdc_wdm
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.349538] usbcore: registered new interface driver ch341
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.354197] usbserial: USB Serial support registered for ch341-uart
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.360876] usbcore: registered new interface driver usb_ch343
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.365543] ch343: USB serial driver for ch342/ch343/ch344/ch347/ch9101/ch9102/ch9103/ch9104, etc.
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.371371] ch343: V1.5 On 2022.12
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.384626] usbcore: registered new interface driver cp210x
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.384794] usbserial: USB Serial support registered for cp210x
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.392223] usbcore: registered new interface driver cypress_m8
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.395320] usbserial: USB Serial support registered for DeLorme Earthmate USB
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.401178] usbserial: USB Serial support registered for HID->COM RS232 Adapter
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.408515] usbserial: USB Serial support registered for Nokia CA-42 V2 Adapter
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.438118] usbcore: registered new interface driver ftdi_sio
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.438267] usbserial: USB Serial support registered for FTDI USB Serial Device
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.445231] Bluetooth: HCI UART driver ver 2.3
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.449981] Bluetooth: HCI UART protocol H4 registered
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.454520] Bluetooth: HCI UART protocol BCSP registered
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.461504] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.465151] Bluetooth: HIDP socket layer initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.626925] usbcore: registered new interface driver pl2303
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.627040] usbserial: USB Serial support registered for pl2303
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.635760] PPP MPPE Compression module registered
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.638727] NET: Registered protocol family 24
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.643553] PPTP driver version 0.8.5
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.649740] Bluetooth: RFCOMM TTY layer initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.650258] Bluetooth: RFCOMM socket layer initialized
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.655086] Bluetooth: RFCOMM ver 1.11
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.675162] usbcore: registered new interface driver usblp
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.725326] xt_time: kernel timezone is -0000
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.737207] l2tp_ppp: PPPoL2TP kernel driver, V2.0
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.741169] usbcore: registered new interface driver option
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.741289] usbserial: USB Serial support registered for GSM modem (1-port)
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.748428] option 3-1:1.0: GSM modem (1-port) converter detected
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.753886] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.760380] option 3-1:1.1: GSM modem (1-port) converter detected
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.766759] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.772803] option 3-1:1.2: GSM modem (1-port) converter detected
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.779545] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB2
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.785694] option 3-1:1.3: GSM modem (1-port) converter detected
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.792364] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB3
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.808178] qmi_wwan 3-1:1.4: cdc-wdm0: USB WDM device
Wed Dec  6 22:30:37 2023 user.warn kernel: [   26.808930] [01-serial-symlink.sh] New device ttyUSB0 at /devices/platform/soc/60f8800.usb2/6000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1:1.0/ttyUSB0/tty/ttyUSB0 appeared!
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.817147] qmi_wwan 3-1:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.1.auto-1, WWAN/QMI device, fa:38:bd:98:3d:8d
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.827448] usbcore: registered new interface driver qmi_wwan
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.850270] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
Wed Dec  6 22:30:37 2023 kern.info kernel: [   26.850335] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld . All Rights Reserved.
Wed Dec  6 22:30:37 2023 user.info kernel: [   26.857619] kmodloader: done loading kernel modules from /etc/modules.d/*
Wed Dec  6 22:30:37 2023 user.warn kernel: [   27.053486] [01-serial-symlink.sh] New device ttyUSB1 at /devices/platform/soc/60f8800.usb2/6000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1:1.1/ttyUSB1/tty/ttyUSB1 appeared!
Wed Dec  6 22:30:37 2023 user.warn kernel: [   27.273606] [01-serial-symlink.sh] New device ttyUSB2 at /devices/platform/soc/60f8800.usb2/6000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1:1.2/ttyUSB2/tty/ttyUSB2 appeared!
Wed Dec  6 22:30:37 2023 user.warn kernel: [   27.461082] [01-serial-symlink.sh] New device ttyUSB3 at /devices/platform/soc/60f8800.usb2/6000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1:1.3/ttyUSB3/tty/ttyUSB3 appeared!
Wed Dec  6 22:30:38 2023 daemon.notice procd: /etc/rc.d/S06firewall:
Wed Dec  6 22:30:38 2023 daemon.notice procd: /etc/rc.d/S06firewall:  SSDK Init OK!
Wed Dec  6 22:30:38 2023 daemon.notice procd: /etc/rc.d/S06firewall: operation done.
Wed Dec  6 22:30:38 2023 daemon.notice procd: /etc/rc.d/S06firewall:
Wed Dec  6 22:30:38 2023 kern.debug kernel: [   29.952814] nf_register_net_hook 0
Wed Dec  6 22:30:38 2023 kern.info kernel: [   29.957127] qssdk: hnat is enabled
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: bonding
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: 8021ad
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: 8021q
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: macvlan
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: veth
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: bridge
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: Network device
Wed Dec  6 22:30:40 2023 user.notice : Added device handler type: tunnel
Wed Dec  6 22:30:41 2023 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Wed Dec  6 22:30:41 2023 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: Connected to system UBus
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: started, version 2.85 cachesize 150
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-regex no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: UBus support enabled: connected to system bus
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: using only locally-known addresses for domain test
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: using only locally-known addresses for domain onion
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: using only locally-known addresses for domain localhost
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: using only locally-known addresses for domain local
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: using only locally-known addresses for domain invalid
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: using only locally-known addresses for domain bind
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: using only locally-known addresses for domain lan
Wed Dec  6 22:30:41 2023 daemon.warn dnsmasq[1515]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: read /etc/hosts - 4 addresses
Wed Dec  6 22:30:41 2023 daemon.info dnsmasq[1515]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Wed Dec  6 22:30:43 2023 daemon.info gsmd[1694]: gsmd-ng init
Wed Dec  6 22:30:43 2023 daemon.info gsmd[1694]: gsmd-ng canary build git#4c2e2f7ffb
Wed Dec  6 22:30:43 2023 daemon.info gsmd[1694]:
Wed Dec  6 22:30:43 2023 daemon.info gsmd[1694]: AT traffic support:  yes
Wed Dec  6 22:30:43 2023 daemon.info gsmd[1694]: Baseband feature support: no
Wed Dec  6 22:30:43 2023 daemon.info gsmd[1694]:
Wed Dec  6 22:30:43 2023 daemon.info gsmd[1694]: gsmd-ng running
Wed Dec  6 22:30:43 2023 daemon.notice wpa_supplicant[1572]: Successfully initialized wpa_supplicant
Wed Dec  6 22:30:44 2023 kern.info kernel: [   35.668285] br-lan: port 1(eth0) entered blocking state
Wed Dec  6 22:30:44 2023 kern.info kernel: [   35.668343] br-lan: port 1(eth0) entered disabled state
Wed Dec  6 22:30:44 2023 kern.info kernel: [   35.672780] device eth0 entered promiscuous mode
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'lan' is enabled
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'lan' is setting up now
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'lan' is now up
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'loopback' is enabled
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'loopback' is setting up now
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'loopback' is now up
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'wan' is enabled
Wed Dec  6 22:30:44 2023 kern.info kernel: [   35.768228] ess_edma c080000.edma eth1: Link is Down
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Network device 'eth0' link is up
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Network device 'lo' link is up
Wed Dec  6 22:30:44 2023 daemon.notice netifd: Interface 'loopback' has link connectivity
Wed Dec  6 22:30:45 2023 kern.info kernel: [   36.712611] br-lan: port 1(eth0) entered blocking state
Wed Dec  6 22:30:45 2023 kern.info kernel: [   36.712671] br-lan: port 1(eth0) entered forwarding state
Wed Dec  6 22:30:45 2023 kern.info kernel: [   36.717765] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Wed Dec  6 22:30:45 2023 daemon.notice netifd: bridge 'br-lan' link is up
Wed Dec  6 22:30:45 2023 daemon.notice netifd: Interface 'lan' has link connectivity
Wed Dec  6 22:30:46 2023 user.notice simcard: Setting SIM slot to 1
Wed Dec  6 22:30:46 2023 user.warn mwan3-hotplug[1820]: hotplug called on lan before mwan3 has been set up
Wed Dec  6 22:30:47 2023 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Wed Dec  6 22:30:47 2023 daemon.info mobifd: [gsm.modem0] Starting modem settings init
Wed Dec  6 22:30:48 2023 user.warn mwan3-hotplug[2748]: hotplug called on loopback before mwan3 has been set up
Wed Dec  6 22:30:49 2023 authpriv.info dropbear[3070]: Not backgrounding
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[1515]: exiting on receipt of SIGTERM
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: Connected to system UBus
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: started, version 2.85 cachesize 150
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-regex no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: UBus support enabled: connected to system bus
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq-dhcp[3310]: DHCP, IP range 192.168.1.100 -- 192.168.1.150, lease time 12h
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: using only locally-known addresses for domain test
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: using only locally-known addresses for domain onion
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: using only locally-known addresses for domain localhost
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: using only locally-known addresses for domain local
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: using only locally-known addresses for domain invalid
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: using only locally-known addresses for domain bind
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: using only locally-known addresses for domain lan
Wed Dec  6 22:30:50 2023 daemon.warn dnsmasq[3310]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: read /etc/hosts - 4 addresses
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq-dhcp[3310]: read /etc/ethers - 0 addresses
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: read /etc/hosts - 4 addresses
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq[3310]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Dec  6 22:30:50 2023 daemon.info dnsmasq-dhcp[3310]: read /etc/ethers - 0 addresses
Wed Dec  6 22:30:51 2023 daemon.info gsmd[1694]: Modem `3-1 [2c7c:0306]` URC Event: ESM reject cause => Requested service option not subscribed
Wed Dec  6 22:30:51 2023 daemon.info dnsmasq[3310]: read /etc/hosts - 4 addresses
Wed Dec  6 22:30:51 2023 daemon.info dnsmasq[3310]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Dec  6 22:30:51 2023 daemon.info dnsmasq-dhcp[3310]: read /etc/ethers - 0 addresses
Wed Dec  6 22:30:51 2023 user.info kernel: [   42.975449] kmodloader: loading kernel modules from /etc/modules-late.d/*
Wed Dec  6 22:30:51 2023 user.info kernel: [   42.975910] kmodloader: done loading kernel modules from /etc/modules-late.d/*
Wed Dec  6 22:30:51 2023 kern.notice ip_blockd service is enabled, initialized firewall rules
Wed Dec  6 22:30:52 2023 kern.notice Port link state of port CPU/WiFi changed to UP
Wed Dec  6 22:30:52 2023 kern.notice Port speed for port CPU/WiFi changed to 1000 baseT
Wed Dec  6 22:30:52 2023 kern.notice Port link state of port LAN1 changed to UP
Wed Dec  6 22:30:52 2023 kern.notice Port speed for port LAN1 changed to 1000 baseT
Wed Dec  6 22:30:52 2023 daemon.info mobifd: [gsm.modem0] SIM is ready
Wed Dec  6 22:30:52 2023 daemon.info mobifd: [gsm.modem0] Config reload initiated
Wed Dec  6 22:30:52 2023 daemon.info mobifd: [gsm.modem0] SIM is ready
Wed Dec  6 22:30:53 2023 user.info : Starting database size optimization...
Wed Dec  6 22:30:54 2023 cron.err crond[3924]: crond (busybox 1.34.1) started, log level 5
Wed Dec  6 22:30:54 2023 daemon.info mobifd: [gsm.modem0] Modem settings init completed
Wed Dec  6 22:30:54 2023 daemon.info mobifd: [gsm.modem0] Starting connection setup
Wed Dec  6 22:30:54 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with "15s" of timeout
Wed Dec  6 22:30:54 2023 daemon.info mobifd: [gsm.modem0] Connected to operator "HT HR HT HR"
Wed Dec  6 22:30:55 2023 daemon.info mobifd: [gsm.modem0] -CFUN- Functionality: "Full"
Wed Dec  6 22:30:55 2023 daemon.info mobifd: [gsm.modem0] -COPS- Mode: "Auto", operator: "HT HR HT HR"
Wed Dec  6 22:30:55 2023 daemon.info mobifd: [gsm.modem0] -CREG- Mode: "Enabled (with location information)", status: "Registered, home", LAC: "3000", cell ID: "140830209", technology: "E-UTRAN"
Wed Dec  6 22:30:55 2023 daemon.info mobifd: [gsm.modem0] -CGREG- Mode: "Enabled (with location information)", status: "Registered, home", LAC: "3000", cell ID: "140830209", technology: "E-UTRAN"
Wed Dec  6 22:30:55 2023 daemon.info mobifd: [gsm.modem0] -CEREG- Mode: "Enabled (with location information)", status: "Registered, home", LAC: "3000", cell ID: "140830209", technology: "E-UTRAN"
Wed Dec  6 22:30:55 2023 cron.err crond[4158]: crond (busybox 1.34.1) started, log level 5
Wed Dec  6 22:30:55 2023 daemon.err insmod: module is already loaded - slhc
Wed Dec  6 22:30:55 2023 daemon.err insmod: module is already loaded - crc-ccitt
Wed Dec  6 22:30:55 2023 daemon.err insmod: module is already loaded - ppp_generic
Wed Dec  6 22:30:55 2023 daemon.err insmod: module is already loaded - ppp_async
Wed Dec  6 22:30:55 2023 daemon.err insmod: module is already loaded - ppp_mppe
Wed Dec  6 22:30:55 2023 daemon.info mobifd: [gsm.modem0] IP address on PDP context "1": "10.252.130.57"
Wed Dec  6 22:30:55 2023 daemon.notice netifd: Interface 'mob1s1a1' is setting up now
Wed Dec  6 22:30:55 2023 daemon.notice netifd: mob1s1a1 (4240): wwan[4240] Using wwan usb device on bus 3-1
Wed Dec  6 22:30:55 2023 daemon.notice netifd: mob1s1a1 (4240): wwan[4240] Using proto:qmux device:/dev/cdc-wdm0 iface:wwan0 desc:Quectel EG06
Wed Dec  6 22:30:56 2023 daemon.notice netifd: mob1s1a1 (4240): Quering active sim position
Wed Dec  6 22:30:56 2023 daemon.notice netifd: mob1s1a1 (4240): Calculated qmimux ifname: qmimux0
Wed Dec  6 22:30:57 2023 user.notice root: uqmi -d /dev/cdc-wdm0 --timeout 3000 --wda-set-data-format --link-layer-protocol raw-ip --ul-protocol qmap --dl-protocol qmap --dl-max-datagrams 32 --dl-datagram-max-size 16384 --ul-max-datagrams 11 --ul-datagram-max-size 8912 --dl-min-padding 0
Wed Dec  6 22:30:57 2023 daemon.notice netifd: mob1s1a1 (4240): Starting network mob1s1a1 using APN: internet.ht.hr
Wed Dec  6 22:30:57 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --set-client-id wds,21 --release-client-id wds --modify-profile --profile-identifier 3gpp,1 --profile-name profile1 --roaming-disallowed-flag no    --auth-type pap  --apn internet.ht.hr  --pdp-type ip
Wed Dec  6 22:30:58 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --get-client-id wds
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 21
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): cid4: 21
Wed Dec  6 22:30:58 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --wds-bind-mux-data-port --mux-id 1 --ep-iface-number 4 --set-client-id wds,21
Wed Dec  6 22:30:58 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --set-ip-family ipv4 --set-client-id wds,21
Wed Dec  6 22:30:58 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --set-client-id wds,21 --start-network --apn internet.ht.hr --profile 1  --auth-type pap --username  --password
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): pdh4: -629723024
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): -629723024
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): Setting up qmimux0
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): Setting dynamic MTU: 1430 on qmimux0
Wed Dec  6 22:30:58 2023 daemon.notice netifd: Interface 'mob1s1a1' is now up
Wed Dec  6 22:30:58 2023 daemon.notice netifd: Network device 'wwan0' link is up
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): {
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	"pdp-type": "ipv4",
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	"ip-family": "ipv4",
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	"mtu": 1430,
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	"ipv4": {
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 		"ip": "10.252.130.57",
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 		"dns1": "195.29.247.161",
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 		"dns2": "195.29.247.162",
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 		"gateway": "10.252.130.58",
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 		"subnet": "255.255.255.252"
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	},
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	"ipv6": {
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240):
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	},
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	"domain-names": {
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240):
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): 	}
Wed Dec  6 22:30:58 2023 daemon.notice netifd: mob1s1a1 (4240): }
Wed Dec  6 22:30:58 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is enabled
Wed Dec  6 22:30:58 2023 daemon.notice netifd: Network device 'qmimux0' link is up
Wed Dec  6 22:30:58 2023 daemon.notice netifd: Interface 'mob1s1a1_4' has link connectivity
Wed Dec  6 22:30:58 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is setting up now
Wed Dec  6 22:30:58 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is now up
Wed Dec  6 22:30:58 2023 daemon.info mobifd: Method of interface 'mob1s1a1' is "bridge". Skipping Ping To DNS functionality
Wed Dec  6 22:30:58 2023 daemon.info mobifd: Connection setup completed for 'mob1s1a1'
Wed Dec  6 22:30:59 2023 daemon.notice netifd: Interface 'mobile_bridge' is enabled
Wed Dec  6 22:30:59 2023 daemon.notice netifd: Interface 'mobile_bridge' is setting up now
Wed Dec  6 22:30:59 2023 daemon.notice netifd: Interface 'mobile_bridge' is now up
Wed Dec  6 22:30:59 2023 daemon.notice netifd: Interface 'mobile_bridge' has link connectivity
Wed Dec  6 22:30:59 2023 user.warn mwan3-hotplug[4903]: hotplug called on mob1s1a1 before mwan3 has been set up
Wed Dec  6 22:31:00 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (wwan0)
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq-dhcp[3310]: DHCPDISCOVER(br-lan) c8:7f:54:bf:d5:d0
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq-dhcp[3310]: DHCPOFFER(br-lan) 192.168.1.139 c8:7f:54:bf:d5:d0
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[3310]: exiting on receipt of SIGTERM
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: Connected to system UBus
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: started, version 2.85 cachesize 150
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-regex no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: UBus support enabled: connected to system bus
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq-dhcp[5385]: DHCP, IP range 192.168.1.100 -- 192.168.1.150, lease time 12h
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq-dhcp[5385]: DHCP, static leases only on 10.252.130.57, lease time 1h
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using only locally-known addresses for domain test
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using only locally-known addresses for domain onion
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using only locally-known addresses for domain localhost
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using only locally-known addresses for domain local
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using only locally-known addresses for domain invalid
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using only locally-known addresses for domain bind
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using nameserver 195.29.247.162#53
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using nameserver 195.29.247.161#53
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: using only locally-known addresses for domain lan
Wed Dec  6 22:31:00 2023 daemon.warn dnsmasq[5385]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: read /etc/hosts - 4 addresses
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq[5385]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Dec  6 22:31:00 2023 daemon.info dnsmasq-dhcp[5385]: read /etc/ethers - 0 addresses
Wed Dec  6 22:31:02 2023 daemon.info dnsmasq[5385]: read /etc/hosts - 4 addresses
Wed Dec  6 22:31:02 2023 daemon.info dnsmasq[5385]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Dec  6 22:31:02 2023 daemon.info dnsmasq-dhcp[5385]: read /etc/ethers - 0 addresses
Wed Dec  6 22:31:03 2023 user.warn mwan3-hotplug[5798]: hotplug called on mob1s1a1_4 before mwan3 has been set up
Wed Dec  6 22:31:03 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (qmimux0)
Wed Dec  6 22:31:05 2023 cron.err crond[6455]: crond (busybox 1.34.1) started, log level 5
Wed Dec  6 22:31:05 2023 daemon.info mdcollectd: Interface already registered
Wed Dec  6 22:31:05 2023 kern.notice Port link state of port LAN1 changed to DOWN
Wed Dec  6 22:31:05 2023 daemon.info dnsmasq[5385]: read /etc/hosts - 4 addresses
Wed Dec  6 22:31:05 2023 daemon.info dnsmasq[5385]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Dec  6 22:31:05 2023 daemon.info dnsmasq-dhcp[5385]: read /etc/ethers - 0 addresses
Wed Dec  6 22:31:06 2023 kern.info Mobile data connected (internal modem)
Wed Dec  6 22:31:06 2023 kern.info Joined LTE network (internal modem)
Wed Dec  6 22:31:06 2023 kern.info Connected to HT HR HT HR operator (internal modem)
Wed Dec  6 22:31:07 2023 user.notice firewall: Reloading firewall due to ifupdate of mob1s1a1 (wwan0)
Wed Dec  6 22:31:07 2023 kern.notice Device startup completed
Wed Dec  6 22:31:08 2023 user.warn mwan3-hotplug[7245]: hotplug called on mobile_bridge before mwan3 has been set up
Wed Dec  6 22:31:08 2023 kern.notice Port link state of port LAN1 changed to UP
Wed Dec  6 22:31:08 2023 kern.notice Port speed for port LAN1 changed to 1000 baseT
Wed Dec  6 22:31:12 2023 cron.err crond[8615]: crond (busybox 1.34.1) started, log level 5
Wed Dec  6 22:31:14 2023 daemon.info procd: - init complete -
Wed Dec  6 22:31:15 2023 daemon.info dfota[7521]: Searching for WAN...
Wed Dec  6 22:31:15 2023 daemon.info dfota[7521]: WAN found on interface: mobile_bridge
Wed Dec  6 22:31:15 2023 daemon.info dfota[7521]: Preparing for gsm.modem0 update!
Wed Dec  6 22:31:15 2023 daemon.info dfota[7521]: Searching for updates...
Wed Dec  6 22:31:16 2023 daemon.info dnsmasq-dhcp[5385]: DHCPDISCOVER(br-lan) c8:7f:54:bf:d5:d0
Wed Dec  6 22:31:16 2023 daemon.info dnsmasq-dhcp[5385]: DHCPOFFER(br-lan) 10.252.130.57 c8:7f:54:bf:d5:d0
Wed Dec  6 22:31:16 2023 daemon.info dnsmasq-dhcp[5385]: DHCPREQUEST(br-lan) 10.252.130.57 c8:7f:54:bf:d5:d0
Wed Dec  6 22:31:16 2023 daemon.info dnsmasq-dhcp[5385]: DHCPACK(br-lan) 10.252.130.57 c8:7f:54:bf:d5:d0
Wed Dec  6 22:31:17 2023 user.info : Finished database optimization
Wed Dec  6 22:31:30 2023 daemon.info dfota[7521]: Connection error to FOTA server! ErrorCode: 169
Wed Dec  6 22:31:31 2023 daemon.info dfota[7521]: No update found!
Wed Dec  6 22:31:31 2023 cron.err crond[9264]: crond (busybox 1.34.1) started, log level 5
Wed Dec  6 22:31:32 2023 cron.err crond[9390]: crond (busybox 1.34.1) started, log level 5
Wed Dec  6 22:31:32 2023 daemon.info dfota[7521]: Update script done!
Wed Dec  6 22:31:44 2023 kern.notice Password auth succeeded for admin on HTTP from 10.252.130.57
Wed Dec  6 22:31:44 2023 daemon.err uhttpd[2760]: vuci: accepted login for admin from 10.252.130.57

DHCP na LANu sam ostavio upaljenog.
Ovo su postavke za mob1sa1 u bridge modu:

[Nikky]

Trebaš postići situaciju da je WAN Asusa IP = 10.x.y.z kao na ovom primjeru,



to je ono šta trebaš, tada Asus i cijela mreža može na Internet.
Važno je da provjeriš / potvrdiš MAC adresu WAN porta na Asusu jer to unosiš u odg. polje Teltonike.

Umjesto Bridge mode možeš probati sa Passthrough mode, podešava se na istom mjestu.


Da slučajno nemaš istovremeno spojen PC i WAN Asusa na Teltoniku ?
Po onim uputama / napomenama samo prvi klijent će se uredno spojiti i dobiti javnu IP adresu ......

Napravi slijedeće:
- spoji PC na Teltoniku i odradi šta trebaš za konfig + Save + Reboot
- dok ide Reboot ištekaj PC i spoji WAN Asusa na Teltoniku i ništa drugo
- ako zakasniš samo ugasi napajanje Teltonike, sačekaj 5 sec., upali je

Kao zadnja varijanta, provjeri koja je FW verzija u uređaju a koja na supportu,
ako ima noviji moguće da su i štagod popravili ...

Javi rezultat

[xlr]

Imao sam nesto slicno kada me zaj kabel izmedju modema i Asusa.

Probaj dvije stvari, promjeni kabel i na Asusu ugasi WAN - dual WAN opciju iako je ne koristis trenutno.

Nazalost ne mogu puno pomoci oko Teltonike.

[Nikky]

Evo nastavak,
zadnji FW za RUT09 je RUTX_R_00.07.05.4 > https://firmware.teltonika-networks....05.4_WEBUI.bin
pa ga ubaci ako već nije. Pazi da odradiš kako treba, da ga ne zbrikaš.

Postoji opcija da prilikom ubacivanja novog FW da NE čuva prethodne postavke (making sure NOT to keep settings), pa odradi tako.

Možda treba nakon ubacivanja odraditi factory reset pa tek onda konfig.
Prije ubacivanja novog FW svakako slikaj / zapiši postavke vezane za WWAN (4g) konekciju (ono APN, dial broj i ostalo...).

Možda pomognu upute iz predzadnjeg posta sa ove stranice > https://community.teltonika-networks...ters-have-used
očito nisi jedini sa tim problemom.

Par interesantnih detalja iz tih uputa:
- ovo oko mijenjanja IP adrese ne trebaš nužno slijediti jer si u prethodnim koracima postavio da budu različite na Teltonici i Asusu
- piše da treba čekati 5 min. nakon podešavanja i reboota pa tek onda spojiti WAN Asusa
- svugdje u Teltonici pogasi TCP/IP v6 i odaberi da samo koristi v4

To be continued

[Bubba]

@Neo-ST svakako isprobaj i Merlin fork Asusovog firmwarea, sto nece rijesiti neke tvoje inicijalne probleme koje imas, ali kada njih rijesis, napravit ces od tog uredjaja 3 puta kvalitetniju igracku!

https://www.asuswrt-merlin.net/

[Neo-ST]

Autor Cuky

Ovo ti je sve ok podeseno.

Na ovo bih samo upalio dmz na teltonici za asusovu ip adresu (sa prilozene slike je to 192.168.1.139) te rezervirao tu ip adresu na njenom dhcp serveru tako da ne skoci na neku drugu.

A šta je sad pak DMZ? Mislim pročitao sam ali jel to potrebno za moj slučaj ?
Također, šta ovde odaberem kad palim DMZ:



Ovaj prvi je Teltonika, drugi je Asus.

Autor Cuky

Bridge nemas potrebe paliti.

Eto vraga...kako sad ovo? Drugi kažu da obavezno stavim u bridge mode radi double NAT-a koji može stvarati probleme...

Autor Cuky

I normalno je da imas dhcp server na oba rutera. Kada asusa spojis na teltoniku nesto mu mora dat adresu (osim ako je nisi fizicki fiksirao na asus ruteru). I isto tako asusov ruter dijeli adrese uredajima koji se spoje na njega sa svog dhcp servera. Najnormalnije ponasanje.

E hvala na ovome, tek sad mi je jasno puno toga. A baš ima logike, nego netko ti treba to ovako laički napisat da shvatiš
Sad sam ugasio DHCP server na Teltonici i postavio WAN IP od Asusa na statičnu .1.10 adresu (vidljivo gore na slici)...i sve radi

Autor Nikky

Trebaš postići situaciju da je WAN Asusa IP = 10.x.y.z kao na ovom primjeru,



to je ono šta trebaš, tada Asus i cijela mreža može na Internet.
Važno je da provjeriš / potvrdiš MAC adresu WAN porta na Asusu jer to unosiš u odg. polje Teltonike.

To kužim i MAC adresu sam ispravno kopirao, ali ne radi dobro.

Autor Nikky

Umjesto Bridge mode možeš probati sa Passthrough mode, podešava se na istom mjestu.

E jbga sad, nemam pojma šta je taj passthrough. Čitao sam ali ne kužim baš razliku.

Autor Nikky

Da slučajno nemaš istovremeno spojen PC i WAN Asusa na Teltoniku ?
Po onim uputama / napomenama samo prvi klijent će se uredno spojiti i dobiti javnu IP adresu ......

Ne, PC je spojen na switch, kao i Asus.
Jedino je Teltonika uštekana direktno u Asusa u njegov WAN port.

Autor xlr

Imao sam nesto slicno kada me zaj kabel izmedju modema i Asusa.

Probaj dvije stvari, promjeni kabel i na Asusu ugasi WAN - dual WAN opciju iako je ne koristis trenutno.

Nazalost ne mogu puno pomoci oko Teltonike.

Nije do kabela, novi su i provjereni. Hvala svejedno.

Autor Nikky

Evo nastavak,
zadnji FW za RUT09 je RUTX_R_00.07.05.4 > https://firmware.teltonika-networks....05.4_WEBUI.bin
pa ga ubaci ako već nije. Pazi da odradiš kako treba, da ga ne zbrikaš.

Postoji opcija da prilikom ubacivanja novog FW da NE čuva prethodne postavke (making sure NOT to keep settings), pa odradi tako.

Možda treba nakon ubacivanja odraditi factory reset pa tek onda konfig.
Prije ubacivanja novog FW svakako slikaj / zapiši postavke vezane za WWAN (4g) konekciju (ono APN, dial broj i ostalo...).

Već je zadnji firmware unutra, mogu je jedino probat factory resetat...

Autor Nikky

Možda pomognu upute iz predzadnjeg posta sa ove stranice > https://community.teltonika-networks...ters-have-used
očito nisi jedini sa tim problemom.

Par interesantnih detalja iz tih uputa:
- ovo oko mijenjanja IP adrese ne trebaš nužno slijediti jer si u prethodnim koracima postavio da budu različite na Teltonici i Asusu
- piše da treba čekati 5 min. nakon podešavanja i reboota pa tek onda spojiti WAN Asusa
- svugdje u Teltonici pogasi TCP/IP v6 i odaberi da samo koristi v4

To be continued

Po tim upustvima sam i radio...i ne radi dobro.
Jedino nisam odradio ovaj dio sa flashanjem fw-a bez da čuva postavke, jer je došla sa zadnjim fw, pa jedino šta još nisam probao je factory reset.

Autor Bubba

@Neo-ST svakako isprobaj i Merlin fork Asusovog firmwarea, sto nece rijesiti neke tvoje inicijalne probleme koje imas, ali kada njih rijesis, napravit ces od tog uredjaja 3 puta kvalitetniju igracku!

https://www.asuswrt-merlin.net/

Budem, čitao sam o njemu ali dok ne riješim da mi osnove mreže rade po PS-u to će pričekati. Hvala svejedno

[Cuky]

Na teltonici - upali DMZ (enable), odaberi adresu od asusa (192.168.1.10) i save/apply.

I to je to.

Uz uvjet da nemas aktivan cgnat svi servisi za koje napravis port forward na asusu (ako ti to uopce treba) ce biti dostupni s interneta.

[Neo-ST]

Da zaključim ovu priču...

Teltonika ima dva bridge moda. Jedan je "bridge", drugi "passthrough".
Nemam pojma točno u čemu je razlika, ja je nisam vidio.
Njihova definicija:

Bridge - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.

Passthrough - in this mode the RUTX09 shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of RUTX09 instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.

Anyway, u bridge modu ništa ne radi, koliko god pokušavao. Veza stalno puca.
U Passthrough sve radi i ponaša se isto kao bridge. Asus dobio WAN IP i sve to...

Kad sam pitao na Teltonika forumu zašto mi ne radi bridge nego passthrough, ovo je njihovo objašnjenje:



Now my question is, what’s so different with Passthrough mode that it works, and Bridge doesn’t ?

Hi,

Bridge Mode is about connecting separate networks seamlessly, while Passthrough Mode allows specific devices to bypass the router’s network functions for direct access or management. The choice between them depends on the network architecture and the specific requirements of your setup.

Regards,

So, is my connection now actually bridged ?

Hi,

As long as your end device is getting the WAN IP of your SIM, configuration for Bridge Mode is done.

Regards,

Out of curiosity can I ask, why doesn’t bridge mode work in my environment then? It’s a simple home network, RUTX09 - Router - Devices.
Is it some hardware fault with RUTX09, a problem with my ISP or my router?

Hi,

Since you want to bridge the IP address of your SIM to a particular device (ASUS), Passthrough is preferable. It is commonly used when you have a specific device (like a server or another router) that needs a public IP address and requires direct access to the internet without any interference from the Teltonika router.

Hope this clears your doubts :blush:

Regards,

Ovo su sada brzine koje dobivam kada napokon sve radi kako treba:

[Nikky]

Pa rekoh odma pri početku da isprobaš Passthrough mode.
Ajde neka, bitno da je blem riješen

[axo]

Pozdrav,

da ne otvaram novu temu jer vezano za asus ruter.

Imam asus xt8 sa USB 3.1 Gen 1 x 1 te novi crucial x9 sa USB 3.2 Gen-2 (10Gb/s) te stavim u ruteru na usb mode: usb 2,0 on prepozna disk te kada ga prebacim na usb 3,0 on ga ne prepozna.


dali je možda problem u kompabilnosti usba?

Ima netko ideju?

Ruter na zadnjoj verziji.

[Prezime]

Jel imas neki drugi USB 3.x disk/stik da probas?

Nevezano za tvoj slucaj, ali neki Android boxovi sa USB 3.0 ne prepoznaju jedan moj 3.0 USB SSDisk (Sandisk -> na 2.0 ga prepoznaju), dok vecina drugih ga prepoznaje uredno...

Edit, ako imas priruci neki USB 3.x hub probaj ih spojit preko njega.

[Nikky]

Lako moguće da je problem šta taj disk ima novu USB 3.x "Bus-powered devices" umotvorinu ... za više vidi Power Consumption sekciju review - a > https://www.anandtech.com/show/18987...-consistency/3

Klasični USB 3 stick će vjerojatno raditi a ako možeš probaj preko USB 3.x hub sa svojim napajanjem.

[axo]

jos kad bi imao hub i neki 3.x usb bilo bi dobro.
Morat cu posudit pa testirat.

[xlr]

Jesi probao preko 2.0 ima li dovoljno brzine za to sto ti treba? Ako streamas filmove biti ce ti vise nego dosta. Meni su stikovi iz nekog razloga u 2.0 portovima, znam da ima neki razlog, ali se ne mogu sjetiti koji je.

[axo]

Autor xlr

Jesi probao preko 2.0 ima li dovoljno brzine za to sto ti treba? Ako streamas filmove biti ce ti vise nego dosta. Meni su stikovi iz nekog razloga u 2.0 portovima, znam da ima neki razlog, ali se ne mogu sjetiti koji je.

Pa realno vrti od 10 do 15 te primarno bi služio kao back up za slike tako da nije nužno da mora bit brz.
Bilo mi cudno zsdto nece na 3.2 pa sam zato potegnuo pitanje.

[Neo-ST]

Autor Bubba

@Neo-ST svakako isprobaj i Merlin fork Asusovog firmwarea, sto nece rijesiti neke tvoje inicijalne probleme koje imas, ali kada njih rijesis, napravit ces od tog uredjaja 3 puta kvalitetniju igracku!

https://www.asuswrt-merlin.net/

Imao Merlin zadnjih par dana, i iako je impresivan sa featuresima (pogotovo Skynet), morao sam ga ipak maknit i vratiti stock fw.

WIFI je daleko slabiji na Merlinu iz nekog razloga nego na stock fw, šta mi je stvaralo probleme po kući sa više uređaja.

Ne znam kako su to uspjeli sjebat, ni na SNB forumu ne znaju, tako da... rip Merlin za mene jbga.

[axo]

Autor Neo-ST

Imao Merlin zadnjih par dana, i iako je impresivan sa featuresima (pogotovo Skynet), morao sam ga ipak maknit i vratiti stock fw.

WIFI je daleko slabiji na Merlinu iz nekog razloga nego na stock fw, šta mi je stvaralo probleme po kući sa više uređaja.

Ne znam kako su to uspjeli sjebat, ni na SNB forumu ne znaju, tako da... rip Merlin za mene jbga.

Nisam isao za time jer kod mene zasada radi ok ali bas cu probat jel ima razlike.
Sta ti je bio problem?

[Neo-ST]

Autor axo

Nisam isao za time jer kod mene zasada radi ok ali bas cu probat jel ima razlike.

Sta ti je bio problem?

https://www.snbforums.com/threads/ax...4/#post-894299

Isti uređaji, na istoj lokaciji u kući sa Merlinom gube signal, sa stockom signal skoro full i stabilni su.

Evo sad npr. tipkam s mobitela u kuhinji koji je spojen na WIFI, to je prije s Merlinom bilo nemoguće.

[Nikky]

Trebalo je analizirati sa WiFi analizerom, jeli do jačine signala, kanala, širine kanala .....
Ali u principu ako si zadovoljan sa opcijama / kako radi stock fw, zašto mijenjati ...

[Neo-ST]

Autor Nikky

Trebalo je analizirati sa WiFi analizerom, jeli do jačine signala, kanala, širine kanala .....
Ali u principu ako si zadovoljan sa opcijama / kako radi stock fw, zašto mijenjati ...

Mda, baš mi se troubleshoota Merlin.
Ovi na SNB forumu su glupi, kažu da nešto nije u redu s mojim routerom, a router radi odlično sa stock fw, dok na Merlinu ne radi dobro. Ali router ne valja

[axo]

Autor Neo-ST

Mda, baš mi se troubleshoota Merlin.
Ovi na SNB forumu su glupi, kažu da nešto nije u redu s mojim routerom, a router radi odlično sa stock fw, dok na Merlinu ne radi dobro. Ali router ne valja

Ja nisam naisao na takve probleme.
Iako su kod mene 2.4 i oba 5ghz odvojena te je kod tebe vjerojatno problem na trenutnoj verziji swa. Možeš uvijek probati stariju ili noviju ver kad ti se bude dalo.
Merlin ima wifi analyzer u postavkama te lako pogledaš šta se događa.Ali otom potom zasada.