Forum: Asus rt-ac68u i Huawei e3372s-153(nie HiLink)

' target='_blank'>Link

25 Kwietnia 2024 14:15:55

Nawigacja

· Strona Główna
· Forum

· Tomato by Shibby
· FreshTomato

Wątki na forum

Najnowsze dyskusje

· Asus TUF-AX3000_V2 p...
· nju swiatło pytania
· Jaki router kupić? ...
· konfiguracja router ...
· Szukam zaproszenia n...
· [Howto] Xpenology na...
· dodatkowe złącza s...
· RT-N18U - nie można...
· [MOD] Tomato64 (x86-64)
· Firewall nie zawsze ...
· [MOD] FreshTomato-AR...
· Optware na CIFS
· RT-AX56U - Status kl...
· [MOD] FreshTomato-MI...
· Multiroom N z wykorz...
· [S] Asus RT-AC68U E1
· [S] ASUS RT-AC68U
· Rozłączanie klient...
· serwer VPN za wan'em
· Przejscie z dyndns f...

Najpopularniejsze obecnie wątki

· Jaki router kupi�...	[552]
· Asus TUF-AX3000_V...	[19]
· Szukam zaproszeni...	[16]
· konfiguracja rout...	[8]
· nju swiatło pytania	[0]

Ankieta

Jaki procesor posiada twój router?

Broadcom MIPSEL

36% [151 głosów]

Broadcom ARM

52% [216 głosów]

Atheros

5% [22 głosów]

Marvell

1% [4 głosów]

Ralink

1% [3 głosów]

Intel/AMD/VIA

1% [5 głosów]

Żaden z powyższych

4% [15 głosów]

Ogółem głosów: 416
Musisz zalogować się, aby móc zagłosować.
Rozpoczęto: 02/02/2015 09:38

Twoje IP

3.144.233.150

O nie! Gdzie jest JavaScript?
Twoja przeglądarka internetowa nie ma włączonej obsługi JavaScript lub nie obsługuje JavaScript. Proszę włączyć JavaScript w przeglądarce internetowej, aby poprawnie wyświetlić tę witrynę, lub zaktualizować do przeglądarki internetowej, która obsługuje JavaScript.

Zobacz wątek

OpenLinksys » :: HOME MEDIA :: » Modemy 3G/LTE

Strona 1 z 2: 12

Asus rt-ac68u i Huawei e3372s-153(nie HiLink)
marcin009988	#1 Dodano 12-03-2015 18:17
User Posty: 43 Dołączył: 12/03/2015 14:05	Mam problem z uruchomieniem tego modemu. Próbowałem z aktualizacją firmware routera do najnowszego oryginalnego ale dalej nie chciał się połączyć. W panelu administracyjnym nie znalazłem nigdzie informacji o aktualnym zasięgu,ani trybie działania (RAS czy NDIS), a wyczytałem na którymś forum że to istotne, router wykrywał modem jako "HUAWEI_MODEM" i tyle. W związku z powyższym wgrałem tomato najnowszą wersję w nadziei że znajdę te ustawienia/informacje albo modem zwyczajnie ruszy ale nic z tego. Na modemie prawie zawsze migała zielona dioda (2 razy co 1sek.), jednak po wpisaniu (wg porady do podobnego zestwu) w scripts/init tego: " switch3g PRODUCT=`cat /tmp/3g.detect` sleep 3 modprobe cdc_ncm sleep 3 MODE="AT^NDISDUP=1,1,\"internet\"" gcom -d /dev/ttyUSB0 -s /etc/gcom/setmode.gcom sleep 3 service wan restart " i zmianie w Networks/Modem device na "/dev/ttyUSB1" zaczęła stale świecić niebieska dioda ale nadal brak dostępu do neta Modem wpięty w USB 2.0 bo 3.0 na dysk chciałem zostawić. Modem jest z t-mobile, a karta z Orange (jedyne co u mnie odbiera) i na kompie wszystko śmiga, download 1-2Mbps na speedteście Gdyby ktoś znał sposób na "dogadanie" się tych urządzeń czy to na oryginalnych softach czy customowyh to proszę o poradę. Edytowany przez marcin009988 dnia 12-03-2015 18:23


shibby	#2 Dodano 12-03-2015 18:27
SysOp Posty: 17067 Dołączył: 15/01/2009 20:30	za bardzo kombinujesz. wraj najnowsze tomato, jako wan ustaw 4G/LTE i tyle. Problemem może być Orange i brak możliwości zdjęcia pinu. Dlatego też dioda nie zmienia koloru. Proxmox VE: i7-7700T, 64GB RAM, 3x2TB SSD, 1x1TB SSD, 512GB NVMe, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology DS920+ VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


marcin009988	#3 Dodano 12-03-2015 19:47
User Posty: 43 Dołączył: 12/03/2015 14:05	Przywróciłem ustawienia fabryczne WPS'em, co by się śladów po moich kombinacjach pozbyć i ustawiłem jak doradziłeś (screen w załączniku 1) ale zielona dioda mruga i oczywiście brak połączenia Tomato wgrywałem wczoraj rano odrazu najnowszy (screen w zał.2) [edit 1] dla pewności wszedłem na stronę Tomato i okazało się że jest nowsze z dzisiaj rana i właśnie zasysam zaraz dam znać czy coś dało marcin009988 załączono następujące plik: Nie masz uprawnień, by zobaczyć załączniki w tym wątku. Edytowany przez marcin009988 dnia 12-03-2015 19:55


shibby	#4 Dodano 12-03-2015 20:24
SysOp Posty: 17067 Dołączył: 15/01/2009 20:30	pokaż logi. Router powinień na wanie dostać ip 192.168.x.x Czy tak się stało? Jak tak to wejdź na ip bramy, dostaniesz się na stronę modemu, wpisz pin, odblokuj kartę i powinien się połączyć. niestety ten modem to hilink i nie ma możliwości odblokowania pinem przeź tomato. Proxmox VE: i7-7700T, 64GB RAM, 3x2TB SSD, 1x1TB SSD, 512GB NVMe, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology DS920+ VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


