Novi Asus router ali ne kužim baš

Neo-ST · 05.12.2023., 23:52

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 · 06.12.2023., 00:54

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 · 06.12.2023., 12:23

@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 · 06.12.2023., 12:44

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 · 06.12.2023., 13:03

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 · 06.12.2023., 16:10

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 · 06.12.2023., 18:28

Ostavi DHCP Server upaljen na Teltonici.

xlr · 06.12.2023., 20:41

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 · 06.12.2023., 22:42

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 · 06.12.2023., 22:47

Code:

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:

Code:

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

05.12.2023., 23:52	#1
Neo-ST Buying Bitcoin Moj komp Datum registracije: Feb 2007 Lokacija: Croatia Postovi: 7,976	Novi Asus router ali ne kužim baš 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 --> Znači kupio sam ovu mrcinu od Asusovog routera jer ovaj od HT-a je počeo krepavat, a ionako već dugo želim pravi router. Router je perverzija, zadnja 2 sata proučavam sve opcije. Posebno je zanimljiv dio sa analizom prometa, klijenata, QoS, itd., no to sada nije bitno. Doma mi je spoj na net preko Teltonika 4G routera (HT sim kartica). I sada meni tu nešto (zapravo puno toga) nije baš jasno. Uboo sam Teltoniku u WAN port od Asusa i sve radi. Ovo su postavke Teltonike za LAN: 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 Zadnje izmijenjeno od: Nikky. 06.12.2023. u 11:21.

06.12.2023., 00:54	#2
xlr 49%winner Moj komp Datum registracije: Sep 2007 Lokacija: PU Postovi: 8,793	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. __________________ ♕ Keep calm and fastboot oem unlock. ♕

06.12.2023., 20:41	#8
xlr 49%winner Moj komp Datum registracije: Sep 2007 Lokacija: PU Postovi: 8,793	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 __________________ ♕ Keep calm and fastboot oem unlock. ♕

06.12.2023., 12:23	#3
Nikky Moderator Datum registracije: Sep 2006 Lokacija: St Postovi: 22,575	@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.

06.12.2023., 12:44	#4
Neo-ST Buying Bitcoin Moj komp Datum registracije: Feb 2007 Lokacija: Croatia Postovi: 7,976	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)...

06.12.2023., 13:03	#5
Nikky Moderator Datum registracije: Sep 2006 Lokacija: St Postovi: 22,575	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

06.12.2023., 16:10	#6
Neo-ST Buying Bitcoin Moj komp Datum registracije: Feb 2007 Lokacija: Croatia Postovi: 7,976	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:

06.12.2023., 18:28	#7
Nikky Moderator Datum registracije: Sep 2006 Lokacija: St Postovi: 22,575	Ostavi DHCP Server upaljen na Teltonici.

06.12.2023., 22:42	#9
Cuky jedan i jedini :D Moj komp Datum registracije: Sep 2005 Lokacija: novi zagreb Postovi: 4,938	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.

Oglasni prostor
PC Ekspert Forum Oglas