marcin009988	#5 Dodano 12-03-2015 20:33
User Posty: 43 Dołączył: 12/03/2015 14:05	z tego co sprawdziłem to nie jest hilink bo w kompie normalną aplikację instaluje (internet manager od t-mobile i działa też z mobile partnerem od huawei i topnetinfo) i bez nich nie da się połączyć tak jak hilinkami. Logi: [code] Jan 1 01:01:25 unknown syslog.info syslogd started: BusyBox v1.21.1 Jan 1 01:01:25 unknown kern.notice kernel: klogd started: BusyBox v1.21.1 (2015-03-11 20:01:47 CET) Jan 1 01:01:25 unknown kern.notice kernel: Linux version 2.6.36.4brcmarm (shibby@builder) (gcc version 4.5.3 (Buildroot 2012.02) ) #3 SMP PREEMPT Wed Mar 11 20:11:36 CET 2015 Jan 1 01:01:25 unknown kern.warn kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f Jan 1 01:01:25 unknown kern.warn kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Jan 1 01:01:25 unknown kern.warn kernel: Machine: Northstar Prototype Jan 1 01:01:25 unknown kern.warn kernel: Ignoring unrecognised tag 0x00000000 Jan 1 01:01:25 unknown kern.info kernel: bootconsole [earlycon0] enabled Jan 1 01:01:25 unknown kern.warn kernel: Memory policy: ECC disabled, Data cache writealloc Jan 1 01:01:25 unknown kern.info kernel: MPCORE found at 19020000 Jan 1 01:01:25 unknown kern.debug kernel: On node 0 totalpages: 65536 Jan 1 01:01:25 unknown kern.debug kernel: DMA zone: 256 pages used for memmap Jan 1 01:01:25 unknown kern.debug kernel: DMA zone: 0 pages reserved Jan 1 01:01:25 unknown kern.debug kernel: DMA zone: 32512 pages, LIFO batch:7 Jan 1 01:01:25 unknown kern.debug kernel: Normal zone: 4864 pages used for memmap Jan 1 01:01:25 unknown kern.debug kernel: Normal zone: 27904 pages, LIFO batch:7 Jan 1 01:01:25 unknown kern.info kernel: PERCPU: Embedded 7 pages/cpu @c8215000 s5504 r8192 d14976 u65536 Jan 1 01:01:25 unknown kern.info kernel: pcpu-alloc: s5504 r8192 d14976 u65536 alloc=16*4096 Jan 1 01:01:25 unknown kern.info kernel: pcpu-alloc: [0] 0 [0] 1 Jan 1 01:01:25 unknown kern.warn kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60416 Jan 1 01:01:25 unknown kern.notice kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug Jan 1 01:01:25 unknown kern.info kernel: PID hash table entries: 1024 (order: 0, 4096 bytes) Jan 1 01:01:25 unknown kern.info kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Jan 1 01:01:25 unknown kern.info kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Jan 1 01:01:25 unknown kern.info kernel: Memory: 128MB 128MB = 256MB total Jan 1 01:01:25 unknown kern.notice kernel: Memory: 255376k/255376k available, 6768k reserved, 0K highmem Jan 1 01:01:25 unknown kern.notice kernel: Virtual kernel memory layout: Jan 1 01:01:25 unknown kern.notice kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB) Jan 1 01:01:25 unknown kern.notice kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) Jan 1 01:01:25 unknown kern.notice kernel: DMA : 0xf7e00000 - 0xffe00000 ( 128 MB) Jan 1 01:01:25 unknown kern.notice kernel: vmalloc : 0xd0800000 - 0xf0000000 ( 504 MB) Jan 1 01:01:25 unknown kern.notice kernel: lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) Jan 1 01:01:25 unknown kern.notice kernel: modules : 0xbf000000 - 0xc0000000 ( 16 MB) Jan 1 01:01:25 unknown kern.notice kernel: .init : 0xc0008000 - 0xc003e000 ( 216 kB) Jan 1 01:01:25 unknown kern.notice kernel: .text : 0xc003e000 - 0xc03ca000 (3632 kB) Jan 1 01:01:25 unknown kern.notice kernel: .data : 0xc03e2000 - 0xc0405de0 ( 144 kB) Jan 1 01:01:25 unknown kern.info kernel: SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 Jan 1 01:01:25 unknown kern.info kernel: Hierarchical RCU implementation. Jan 1 01:01:25 unknown kern.info kernel: RCU-based detection of stalled CPUs is disabled. Jan 1 01:01:25 unknown kern.info kernel: Verbose stalled-CPUs detection is disabled. Jan 1 01:01:25 unknown kern.info kernel: NR_IRQS:256 Jan 1 01:01:25 unknown kern.info kernel: MPCORE GIC init Jan 1 01:01:25 unknown kern.warn kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored. Jan 1 01:01:25 unknown kern.info kernel: MPCORE Global Timer Clock 400000000Hz Jan 1 01:01:25 unknown kern.info kernel: Calibrating delay loop... 1599.07 BogoMIPS (lpj=7995392) Jan 1 01:01:25 unknown kern.info kernel: pid_max: default: 32768 minimum: 301 Jan 1 01:01:25 unknown kern.warn kernel: Mount-cache hash table entries: 512 Jan 1 01:01:25 unknown kern.info kernel: CPU: Testing write buffer coherency: ok Jan 1 01:01:25 unknown kern.info kernel: MPCORE Private timer setup CPU0 Jan 1 01:01:25 unknown kern.info kernel: Calibrating local timer... 399.831MHz. Jan 1 01:01:25 unknown kern.info kernel: L310: cache controller enabled 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x7a130000 Jan 1 01:01:25 unknown kern.warn kernel: CPU1: Booted secondary processor Jan 1 01:01:25 unknown kern.info kernel: MPCORE Private timer setup CPU1 Jan 1 01:01:25 unknown kern.info kernel: Brought up 2 CPUs Jan 1 01:01:25 unknown kern.info kernel: SMP: Total of 2 processors activated (3194.88 BogoMIPS). Jan 1 01:01:25 unknown kern.info kernel: devtmpfs: initialized Jan 1 01:01:25 unknown kern.info kernel: atomic64 test passed Jan 1 01:01:25 unknown kern.info kernel: NET: Registered protocol family 16 Jan 1 01:01:25 unknown kern.warn kernel: Found a AMD NAND flash: Jan 1 01:01:25 unknown kern.warn kernel: Total size: 128MB Jan 1 01:01:25 unknown kern.warn kernel: Block size: 128KB Jan 1 01:01:25 unknown kern.warn kernel: Page Size: 2048B Jan 1 01:01:25 unknown kern.warn kernel: OOB Size: 64B Jan 1 01:01:25 unknown kern.warn kernel: Sector size: 512B Jan 1 01:01:25 unknown kern.warn kernel: Spare size: 16B Jan 1 01:01:25 unknown kern.warn kernel: ECC level: 8 (8-bit) Jan 1 01:01:25 unknown kern.warn kernel: Device ID: 0x 1 0xf1 0x 0 0x1d 0x 1 0xf1 Jan 1 01:01:25 unknown kern.info kernel: CCA UART Clock Config: Sel=1 Ovr=1 Div=48 Jan 1 01:01:25 unknown kern.info kernel: CCA UART Clock rate 100000000Hz Jan 1 01:01:25 unknown kern.warn kernel: bio: create slab at 0 Jan 1 01:01:25 unknown kern.info kernel: Switching to clocksource mpcore_gtimer Jan 1 01:01:25 unknown kern.info kernel: NET: Registered protocol family 2 Jan 1 01:01:25 unknown kern.info kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes) Jan 1 01:01:25 unknown kern.info kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes) Jan 1 01:01:25 unknown kern.info kernel: TCP bind hash table entries: 8192 (order: 4, 98304 bytes) Jan 1 01:01:25 unknown kern.info kernel: TCP: Hash tables configured (established 8192 bind 8192) Jan 1 01:01:25 unknown kern.info kernel: TCP reno registered Jan 1 01:01:25 unknown kern.info kernel: UDP hash table entries: 128 (order: 0, 4096 bytes) Jan 1 01:01:25 unknown kern.info kernel: UDP-Lite hash table entries: 128 (order: 0, 4096 bytes) Jan 1 01:01:25 unknown kern.info kernel: NET: Registered protocol family 1 Jan 1 01:01:25 unknown kern.debug kernel: PCI: CLS 0 bytes, default 32 Jan 1 01:01:25 unknown kern.warn kernel: PCI: no core Jan 1 01:01:25 unknown kern.warn kernel: PCI: no core Jan 1 01:01:25 unknown kern.info kernel: PCI: scanning bus 0 Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:00.0: reg 10: [mem 0x18000000-0x18000fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:00.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:01.0: reg 10: [mem 0x18001000-0x18001fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:01.0: reg 14: [mem 0x18002000-0x18002fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:01.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:02.0: reg 10: [mem 0x1802c000-0x1802cfff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:02.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:03.0: reg 10: [mem 0x18024000-0x18024fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:03.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:04.0: reg 10: [mem 0x18025000-0x18025fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:04.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:05.0: reg 10: [mem 0x18026000-0x18026fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:05.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:06.0: reg 10: [mem 0x18027000-0x18027fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:06.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:07.0: reg 10: [mem 0x18012000-0x18012fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:07.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:08.0: reg 10: [mem 0x18013000-0x18013fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:08.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:09.0: reg 10: [mem 0x18014000-0x18014fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:09.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0a.0: reg 10: [mem 0x1800b000-0x1800bfff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0a.0: reg 14: [mem 0x1800c000-0x1800cfff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0a.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0b.0: reg 10: [mem 0x18022000-0x18022fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0b.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0b.1: reg 10: [mem 0x18021000-0x18021fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0b.1: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0c.0: reg 10: [mem 0x18023000-0x18023fff] Jan 1 01:01:25 unknown kern.debug kernel: pci 0000:00:0c.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:0d.0: reg 10: [mem 0x18020000-0x18020fff] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:0d.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:0e.0: reg 10: [mem 0x18210000-0x1821ffff] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:0e.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:0f.0: reg 10: [mem 0x18010000-0x18010fff] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:0f.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:10.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:11.0: reg 10: [mem 0x18028000-0x18028fff] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:11.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:12.0: reg 10: [mem 0x18029000-0x18029fff] Jan 1 01:01:26 unknown kern.debug kernel: pci 0000:00:12.0: reg 30: [mem 0x00000000-0x000007ff pref] Jan 1 01:01:26 unknown kern.warn kernel: PCI: Fixing up bus 0 Jan 1 01:01:26 unknown kern.info kernel: PCIE1 link=1 Jan 1 01:01:26 unknown kern.info kernel: PCIE1 switching to GEN2 Jan 1 01:01:26 unknown kern.info kernel: PCIE1 link=1 Jan 1 01:01:26 unknown kern.debug kernel: pci 0001:00:00.0: PME# supported from D0 D3hot D3cold Jan 1 01:01:26 unknown kern.debug kernel: pci 0001:00:00.0: PME# disabled Jan 1 01:01:26 unknown kern.warn kernel: PCI: Fixing up bus 0 Jan 1 01:01:26 unknown kern.info kernel: PCI: bus0: Fast back to back transfers disabled Jan 1 01:01:26 unknown kern.debug kernel: pci 0001:01:00.0: reg 10: [mem 0x08000000-0x08007fff 64bit] Jan 1 01:01:26 unknown kern.debug kernel: pci 0001:01:00.0: supports D1 D2 Jan 1 01:01:26 unknown kern.warn kernel: PCI: Fixing up bus 1 Jan 1 01:01:26 unknown kern.info kernel: PCI: bus1: Fast back to back transfers disabled Jan 1 01:01:26 unknown kern.info kernel: pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff] Jan 1 01:01:26 unknown kern.info kernel: pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit] Jan 1 01:01:26 unknown kern.info kernel: pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff] Jan 1 01:01:26 unknown kern.info kernel: pci 0001:00:00.0: PCI bridge to [bus 01-01] Jan 1 01:01:26 unknown kern.info kernel: pci 0001:00:00.0: bridge window [io disabled] Jan 1 01:01:26 unknown kern.info kernel: pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff] Jan 1 01:01:26 unknown kern.info kernel: pci 0001:00:00.0: bridge window [mem pref disabled] Jan 1 01:01:26 unknown kern.info kernel: PCIE2 link=1 Jan 1 01:01:26 unknown kern.info kernel: PCIE2 switching to GEN2 Jan 1 01:01:26 unknown kern.info kernel: PCIE2 link=1 Jan 1 01:01:26 unknown kern.debug kernel: pci 0002:00:00.0: PME# supported from D0 D3hot D3cold Jan 1 01:01:26 unknown kern.debug kernel: pci 0002:00:00.0: PME# disabled Jan 1 01:01:26 unknown kern.warn kernel: PCI: Fixing up bus 0 Jan 1 01:01:26 unknown kern.info kernel: PCI: bus0: Fast back to back transfers disabled Jan 1 01:01:26 unknown kern.debug kernel: pci 0002:02:00.0: reg 10: [mem 0x40000000-0x40007fff 64bit] Jan 1 01:01:26 unknown kern.debug kernel: pci 0002:02:00.0: supports D1 D2 Jan 1 01:01:26 unknown kern.warn kernel: PCI: Fixing up bus 2 Jan 1 01:01:26 unknown kern.info kernel: PCI: bus2: Fast back to back transfers disabled Jan 1 01:01:26 unknown kern.info kernel: pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff] Jan 1 01:01:26 unknown kern.info kernel: pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit] Jan 1 01:01:26 unknown kern.info kernel: pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff] Jan 1 01:01:26 unknown kern.info kernel: pci 0002:00:00.0: PCI bridge to [bus 02-02] Jan 1 01:01:26 unknown kern.info kernel: pci 0002:00:00.0: bridge window [io disabled] Jan 1 01:01:26 unknown kern.info kernel: pci 0002:00:00.0: bridge window [mem 0x40000000-0x400fffff] Jan 1 01:01:26 unknown kern.info kernel: pci 0002:00:00.0: bridge window [mem pref disabled] Jan 1 01:01:26 unknown user.err syslog: module fat not found in modules.dep Jan 1 01:01:26 unknown user.err syslog: module vfat not found in modules.dep Jan 1 01:01:26 unknown kern.info kernel: PCIE3 link=0 Jan 1 01:01:26 unknown kern.notice kernel: VFS: Disk quotas dquot_6.5.2 Jan 1 01:01:26 unknown kern.warn kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Jan 1 01:01:26 unknown kern.info kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher Jan 1 01:01:26 unknown kern.info kernel: fuse init (API version 7.15) Jan 1 01:01:26 unknown kern.info kernel: msgmni has been set to 498 Jan 1 01:01:26 unknown kern.info kernel: io scheduler noop registered (default) Jan 1 01:01:26 unknown kern.info kernel: io scheduler deadline registered Jan 1 01:01:26 unknown kern.info kernel: io scheduler cfq registered Jan 1 01:01:26 unknown kern.info kernel: Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled Jan 1 01:01:26 unknown kern.info kernel: serial8250.0: ttyS0 at MMIO 0x18000300 (irq = 117) is a 16550 Jan 1 01:01:26 unknown kern.info kernel: console [ttyS0] enabled, bootconsole disabled Jan 1 01:01:26 unknown kern.info kernel: serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117) is a 16550 Jan 1 01:01:26 unknown kern.info kernel: brd: module loaded Jan 1 01:01:26 unknown kern.info kernel: loop: module loaded Jan 1 01:01:26 unknown kern.err kernel: pflash: found no supported devices Jan 1 01:01:26 unknown kern.err kernel: bcmsflash: found no supported devices Jan 1 01:01:26 unknown kern.warn kernel: Boot partition size = 524288(0x80000) Jan 1 01:01:26 unknown kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 Jan 1 01:01:26 unknown kern.notice kernel: nflash: squash filesystem with lzma found at block 29 Jan 1 01:01:26 unknown kern.notice kernel: Creating 4 MTD partitions on "nflash": Jan 1 01:01:26 unknown kern.notice kernel: 0x000000000000-0x000000080000 : "boot" Jan 1 01:01:26 unknown kern.notice kernel: 0x000000080000-0x000000200000 : "nvram" Jan 1 01:01:26 unknown kern.notice kernel: 0x000000200000-0x000002000000 : "linux" Jan 1 01:01:26 unknown kern.notice kernel: 0x0000003ab990-0x000002000000 : "rootfs" Jan 1 01:01:26 unknown kern.info kernel: PPP generic driver version 2.4.2 Jan 1 01:01:26 unknown kern.info kernel: PPP MPPE Compression module registered Jan 1 01:01:26 unknown kern.info kernel: NET: Registered protocol family 24 Jan 1 01:01:26 unknown kern.info kernel: PPTP driver version 0.8.5 Jan 1 01:01:26 unknown kern.warn kernel: === PPTP init === Jan 1 01:01:26 unknown kern.info kernel: u32 classifier Jan 1 01:01:26 unknown kern.info kernel: Actions configured Jan 1 01:01:26 unknown kern.info kernel: Netfilter messages via NETLINK v0.30. Jan 1 01:01:26 unknown kern.info kernel: nf_conntrack version 0.5.0 (3990 buckets, 15960 max) Jan 1 01:01:26 unknown kern.info kernel: xt_time: kernel timezone is -0000 Jan 1 01:01:26 unknown kern.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Jan 1 01:01:26 unknown kern.info kernel: TCP cubic registered Jan 1 01:01:26 unknown kern.info kernel: NET: Registered protocol family 10 Jan 1 01:01:26 unknown kern.info kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team Jan 1 01:01:26 unknown kern.info kernel: NET: Registered protocol family 17 Jan 1 01:01:26 unknown kern.info kernel: L2TP core driver, V2.0 Jan 1 01:01:26 unknown kern.info kernel: PPPoL2TP kernel driver, V2.0 Jan 1 01:01:26 unknown kern.info kernel: 802.1Q VLAN Support v1.8 Ben Greear Jan 1 01:01:26 unknown kern.info kernel: All bugs added by David S. Miller Jan 1 01:01:26 unknown kern.notice kernel: Registering the dns_resolver key type Jan 1 01:01:26 unknown kern.info kernel: Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012 Jan 1 01:01:26 unknown kern.info kernel: NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD NAND 128MiB 3,3V 8-bit) Jan 1 01:01:26 unknown kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at: Jan 1 01:01:26 unknown kern.warn kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Jan 1 01:01:26 unknown kern.warn kernel: Available 7 bytes at (off,len): Jan 1 01:01:26 unknown kern.warn kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) Jan 1 01:01:26 unknown kern.info kernel: Scanning device for bad blocks Jan 1 01:01:26 unknown kern.warn kernel: Options: NO_AUTOINCR,NO_READRDY,BBT_SCAN2NDPAGE, Jan 1 01:01:26 unknown kern.notice kernel: Creating 2 MTD partitions on "brcmnand": Jan 1 01:01:26 unknown kern.notice kernel: 0x000002000000-0x000008000000 : "brcmnand" Jan 1 01:01:26 unknown kern.notice kernel: 0x000004000000-0x000008000000 : "jffs2" Jan 1 01:01:26 unknown kern.warn kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3. Jan 1 01:01:26 unknown kern.info kernel: devtmpfs: mounted Jan 1 01:01:26 unknown kern.info kernel: Freeing init memory: 216K Jan 1 01:01:26 unknown kern.warn kernel: emf: module license 'Proprietary' taints kernel. Jan 1 01:01:26 unknown kern.warn kernel: Disabling lock debugging due to kernel taint Jan 1 01:01:26 unknown kern.warn kernel: et_module_init: passivemode set to 0x0 Jan 1 01:01:26 unknown kern.warn kernel: et_module_init: txworkq set to 0x0 Jan 1 01:01:26 unknown kern.warn kernel: et_module_init: et_txq_thresh set to 0x0 Jan 1 01:01:26 unknown kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.86 (r456083) Jan 1 01:01:26 unknown kern.warn kernel: wl_module_init: passivemode set to 0x0 Jan 1 01:01:26 unknown kern.warn kernel: wl_module_init: txworkq set to 0x0 Jan 1 01:01:26 unknown kern.warn kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083) Jan 1 01:01:26 unknown kern.warn kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083) Jan 1 01:01:26 unknown kern.info kernel: usbcore: registered new interface driver usbfs Jan 1 01:01:26 unknown kern.info kernel: usbcore: registered new interface driver hub Jan 1 01:01:26 unknown kern.info kernel: usbcore: registered new device driver usb Jan 1 01:01:26 unknown user.debug hotplug[796]: Attached USB device 1-0:1.0 [INTERFACE=9/0/0 PRODUCT=1d6b/3/206] Jan 1 01:01:26 unknown kern.notice kernel: SCSI subsystem initialized Jan 1 01:01:26 unknown kern.warn kernel: csw_retry 100 Jan 1 01:01:26 unknown kern.info kernel: Initializing USB Mass Storage driver... Jan 1 01:01:26 unknown kern.info kernel: usbcore: registered new interface driver usb-storage Jan 1 01:01:26 unknown kern.info kernel: USB Mass Storage support registered. Jan 1 01:01:26 unknown kern.notice kernel: jnl: driver (lke_8.9.0, Apr 9 2014 16:56:06, LBD=ON) loaded at bf571000 Jan 1 01:01:26 unknown kern.notice kernel: ufsd:: trace mask set to 0000000f Jan 1 01:01:26 unknown kern.notice kernel: ufsd: driver (lke_8.9.0 lke_8.9.0_r225078_b43, LBD=ON, delalloc, acl, ioctl, ugm, sd(1), wb, tr) loaded at bf57e000 Jan 1 01:01:26 unknown kern.notice kernel: NTFS support included Jan 1 01:01:26 unknown kern.notice kernel: Hfs+/HfsJ support included Jan 1 01:01:26 unknown kern.notice kernel: optimized: speed Jan 1 01:01:26 unknown kern.notice kernel: Build_for__ASUS_PRODUCTS_003_lke_8.9.0_r225078_b43 Jan 1 01:01:26 unknown kern.info kernel: xhci_hcd 0000:00:0c.0: xHCI Host Controller Jan 1 01:01:26 unknown kern.info kernel: xhci_hcd 0000:00:0c.0: new USB bus registered, assigned bus number 1 Jan 1 01:01:26 unknown kern.info kernel: xhci_hcd 0000:00:0c.0: irq 112, io mem 0x18023000 Jan 1 01:01:26 unknown kern.err kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X Jan 1 01:01:26 unknown user.debug hotplug[805]: Attached USB device 2-0:1.0 [INTERFACE=9/0/0 PRODUCT=1d6b/2/206] Jan 1 01:01:26 unknown kern.err kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry Jan 1 01:01:26 unknown kern.warn kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values Jan 1 01:01:26 unknown kern.debug kernel: xHCI xhci_add_endpoint called for root hub Jan 1 01:01:26 unknown kern.debug kernel: xHCI xhci_check_bandwidth called for root hub Jan 1 01:01:26 unknown kern.info kernel: hub 1-0:1.0: USB hub found Jan 1 01:01:26 unknown kern.info kernel: hub 1-0:1.0: 1 port detected Jan 1 01:01:26 unknown kern.info kernel: [xhci-hub] usb2mode:[0] Jan 1 01:01:26 unknown kern.info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 1 01:01:26 unknown kern.info kernel: ehci_hcd 0000:00:0b.1: EHCI Host Controller Jan 1 01:01:26 unknown kern.info kernel: ehci_hcd 0000:00:0b.1: new USB bus registered, assigned bus number 2 Jan 1 01:01:26 unknown kern.info kernel: ehci_hcd 0000:00:0b.1: irq 111, io mem 0x18021000 Jan 1 01:01:26 unknown kern.info kernel: ehci_hcd 0000:00:0b.1: USB 0.0 started, EHCI 1.00 Jan 1 01:01:26 unknown kern.info kernel: hub 2-0:1.0: USB hub found Jan 1 01:01:26 unknown kern.info kernel: hub 2-0:1.0: 2 ports detected Jan 1 01:01:26 unknown kern.info kernel: usbcore: registered new interface driver hiddev Jan 1 01:01:26 unknown kern.info kernel: usbcore: registered new interface driver usbhid Jan 1 01:01:27 unknown kern.info kernel: usbhid: USB HID core driver Jan 1 01:01:27 unknown kern.info kernel: usb 2-2: new high speed USB device using ehci_hcd and address 2 Jan 1 01:01:27 unknown kern.info kernel: device vlan1 entered promiscuous mode Jan 1 01:01:27 unknown kern.info kernel: device eth0 entered promiscuous mode Jan 1 01:01:27 unknown kern.info kernel: scsi0 : usb-storage 2-2:1.0 Jan 1 01:01:27 unknown user.debug hotplug[867]: Attached USB device 2-2:1.0 [INTERFACE=8/6/80 PRODUCT=12d1/14fe/102] Jan 1 01:01:27 unknown kern.info kernel: device eth1 entered promiscuous mode Jan 1 01:01:28 unknown kern.notice kernel: scsi 0:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 Jan 1 01:01:28 unknown kern.notice kernel: scsi 0:0:0:1: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Jan 1 01:01:28 unknown kern.notice kernel: sd 0:0:0:1: [sda] Attached SCSI removable disk Jan 1 01:01:28 unknown kern.info kernel: device eth2 entered promiscuous mode Jan 1 01:01:28 unknown kern.info kernel: br0: port 3(eth2) entering forwarding state Jan 1 01:01:28 unknown kern.info kernel: br0: port 3(eth2) entering forwarding state Jan 1 01:01:28 unknown kern.info kernel: br0: port 2(eth1) entering forwarding state Jan 1 01:01:28 unknown kern.info kernel: br0: port 2(eth1) entering forwarding state Jan 1 01:01:28 unknown kern.info kernel: br0: port 1(vlan1) entering forwarding state Jan 1 01:01:28 unknown kern.info kernel: br0: port 1(vlan1) entering forwarding state Jan 1 01:01:29 unknown kern.info kernel: ipt_account 0.1.21 : Piotr Gasidlo , http://code.google.com/p/ipt-account/ Jan 1 01:01:30 unknown authpriv.warn dropbear[948]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key Jan 1 01:01:30 unknown authpriv.info dropbear[962]: Running in background Jan 1 01:01:30 unknown kern.info kernel: usbcore: registered new interface driver cdc_ether Jan 1 01:01:30 unknown kern.info kernel: cdc_ncm: 14-Mar-2012 Jan 1 01:01:30 unknown kern.info kernel: usbcore: registered new interface driver cdc_ncm Jan 1 01:01:30 unknown daemon.info dnsmasq[989]: started, version 2.72+ cachesize 1500 Jan 1 01:01:30 unknown daemon.info dnsmasq[989]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset Tomato-helper auth DNSSEC loop-detect Jan 1 01:01:30 unknown daemon.info dnsmasq[989]: asynchronous logging enabled, queue limit is 5 messages Jan 1 01:01:30 unknown daemon.info dnsmasq-dhcp[989]: DHCP, IP range 192.168.1.2 -- 192.168.1.51, lease time 1d Jan 1 01:01:30 unknown daemon.warn dnsmasq[989]: failed to access /etc/resolv.dnsmasq: No such file or directory Jan 1 01:01:30 unknown daemon.info dnsmasq[989]: read /etc/hosts - 2 addresses Jan 1 01:01:30 unknown daemon.info dnsmasq[989]: read /etc/dnsmasq/hosts/hosts - 3 addresses Jan 1 01:01:30 unknown daemon.info dnsmasq-dhcp[989]: read /etc/dnsmasq/dhcp/dhcp-hosts Jan 1 01:01:30 unknown user.notice root: 4G MODEM FOUND - 12d1:14fe - Switching ... Jan 1 01:01:30 unknown kern.info kernel: usb 2-2: USB disconnect, address 2 Jan 1 01:01:30 unknown user.info preinit[1]: NGinX - daemon not enabled cancelled generation of config file Jan 1 01:01:30 unknown user.debug preinit[1]: starting rstats. Jan 1 01:01:30 unknown user.debug preinit[1]: starting cstats. Jan 1 01:01:31 unknown kern.info kernel: usbcore: registered new interface driver usbserial Jan 1 01:01:31 unknown kern.info kernel: USB Serial support registered for generic Jan 1 01:01:31 unknown kern.info kernel: usbcore: registered new interface driver usbserial_generic Jan 1 01:01:31 unknown kern.info kernel: usbserial: USB Serial Driver core Jan 1 01:01:31 unknown kern.info kernel: usbcore: deregistering interface driver usbserial_generic Jan 1 01:01:31 unknown kern.info kernel: USB Serial deregistering driver generic Jan 1 01:01:31 unknown kern.info kernel: usbcore: deregistering interface driver usbserial Jan 1 01:01:31 unknown kern.info kernel: usbcore: registered new interface driver usbserial Jan 1 01:01:31 unknown kern.info kernel: USB Serial support registered for generic Jan 1 01:01:31 unknown kern.info kernel: usb 2-2: new high speed USB device using ehci_hcd and address 3 Jan 1 01:01:31 unknown kern.info kernel: usb 2-2: MAC-Address: 00:1e:10:1f:00:00 Jan 1 01:01:31 unknown user.debug hotplug[1135]: Attached USB device 2-2:1.1 [INTERFACE=255/2/1 PRODUCT=12d1/1506/102] Jan 1 01:01:31 unknown kern.info kernel: cdc_ncm 2-2:1.2: usb0: register 'cdc_ncm' at usb-0000:00:0b.1-2, Mobile Broadband Network Device, 00:1e:10:1f:00:00 Jan 1 01:01:31 unknown kern.info kernel: scsi1 : usb-storage 2-2:1.3 Jan 1 01:01:31 unknown kern.info kernel: scsi2 : usb-storage 2-2:1.4 Jan 1 01:01:31 unknown kern.info kernel: usbcore: registered new interface driver usbserial_generic Jan 1 01:01:31 unknown kern.info kernel: usbserial: USB Serial Driver core Jan 1 01:01:31 unknown user.debug hotplug[1134]: Attached USB device 2-2:1.0 [INTERFACE=255/2/18 PRODUCT=12d1/1506/102] Jan 1 01:01:31 unknown user.debug hotplug[1141]: Attached USB device 2-2:1.2 [INTERFACE=255/2/22 PRODUCT=12d1/1506/102] Jan 1 01:01:31 unknown user.debug hotplug[1149]: Attached USB device 2-2:1.4 [INTERFACE=8/6/80 PRODUCT=12d1/1506/102] Jan 1 01:01:31 unknown user.debug hotplug[1150]: Attached USB device 2-2:1.3 [INTERFACE=8/6/80 PRODUCT=12d1/1506/102] Jan 1 01:01:31 unknown user.notice root: 4G MODEM WAN found - Non-Hilink - using usb0 as WAN Jan 1 01:01:31 unknown user.notice root: 4G MODEM - connecting ... Jan 1 01:01:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:32 unknown kern.notice kernel: scsi 1:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 Jan 1 01:01:32 unknown kern.notice kernel: scsi 2:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Jan 1 01:01:32 unknown kern.notice kernel: sd 2:0:0:0: [sda] Attached SCSI removable disk Jan 1 01:01:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:37 unknown daemon.err apcupsd[845]: apcupsd FATAL ERROR in linux-usb.c at line 609 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see . Jan 1 01:01:37 unknown daemon.err apcupsd[845]: apcupsd error shutdown completed Jan 1 01:01:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:45 unknown kern.warn kernel: gro disabled Jan 1 01:01:45 unknown user.notice root: Transmission daemon successfully stoped Jan 1 01:01:45 unknown user.info preinit[1]: Asus RT-AC68R/U: Tomato 1.28.0000 -127 K26ARM USB AIO-64K Jan 1 01:01:45 unknown user.notice root: Stoping NFS Server ... Jan 1 01:01:46 unknown user.notice root: NFS Server stoped ... Jan 1 01:01:46 unknown daemon.info dnsmasq-dhcp[989]: DHCPDISCOVER(br0) 192.168.1.8 ec:b1:d7:d9:62:0c Jan 1 01:01:46 unknown daemon.info dnsmasq-dhcp[989]: DHCPOFFER(br0) 192.168.1.8 ec:b1:d7:d9:62:0c Jan 1 01:01:46 unknown daemon.info dnsmasq-dhcp[989]: DHCPREQUEST(br0) 192.168.1.8 ec:b1:d7:d9:62:0c Jan 1 01:01:46 unknown daemon.info dnsmasq-dhcp[989]: DHCPACK(br0) 192.168.1.8 ec:b1:d7:d9:62:0c komp Jan 1 01:01:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:50 unknown daemon.info dnsmasq-dhcp[989]: DHCPREQUEST(br0) 192.168.1.8 ec:b1:d7:d9:62:0c Jan 1 01:01:50 unknown daemon.info dnsmasq-dhcp[989]: DHCPACK(br0) 192.168.1.8 ec:b1:d7:d9:62:0c komp Jan 1 01:01:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:20 unknown kern.info kernel: ADDRCONF(NETDEV_UP): usb0: link is not ready Jan 1 01:02:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:34 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:39 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:49 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:54 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:59 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:04 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:09 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:34 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:39 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:00 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:15 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:25 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:30 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:40 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:45 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:00 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:46 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:51 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:07:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:23 unknown daemon.info dnsmasq-dhcp[989]: DHCPREQUEST(br0) 192.168.1.8 ec:b1:d7:d9:62:0c Jan 1 01:08:23 unknown daemon.info dnsmasq-dhcp[989]: DHCPACK(br0) 192.168.1.8 ec:b1:d7:d9:62:0c komp Jan 1 01:08:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:08:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:09:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:17 unknown daemon.info dnsmasq-dhcp[989]: DHCPREQUEST(br0) 192.168.1.8 ec:b1:d7:d9:62:0c Jan 1 01:10:17 unknown daemon.info dnsmasq-dhcp[989]: DHCPACK(br0) 192.168.1.8 ec:b1:d7:d9:62:0c komp Jan 1 01:10:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:10:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:34 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:39 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:49 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:54 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:11:59 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:04 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:09 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:40 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:45 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:12:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:00 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:15 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:25 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:30 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:40 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:45 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:13:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:46 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:51 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:14:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:15:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:16:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:17:59 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:04 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:09 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:34 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:39 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:49 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:54 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:18:59 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:04 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:09 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:25 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:30 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:40 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:45 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:19:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:00 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:15 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:25 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:30 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:46 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:51 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:20:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:46 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:51 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:21:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:22:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:23:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:49 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:54 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:24:59 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:04 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:09 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:34 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:39 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:49 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:54 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:25:59 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:15 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:25 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:30 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:40 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:45 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:26:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:00 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:15 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:46 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:51 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:27:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:28:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:29:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:30:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:34 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:39 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:49 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:54 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:31:59 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:04 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:09 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:34 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:39 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:44 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:49 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:32:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:00 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:15 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:25 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:30 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:40 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:45 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:33:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:00 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:05 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:46 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:51 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:34:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:35:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:36:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:37:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:38:02 unknown kern.info kernel: usb 2-2: USB disconnect, address 3 Jan 1 01:38:02 unknown kern.info kernel: cdc_ncm 2-2:1.2: usb0: unregister 'cdc_ncm' usb-0000:00:0b.1-2, Mobile Broadband Network Device Jan 1 01:38:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:38:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:38:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:38:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:38:21 unknown daemon.info dnsmasq-dhcp[989]: DHCPREQUEST(br0) 192.168.1.8 ec:b1:d7:d9:62:0c Jan 1 01:38:21 unknown daemon.info dnsmasq-dhcp[989]: DHCPACK(br0) 192.168.1.8 ec:b1:d7:d9:62:0c komp Jan 1 01:38:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:38:29 unknown user.notice root: 4G MODEM - device Edytowany przez marcin009988 dnia 12-03-2015 20:41


shibby	#6 Dodano 12-03-2015 22:21
SysOp Posty: 17067 Dołączył: 15/01/2009 20:30	racja, to nie hilink Cytat cdc_ncm 2-2:1.2: usb0: unregister 'cdc_ncm' usb-0000:00:0b.1-2, Mobile Broadband Network Device 4G MODEM WAN found - Non-Hilink - using usb0 as WAN interfejs WAN został wykryty ale Cytat 4G MODEM FOUND - 12d1:14fe - Switching ... i nie potrafi go przełączyć przez co nie wykrywa interfejsu diagnostycznego ttyUSBX, który to służy to wywołania połączenia LTE w non-hilinku. Widzę, że pojawiła się w styczniu nowa wersja usb_modeswitch wraz z nową definicją modemów i akurat jest zmiana w pliku dla twojego modemu. to może być to. W wolnej chwili skompiluję ci testówkę i dam znac. Proxmox VE: i7-7700T, 64GB RAM, 3x2TB SSD, 1x1TB SSD, 512GB NVMe, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology DS920+ VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


marcin009988	#7 Dodano 13-03-2015 09:25
User Posty: 43 Dołączył: 12/03/2015 14:05	Dzięki za informację że jeszcze jest nadzieja. Tymczasem dzisiaj po zajęciach podjadę jeszcze do orange, żeby mi kartę wymienili na taką z odblokowaną możliwością wyłączenia PINu


shibby	#8 Dodano 13-03-2015 10:39
SysOp Posty: 17067 Dołączył: 15/01/2009 20:30	nie wymienią ci. Wiele osób wojowało i nic nie zdziałało. Jedyna opcja to zmienić operatora bo tylko orange PIN wymusza. Ale u ciebie problemu nie będzie to do non-hilink to Tomato potrafi wysłać pin. Problem z pinem pojawia się tylko na hilinkach. Połączony z 13 March 2015 12:06:19: wysłałem ci PW. Edytowany przez shibby dnia 13-03-2015 12:06 Proxmox VE: i7-7700T, 64GB RAM, 3x2TB SSD, 1x1TB SSD, 512GB NVMe, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology DS920+ VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


marcin009988	#9 Dodano 13-03-2015 16:25
User Posty: 43 Dołączył: 12/03/2015 14:05	Niestety to samo oto logi(100 ostatnich): Jan 1 01:01:05 unknown kern.info kernel: USB Serial support registered for generic Jan 1 01:01:05 unknown kern.info kernel: usbserial_generic 2-2:1.0: generic converter detected Jan 1 01:01:05 unknown kern.info kernel: usb 2-2: generic converter now attached to ttyUSB0 Jan 1 01:01:05 unknown user.notice root: 4G MODEM ready - using usbserial module Jan 1 01:01:05 unknown kern.info kernel: usbserial_generic 2-2:1.1: generic converter detected Jan 1 01:01:05 unknown kern.info kernel: usb 2-2: generic converter now attached to ttyUSB1 Jan 1 01:01:05 unknown kern.info kernel: usbcore: registered new interface driver usbserial_generic Jan 1 01:01:05 unknown kern.info kernel: usbserial: USB Serial Driver core Jan 1 01:01:10 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:12 unknown daemon.err apcupsd[1587]: apcupsd FATAL ERROR in linux-usb.c at line 609 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see . Jan 1 01:01:12 unknown daemon.err apcupsd[1587]: apcupsd error shutdown completed Jan 1 01:01:15 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:20 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:25 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:30 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:33 unknown user.notice root: 4G MODEM WAN found - Non-Hilink - using usb0 as WAN Jan 1 01:01:35 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:38 unknown user.notice root: 4G MODEM Signal Strength: -113 dBm Jan 1 01:01:38 unknown user.notice root: 4G MODEM - connecting ... Jan 1 01:01:40 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:42 unknown user.notice root: 4G MODEM - connected ... Jan 1 01:01:42 unknown user.notice root: 4G MODEM - WAN configured ... Jan 1 01:01:45 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:50 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:01:55 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:03 unknown daemon.info dnsmasq-dhcp[1696]: DHCPINFORM(br0) 192.168.1.27 00:24:54:b6:42:f9 Jan 1 01:02:03 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.27 00:24:54:b6:42:f9 Marcin_Laptop Jan 1 01:02:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:21 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:26 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:31 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:36 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:41 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:46 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:51 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:02:56 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:01 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:06 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:11 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:16 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:16 unknown daemon.info dnsmasq-dhcp[1696]: DHCPINFORM(br0) 192.168.1.27 00:24:54:b6:42:f9 Jan 1 01:03:16 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.27 00:24:54:b6:42:f9 Marcin_Laptop Jan 1 01:03:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:42 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:47 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:52 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:03:57 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:01 unknown daemon.info dnsmasq-dhcp[1696]: DHCPREQUEST(br0) 192.168.1.27 00:24:54:b6:42:f9 Jan 1 01:04:01 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.27 00:24:54:b6:42:f9 Marcin_Laptop Jan 1 01:04:02 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:04 unknown daemon.info dnsmasq-dhcp[1696]: DHCPINFORM(br0) 192.168.1.27 00:24:54:b6:42:f9 Jan 1 01:04:04 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.27 00:24:54:b6:42:f9 Marcin_Laptop Jan 1 01:04:07 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:12 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:17 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:22 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:27 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:32 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:37 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:04:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:03 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:08 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:13 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:18 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:23 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:28 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:33 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:38 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:43 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:44 unknown daemon.info dnsmasq-dhcp[1696]: DHCPREQUEST(br0) 192.168.2.100 5c:ac:4c:7c:cd:a8 Jan 1 01:05:44 unknown daemon.info dnsmasq-dhcp[1696]: DHCPNAK(br0) 192.168.2.100 5c:ac:4c:7c:cd:a8 wrong network Jan 1 01:05:47 unknown daemon.info dnsmasq-dhcp[1696]: DHCPDISCOVER(br0) 5c:ac:4c:7c:cd:a8 Jan 1 01:05:47 unknown daemon.info dnsmasq-dhcp[1696]: DHCPOFFER(br0) 192.168.1.40 5c:ac:4c:7c:cd:a8 Jan 1 01:05:47 unknown daemon.info dnsmasq-dhcp[1696]: DHCPREQUEST(br0) 192.168.1.40 5c:ac:4c:7c:cd:a8 Jan 1 01:05:47 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.40 5c:ac:4c:7c:cd:a8 Marcin_Laptop Jan 1 01:05:48 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:50 unknown daemon.info dnsmasq-dhcp[1696]: DHCPINFORM(br0) 192.168.1.40 5c:ac:4c:7c:cd:a8 Jan 1 01:05:50 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.40 5c:ac:4c:7c:cd:a8 Marcin_Laptop Jan 1 01:05:53 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:05:58 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:04 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:09 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:14 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:19 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:24 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:27 unknown daemon.info dnsmasq-dhcp[1696]: DHCPREQUEST(br0) 192.168.1.27 00:24:54:b6:42:f9 Jan 1 01:06:27 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.27 00:24:54:b6:42:f9 Marcin_Laptop Jan 1 01:06:29 unknown user.notice root: 4G MODEM - device not ready ... Jan 1 01:06:31 unknown daemon.info dnsmasq-dhcp[1696]: DHCPINFORM(br0) 192.168.1.27 00:24:54:b6:42:f9 Jan 1 01:06:31 unknown daemon.info dnsmasq-dhcp[1696]: DHCPACK(br0) 192.168.1.27 00:24:54:b6:42:f9 Marcin_Laptop Jan 1 01:06:34 unknown user.notice root: 4G MODEM - device not ready ... [EDIT] i cały plik http://wklej.org/id/1661515/ Połączony z 13 March 2015 16:48:17: Przełonczyłem przed chwila na 3G modem i ze zdziwieniem zobaczyłem jasno-niebieską stale świecącą diodę na modemie i w overview routera było że połączony ale na kompie strony się nie ładuja kolejny log http://wklej.org/id/1661528/ Połączony z 13 March 2015 17:24:25: dodam, że wcześniej też prubowałem z 3G modem ale było to samo co na 4G i w sumie gdyby na 3G zadziałał to by wystarczyło bo i tak LTE mi nawet z kompa nie złapało. Połączony z 13 March 2015 17:30:05: zazwyczaj UMTS lub HSPA+ żadziej DC+HSPA i ok -90 do -85 sygnał na drucie miedzianym na antenach "kupnych" nie idzie nic znaleźć co najwyżej -94 do -90 Edytowany przez marcin009988 dnia 13-03-2015 17:30


shibby	#10 Dodano 13-03-2015 18:46
SysOp Posty: 17067 Dołączył: 15/01/2009 20:30	powiem tak, sukces jest bo wykrywa ci już interfejsy ttyusb, tak wirc aktualizacja usbmodeswitch była na plus. w pierwszym przypadju cis go przyblokowalo bo wszystkie interfejsy miał ale nie mógł modelu przygotować. w drugim przypadku na 3G się połączył bo tu też jest używany interfejs ttyusb. zrób tak: wyciągnij modem, zresetuj router, podłącz moden i dopiero włącz 4g na wan. Proxmox VE: i7-7700T, 64GB RAM, 3x2TB SSD, 1x1TB SSD, 512GB NVMe, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology DS920+ VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


marcin009988	#11 Dodano 13-03-2015 19:17
User Posty: 43 Dołączył: 12/03/2015 14:05	Coś poszło dalej bo miga niebieska dioda na modemie czyli sieć wykrywa tylko łączyć się nie chce (ćwieciłaby stale wg opisu z manuala), a w overview cały czas wyświetla retriving. log:http://wklej.org/id/1661674/ A o co chodzi z tym że na 3G niby połączony ale net nie działa? Edytowany przez marcin009988 dnia 13-03-2015 19:25 ASUS RT-AC68U + tomato-ARM-134-AIO + Huawei e3372s-153 [no HiLink] ASUS RT-N18U + tomato-ARM-132-AIO + 2xHDD


domestos007	#12 Dodano 13-03-2015 20:17
User Posty: 161 Dołączył: 26/04/2012 15:36	Mam ten sam problem jak ustawie na 4G/LTE to nie dostaję adresów, modem z Play-a nie hilink. Aktualnie działa u mnie lte jako zwykły modem ustawiony na 3G. Transfery na poziomie 2-3.5 MB/s także nie jest źle ale pewnie lepiej jakby działał w trybie 4G/LTE. Cytat marcin009988 napisał(a): A o co chodzi z tym że na 3G niby połączony ale net nie działa? sprawdź czy pobiera adresy ip. Edytowany przez domestos007 dnia 13-03-2015 20:27


marcin009988	#13 Dodano 13-03-2015 20:22
User Posty: 43 Dołączył: 12/03/2015 14:05	z ciekawości wróciłem na 3G i znów na kompie brak neta ale zrobiłem z menu rouera pinga na wp.pl i bez odpowiedzi (100% straconych pakietów), potem dałem ip do wp i 0% straconych pakietów czyli tak jakby dns nie działał, więc znalazłem ustawiłem w Networks/Lan dnsy googla i teraz w pingu z rutera normalnie do wp pakiety idą ale nie zawsze i ze stratami 40% Połączony z 13 March 2015 20:36:52: Przerabiania na HiLink chciałem uniknąć i zostawić jako ostateczność, bo poczytałem już o tym wcześniej i niektórzy pisali że była różnica w transferach przez podwójny NAT. Połączony z 13 March 2015 21:24:11: z tymi DNSami net działa na kompach ale koszmarnie. Na speedteście Pingu nie robi (0), DL 0,2-0,3Mb,UL 0 wpiąłem do kompa i to samo czyli znowu orange z nadajnikami fiksuje bo wczoraj na kompie 1,2-2,5Mb spokojnie ciągną co dawało komfortowe www. Oczywiście modem z "drutami antenowymi" cały czas w tym samym miejscu na oknie taśmą przyklejony i tylko przedłużkę przepinam. Edytowany przez marcin009988 dnia 13-03-2015 21:24 ASUS RT-AC68U + tomato-ARM-134-AIO + Huawei e3372s-153 [no HiLink] ASUS RT-N18U + tomato-ARM-132-AIO + 2xHDD


domestos007	#14 Dodano 14-03-2015 09:04
User Posty: 161 Dołączył: 26/04/2012 15:36	Może potrzebujesz mocniejszej anteny mam na zbyciu parę modeli w dobrej cenie.


marcin009988	#15 Dodano 14-03-2015 09:39
User Posty: 43 Dołączył: 12/03/2015 14:05	Jeżeli chodzi o anteny to musiały by być dookólne bo z odbić gdzieś łapię i kierunkowe nie zdają egzaminu już kilka takich sprawdzałem i kupnych i BiQuada samoróbki co ciekawe moje samoróbki lepiej chodziły, bo niby moc sygnału taka sama jak w kupnych ale prędkości trochę wyższe i stabilniejsze byly, ale i tak najlepiej łapie prosty kawałek miedziaka prosto w złącze anteny wsadzony (czyli najprostsa dokólna antena jak mi się zdaje). Połączony z 15 March 2015 18:53:24: Podsumowując modem odpalił w 3g po wgraniu (jak mi polecił Shibby) tego obrazu < shibby ciach. proszę nie publikować testowych obrazów >[/url] A czy kolwiek u mnie prawdopodobni po prostu 4g(LTE) nie łapie i też będzie działć. Dzięki za pomoc i myślę, że temat do zamknięcia Edytowany przez shibby dnia 15-03-2015 19:01 ASUS RT-AC68U + tomato-ARM-134-AIO + Huawei e3372s-153 [no HiLink] ASUS RT-N18U + tomato-ARM-132-AIO + 2xHDD


domestos007	#16 Dodano 15-03-2015 20:28
User Posty: 161 Dołączył: 26/04/2012 15:36	U mnie działa lte ustawione jako 3G świeci się dioda na niebiesko, jak przestawię na 4G/LTE mam dokładnie to samo " 4G MODEM - device not ready ...".


marcin009988	#17 Dodano 16-03-2015 09:43
User Posty: 43 Dołączył: 12/03/2015 14:05	jasno niebieska świeci się też przy DC+HSPA ( w top_netinfo jako HSPA++) przynajmniej w kompie tak miałem na managerach ASUS RT-AC68U + tomato-ARM-134-AIO + Huawei e3372s-153 [no HiLink] ASUS RT-N18U + tomato-ARM-132-AIO + 2xHDD


domestos007	#18 Dodano 16-03-2015 10:12
User Posty: 161 Dołączył: 26/04/2012 15:36	Gdyby było tak jak piszesz to już dawno zjadłoby mi cały transfer, a dalej mam tyle ile miałem pierwotnie na koncie czyli bryka w lte i jest na razie za free. Tak jak piszesz to według mnie powinna się świecić na zielono ale może się mylę. Teraz sprawdzałem i za 5 dni jest ściągnięte 48 GB danych czyli ewidentnie bryka w lte.


marcin009988	#19 Dodano 16-03-2015 12:32
User Posty: 43 Dołączył: 12/03/2015 14:05	Chodziło mi o to że świeci na ten kolor TEŻ przy DC+HSPA czyli można powiedzieć że oba standardy traktuje jako 4g a nie tylko LTE Połączony z 16 March 2015 12:52:47: A jest może jakaś komenda do sprawdzenia jakości sygnału i technologi w jakiej jest połączony modem? Połączony z 10 marzec 2016 19:44:21: Od kilku dni mam problem z łączeniem się do neta. Jak modem jest wpięty do routera to muszę kombinować, żeby się połączył. Od czasu ostatnich problemów z tego wątku, wystarczyło w ustawieniach wyłączyć i włączyć obsługę usb, a w najgorszym przypadku zrobić reboota też z poziomu stronki. Jednak od może 10 dni zaczęło robić się coraz gorzej i teraz dopiero po kilku wyłączeniach i włączania zasilania, wypinaniach i wpinaniach modemu udaje się połączyć. Oczywiście jak do kompa wpinam to łapie od strzału i nie ma problemów. Próbowałem wpiąć z zasilanym USB, żeby sprawdzić czy czasem zwyczajnie prądu nie brakuje, ale też nie pomogło, a nawet ani razu się w routerze nie połączył, a w kompie znowu bez problemów. nie wiem czy to wina skryptów czy sterownika w routerze, ale jest coraz gorzej. O ile manewry na stronce mi nie przeszkadzały, to już jak muszę podejść do routera, i nieraz ze 40min walczyć żeby zadziałał to już przegięcie. wklejka z ostatnim logiem: http://wklej.org/id/2080346/ A no i teraz dużo krócej trzyma połączenie. Wcześniej nawet 3 dni bez przerw w połączeniu, a teraz do 2 razy dziennie zrywa. Połączony z 10 marzec 2016 19:58:25: Zasysam już najnowszy firmware i zobaczymy czy będzie poprawa Połączony z 10 marzec 2016 20:46:59: Dobra nowy soft wgrany i jak na razie wychodzi, że zrobiłem z siebie głupka, bo zamiast najpierw wgrywać nówkę to wziąłem się za pisanie postu. Jest mega poprawa, przynajmniej w łączeniu, bo ile razy mym nie przeskakiwał między trybami 3G i 4G to na obu łączy po krótkiej chwili. Zobaczę jeszcze jak długo takie połączenie będzie utrzymywał. Edytowany przez marcin009988 dnia 10-03-2016 20:46 ASUS RT-AC68U + tomato-ARM-134-AIO + Huawei e3372s-153 [no HiLink] ASUS RT-N18U + tomato-ARM-132-AIO + 2xHDD


psi12	#20 Dodano 10-03-2016 22:54
User Posty: 28 Dołączył: 05/03/2016 00:08	Masz tez moze stacjonarne lacze i moglbys powiedziec jak dziala opcja failover? Chodzi mi glownie o czas przelaczania ze stacjonarnego na modem LTE. Potrzebuje backupu swojego lacza z UPC i mysle nad kupnem 4g-ac55u lub wlasnie modelu np jak Ac68u i podlaczeniu do niego modemu, lub po prostu z innego routera ethernetem na drugi WAN. Kwestia jak ten failover w ogole dziala

Strona 1 z 2: 12

Przejdź do forum

Zaloguj

Nie masz jeszcze konta? Zarejestruj się.

Zapomniałeś/aś hasła?

Aktualnie online

· Gości online: 6

· Użytkowników online: 0

· Łącznie użytkowników: 24,117
· Najnowszy użytkownik: Ja

Czat

Musisz się zalogować, aby opublikować wiadomość.

tamtosiamto

23-04-2024 12:35

modem bez smilocka?

man1

22-04-2024 23:27

Czy próbował ktoś uzywac karty voice (z nolimit GB) od tmobile w modemie /routerze? Da się jakoś to zrobić? Bo u mnie neta brak. E3372

tamtosiamto

31-03-2024 12:54

Wesolego jajka wszytskim forumowiczom

tamtosiamto

28-03-2024 23:24

tak, tak zgadza sie, ale ja pytam o wykluczenie noda na guest network w first set, i to nie dziala

Adooni

24-03-2024 13:16

Guest network is currently designed to allow the first set of each band (2.4G, 5G, 5G-1) available to the AiMesh node

tamtosiamto

24-03-2024 03:03

ale w 1 jest opcja do wyboru - dla calej sieci albo rutera only i wlasnie o tym mowie, ze nie dziala

Adooni

23-03-2024 16:31

w dokumencie asusa jest ze wlasnie dla 1 ma dzialac na nodach tez

tamtosiamto

23-03-2024 15:39

tak, ale nie zmienia to faktu, ze w pierwszej nie dziala wylaczanie aimesh dla goscinnej( a powinno), czyli jest jakis bug. Mam start soft, bo to dsl-ac68 ktory nie jest juz updateowany

Adooni

22-03-2024 18:07

nie, 1 wsza bedzie wszedzie trzeba 2ga zrobic dla kazdego pasma te nie sa przenoszone

tamtosiamto

19-03-2024 19:57

czyli jak mam jedna siec goscinna to powinno dzialac separowanie gosci od noda -a nie dziala

Archiwum shoutboksa

71,327,625 unikalnych wizyt