Forum: [MOD] Tomato by shibby

Nawigacja

· Tomato by Shibby
· FreshTomato

Wątki na forum

Najnowsze dyskusje

· [S] Asus RT-AC56U
· DIR868l OFW asus vs ...
· Szukam zaproszenia n...
· [MOD] FreshTomato-AR...
· Asus RT-AC5300 ,prob...
· archer c6 v3.20
· [S] Nighthawk R7000P...
· [S]Asus RT-AC5300 - ...
· Tanie N100 na promce...
· net z telefonu wifi+...
· Tomato - bugi/proble...
· HUAWEI z światłowodem
· Asus TUF-AX3000_V2 p...
· rt-ax88upro częste ...
· [Howto] Xpenology na...
· Jaki router pod Open...
· Ruter z tomato
· Czy to jeszcze NAS?
· RT AC66U B1
· Wireguard na FreshTo...

Najpopularniejsze obecnie wątki

· DIR868l OFW asus ...	[8]
· [S] Asus RT-AC56U	[0]

Ankieta

Jaki procesor posiada twój router?

Broadcom MIPSEL

36% [151 głosów]

Broadcom ARM

52% [219 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: 419
Musisz zalogować się, aby móc zagłosować.
Rozpoczęto: 02/02/2015 09:38

Twoje IP

18.117.71.239

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 » :: OPROGRAMOWANIE :: » Tomato - firmware

Strona 478 z 687: 1...475 476 477478479 480 481...687

[MOD] Tomato by shibby
glorifyday	#9541 Dodano 23-07-2014 20:22
User Posty: 32 Dołączył: 29/05/2013 14:14	Cytat Przywróć tryb gateway. Router czy gateway, wsjo ryba, zachowanie takie samo: 1. klient podlacza sie po wifi najpierw do RT-N16 - widac klientow wifi z Linksysa, 2. przechodze z pokoju do pokoju, klient traci polaczenie z RT-N16, laczy sie z linksysem - widac klientow wifi z Linksysa, 3. wracam do pokoju z RT-N16, klient rozlacza sie z linksysyem, laczy z RT-N16 - klienci z linksysa znikaja. Jak sie znowu przelacze na linksysa i wylacze wifi w komorce (kliencie), z wylaczonym przejde do pokoju z RT-N16, to moge powrocic do punktu 1. Nie wiem, na ile to jest powtarzalne, ale pare razy mi sie tak udalo zrobic. Osobna sprawa... co sie stalo z /usr/bin/ether-wake ? Połączony z 24 lipiec 2014 01:47:18: EDIT: znalazlem ether-wake, przeniesione do /usr/sbin. Edytowany przez glorifyday dnia 24-07-2014 01:47


jwshields	#9542 Dodano 25-07-2014 05:29
User Posty: 6 Dołączył: 25/07/2014 05:22	I tylko po angielsku. Moje przeprosiny --------------- I am having a problem with Tomato Firmware 1.28.0000 MIPSR2-121 K26 USB Max on a Linksys E2500 V1 router. The router has been randomly crashing and rebooting. I was able to capture a log for it, any help would be appreciated. Here is a log: http://pastebin.com/j4t1n0gJ Problem begins at line 59, "Jul 24 20:10:04"


shibby	#9543 Dodano 25-07-2014 08:48
SysOp Posty: 17109 Dołączył: 15/01/2009 20:30	did you erase nvram? Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology SA6400 VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


kille72	#9544 Dodano 25-07-2014 12:23
Administrator Posty: 2986 Dołączył: 12/02/2007 23:43	WRT54GL postawiony u kumpla z Tomato 034H ND Std, chyba okolo 3 lata temu, zapomnialem nawet o nim Zero problemow, uptime na dzien dzisiejszy to 201 dni!


l200	#9545 Dodano 25-07-2014 13:27
User Posty: 2 Dołączył: 25/07/2014 12:23	Hi Shibby and other! I love your job. Offer. For support usb-to-lan host modems. ( example LU150: Vendor=1076 ProdID=8003 Manufacturer=GCT SEMICONDUCTOR Inc ) Insert the support USB Host side RNDIS driver. Pleeease! -) p.s. download rndis_host.ko vermagic=2.6.22.19 mod_unload MIPS32_R2 32BIT https://cloud.mail.ru/public/815f8897...is_host.ko Edytowany przez l200 dnia 25-07-2014 13:32


44hunter	#9546 Dodano 25-07-2014 14:45
User Posty: 4 Dołączył: 25/07/2014 14:38	bry, może dorzuce coś od siebie co do LTE i E3272 (mam go od play ale bez hilink) bo łączy sie przez jakąś playową apke i nie ma dostepu do panela przez 192.168.1.1, akurat z zasięgiem u mnie nie ma problemu bo mam BTS 200 m za oknem i tu pytanie dziad łączy sie w LTE jak podepne do kompa, wcześniej miałem ruter asusa dsl-n55u do netii, po wpięciu go do tego rutera i ustawieniu dual wan auto auto bla bla bla, od kopa startuje i łączy sie w LTE (transfery takie same jak na kompie jedynie jak na komputerze miałem upload 10 to tu jest 3,5mbit ale dioda świeci na taki sam kolor więc to chyba LTE bo na 3g downloadu bym 30mbit nie osiągnał? i tu pytanie chce to sprzedać i kupić albo asus rt-n66u ze względu na tomato, tylko czo to będzie śmigać w LTE? bo transfer bez limitu mam na lte a nie 3g albo nie pierdzielić sie z tomato i brać airlive n450r no i na tym działa w LTE no ale nie ma tomato ;/


shibby	#9547 Dodano 25-07-2014 15:50
SysOp Posty: 17109 Dołączył: 15/01/2009 20:30	na asusie nie działa w LTE, chyba że masz jakiś naprawdę świeży firmware wgrany (o czym w changelogu pisało), bo asus obsługę LTE do swoich softów dopiero wdraża. Co do koloru diody to ja mam E3276 i nie ważne czy łączę się na 3G czy LTE to kolor diody jest taki sam (błękitna), tak więc kolor nie może być wyznacznikiem). Jak zalogujesz się do routera telnetem po podeślesz mi logi z wykrycia modemu i nawiązania połączenia to powiem ci czy na tomato ruszy I jeszcze jedna uwaga ode mnie: Ja mam u siebie dość słaby sygnał LTE (jedna, dwie kreski - tmobile). Nie mniej jednak prędkości DL mam bardzo posobne zarówno w LTE jak i w 3G (ok 10-12Mbps). Natomiast upload jest znacznie wyższy na LTE - ok 10mbps, natomiast na 3G mam właśnie ok 3mbps. Identyczna zależność jak u ciebie Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology SA6400 VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


44hunter	#9548 Dodano 25-07-2014 16:18
User Posty: 4 Dołączył: 25/07/2014 14:38	toś mnie zmartwił :D zamówilem już tego airlive, jakby co to zwróce, tylko musze sie sprężać bo testowanie tego neta mam do wtorku :D tj musze oddać albo zostaje z badziewiem :) wiem że to pewnie tu jest na forum, putty mam, wiem jak sie zalogować, ale jak pobrać logi z tego dsl-n55u tyle że tam tomato sie wrzucić nie da :) to mowie przyszlosciowo o tym rt-n66u aha nadmienie iż ten download jak mam modem w kompie to mam rzędu 30mbit czyli max co na play i jak wepne w tego asusa n55u to też mam 30 mbit tylko upload z 10 spada do 3 albo 4 Kod Pobierz kod źródłowy lsmod Module Size Used by Tainted: P nf_nat_sip 4224 0 nf_conntrack_sip 8960 1 nf_nat_sip nf_nat_h323 6912 0 nf_conntrack_h323 50304 1 nf_nat_h323 nf_nat_rtsp 5552 0 nf_conntrack_rtsp 7488 1 nf_nat_rtsp nf_nat_ftp 2688 0 nf_conntrack_ftp 8224 1 nf_nat_ftp ip6table_filter 1888 0 ip6table_mangle 2016 0 option 41008 1 usbserial 32704 3 option sr_mod 16240 0 cdrom 43008 1 sr_mod zaurus 4128 0 net1080 5216 0 rndis_host 5792 0 cdc_ether 5248 2 zaurus,rndis_host asix 17184 0 usbnet 17872 5 zaurus,net1080,rndis_host,cdc_ether,asix usblp 13376 0 ohci_hcd 27728 0 ehci_hcd 47408 0 ufsd 308880 1 vfat 11840 0 fat 58480 1 vfat ext2 68512 0 ext3 138336 0 jbd 64224 1 ext3 mbcache 7472 2 ext2,ext3 usb_storage 100000 1 sg 31968 0 sd_mod 27840 2 scsi_wait_scan 960 0 scsi_mod 107520 5 sr_mod,usb_storage,sg,sd_mod,scsi_wait_scan usbcore 159936 13 option,usbserial,zaurus,net1080,rndis_host,cdc_ether,asix,usbnet,usblp,ohci_hcd,ehci_hcd,usb_storage nf_nat_pptp 2816 0 nf_conntrack_pptp 6064 1 nf_nat_pptp nf_nat_proto_gre 2096 1 nf_nat_pptp nf_conntrack_proto_gre 4192 1 nf_conntrack_pptp RTPCI_ap 1271424 1 rt2860v2_ap 1482320 1 nvram_linux 19536 36 RTPCI_ap,rt2860v2_ap Edytowany przez 44hunter dnia 25-07-2014 16:30


shibby	#9549 Dodano 25-07-2014 17:33
SysOp Posty: 17109 Dołączył: 15/01/2009 20:30	Cytat cdc_ether 5248 2 zaurus,rndis_host usbnet 17872 5 zaurus,net1080,rndis_host,cdc_ether,asix to może wskazywać na to, że modem faktycznie działa jako LTE. Pokaż proszę wynik komendy dmesg, Najlepiej zaraz po restarcie routera i nawiązaniu połączenia 3G/LTE Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology SA6400 VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


jwshields	#9550 Dodano 25-07-2014 17:35
User Posty: 6 Dołączył: 25/07/2014 05:22	Cytat shibby napisał(a): did you erase nvram? I just erased the NVRAM, reconfiguring my router right now. I will report back. I just wanted to thank you for this project, you're great!


44hunter	#9551 Dodano 25-07-2014 17:56
User Posty: 4 Dołączył: 25/07/2014 14:38	usbcore: registered new interface driver zaurus eth2.1.2: add 33:33:00:00:00:01 mcast address to master interface eth2.1.2: add 01:00:5e:00:00:01 mcast address to master interface eth2.1.2: dev_set_promiscuity(master, 1) eth2.1: dev_set_promiscuity(master, 1) device eth2 entered promiscuous mode eth2.1: add 01:00:5e:00:00:01 mcast address to master interface eth2.1: add 33:33:00:00:00:01 mcast address to master interface device eth2.1 entered promiscuous mode device eth2.1.2 entered promiscuous mode tp_init uses obsolete (PF_INET,SOCK_PACKET) br1: port 1(eth2.1.2) entering learning state br0: starting userspace STP failed, starting kernel STP eth2.2: dev_set_promiscuity(master, 1) device eth2.2 entered promiscuous mode RX DESC a76d2000 size = 2048 RtmpChipOpsEepromHook::e2p_type=0, inf_Type=5 NVM is FLASH mode 1. Phy Mode = 6 2. Phy Mode = 6 3. Phy Mode = 6 AntCfgInit: primary/secondary ant 0/1 RTMPSetPhyMode: channel is out of range, use first channel=0 MCS Set = ff ff 00 00 01 SYNC - BBP R4 to 20MHz.l scsi 0:0:0:0: Direct-Access ADATA HD710 AX00 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 1465149168 512-byte hardware sectors (750156 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Assuming drive cache: write through sda:<5>scsi 1:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANS I: 2 scsi 1:0:0:0: Attached scsi generic sg0 type 5 scsi 2:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 sd 2:0:0:0: [sdb] Attached SCSI removable disk sd 2:0:0:0: Attached scsi generic sg1 type 0 usbcore: registered new interface driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1- port) option 1-2:1.0: GSM modem (1-port) converter detected usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0 option 1-2:1.1: GSM modem (1-port) converter detected usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1 option 1-2:1.2: GSM modem (1-port) converter detected usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2 usbcore: registered new interface driver option drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.2 sda1 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg2 type 0 sr0: scsi-1 drive Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi CD-ROM sr0 ufsd: use builtin utf8 instead of kernel utf8 eth2: no IPv6 routers present ufsd: sda1 without journal ===================================================== Channel 1 : Dirty = 0, False CCA = 17, Busy Time = 326, Skip Channel = FALSE Channel 2 : Dirty = 0, False CCA = 21, Busy Time = 487, Skip Channel = FALSE Channel 3 : Dirty = 0, False CCA = 15, Busy Time = 88, Skip Channel = FALSE Channel 4 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 5 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 6 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 7 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 8 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 9 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 10 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 11 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 12 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 13 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE ===================================================== Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 1 Min Dirty = 0 ExChannel = 5 , 0 BW = 40 Main bssid = e0:3f:49:96:10:08 <==== rt28xx_init, Status=0 0x1300 = 00064380 device rai0 entered promiscuous mode RX DESC a5bc3000 size = 2048 <-- RTMPAllocTxRxRingMemory, Status=0 1. Phy Mode = 11 2. Phy Mode = 11 3. Phy Mode = 11 AntCfgInit: primary/secondary ant 0/1 RTMPSetPhyMode: channel is out of range, use first channel=0 MCS Set = ff ff ff 00 01 SYNC - BBP R4 to 20MHz.l ===================================================== Channel 36 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 40 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 44 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 48 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE ===================================================== Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 36 Min Dirty = 0 ExChannel = 0 , 0 BW = 40 Main bssid = e0:3f:49:96:10:0c <==== rt28xx_init, Status=0 0x1300 = 00064380 device ra0 entered promiscuous mode br0: topology change detected, propagating br0: port 3(ra0) entering forwarding state br0: topology change detected, propagating br0: port 2(rai0) entering forwarding state br0: topology change detected, propagating br0: port 1(eth2.2) entering forwarding state eth2.1: add 33:33:00:00:00:02 mcast address to master interface eth2.2: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.1.2: add 33:33:00:00:00:02 mcast address to master interface set watchdog pid as: 435 set watchdog pid as: 435 eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.1.2: del 33:33:00:00:00:02 mcast address from vlan interface eth2.1.2: del 33:33:00:00:00:02 mcast address from master interface eth2.1.2: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.1.2: del 01:00:5e:00:00:01 mcast address from master interface eth2.1.2: del 33:33:00:00:00:01 mcast address from vlan interface eth2.1.2: del 33:33:00:00:00:01 mcast address from master interface br1: port 1(eth2.1.2) entering disabled state eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface nf_conntrack_rtsp v0.6.21 loading nf_nat_rtsp v0.6.21 loading tego e3272 to mam bez hilink bynajmiej na nim nie pisze ze go ma, to dobrze czy źle? bo jak mowilem nie dam rady sie zalogowac do bramy jak podepne do kompa, tylko jakaś apka z play sie instaluje Edytowany przez 44hunter dnia 25-07-2014 18:05


shibby	#9552 Dodano 25-07-2014 18:12
SysOp Posty: 17109 Dołączył: 15/01/2009 20:30	Trochę mało. Widać jak moduł option wykrywa modem. Nie widać natomiast ładowania pozostałych modułów, nie widać też danego momentu łączenia. Jeżeli faktycznie option używany jest do łączenia to mam złe wieści. To był kompletny log? Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology SA6400 VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


44hunter	#9553 Dodano 25-07-2014 18:14
User Posty: 4 Dołączył: 25/07/2014 14:38	usbcore: registered new interface driver zaurus eth2.1.2: add 33:33:00:00:00:01 mcast address to master interface eth2.1.2: add 01:00:5e:00:00:01 mcast address to master interface eth2.1.2: dev_set_promiscuity(master, 1) eth2.1: dev_set_promiscuity(master, 1) device eth2 entered promiscuous mode eth2.1: add 01:00:5e:00:00:01 mcast address to master interface eth2.1: add 33:33:00:00:00:01 mcast address to master interface device eth2.1 entered promiscuous mode device eth2.1.2 entered promiscuous mode tp_init uses obsolete (PF_INET,SOCK_PACKET) br1: port 1(eth2.1.2) entering learning state br0: starting userspace STP failed, starting kernel STP eth2.2: dev_set_promiscuity(master, 1) device eth2.2 entered promiscuous mode RX DESC a76d2000 size = 2048 RtmpChipOpsEepromHook::e2p_type=0, inf_Type=5 NVM is FLASH mode 1. Phy Mode = 6 2. Phy Mode = 6 3. Phy Mode = 6 AntCfgInit: primary/secondary ant 0/1 RTMPSetPhyMode: channel is out of range, use first channel=0 MCS Set = ff ff 00 00 01 SYNC - BBP R4 to 20MHz.l scsi 0:0:0:0: Direct-Access ADATA HD710 AX00 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 1465149168 512-byte hardware sectors (750156 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Assuming drive cache: write through sda:<5>scsi 1:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 scsi 1:0:0:0: Attached scsi generic sg0 type 5 scsi 2:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 sd 2:0:0:0: [sdb] Attached SCSI removable disk sd 2:0:0:0: Attached scsi generic sg1 type 0 usbcore: registered new interface driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port) option 1-2:1.0: GSM modem (1-port) converter detected usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0 option 1-2:1.1: GSM modem (1-port) converter detected usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1 option 1-2:1.2: GSM modem (1-port) converter detected usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2 usbcore: registered new interface driver option drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.2 sda1 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg2 type 0 sr0: scsi-1 drive Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi CD-ROM sr0 ufsd: use builtin utf8 instead of kernel utf8 eth2: no IPv6 routers present ufsd: sda1 without journal ===================================================== Channel 1 : Dirty = 0, False CCA = 17, Busy Time = 326, Skip Channel = FALSE Channel 2 : Dirty = 0, False CCA = 21, Busy Time = 487, Skip Channel = FALSE Channel 3 : Dirty = 0, False CCA = 15, Busy Time = 88, Skip Channel = FALSE Channel 4 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 5 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 6 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 7 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 8 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 9 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 10 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 11 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 12 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 13 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE ===================================================== Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 1 Min Dirty = 0 ExChannel = 5 , 0 BW = 40 Main bssid = e0:3f:49:96:10:08 <==== rt28xx_init, Status=0 0x1300 = 00064380 device rai0 entered promiscuous mode RX DESC a5bc3000 size = 2048 <-- RTMPAllocTxRxRingMemory, Status=0 1. Phy Mode = 11 2. Phy Mode = 11 3. Phy Mode = 11 AntCfgInit: primary/secondary ant 0/1 RTMPSetPhyMode: channel is out of range, use first channel=0 MCS Set = ff ff ff 00 01 SYNC - BBP R4 to 20MHz.l ===================================================== Channel 36 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 40 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 44 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE Channel 48 : Dirty = 0, False CCA = 0, Busy Time = 0, Skip Channel = FALSE ===================================================== Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 36 Min Dirty = 0 ExChannel = 0 , 0 BW = 40 Main bssid = e0:3f:49:96:10:0c <==== rt28xx_init, Status=0 0x1300 = 00064380 device ra0 entered promiscuous mode br0: topology change detected, propagating br0: port 3(ra0) entering forwarding state br0: topology change detected, propagating br0: port 2(rai0) entering forwarding state br0: topology change detected, propagating br0: port 1(eth2.2) entering forwarding state eth2.1: add 33:33:00:00:00:02 mcast address to master interface eth2.2: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.1.2: add 33:33:00:00:00:02 mcast address to master interface set watchdog pid as: 435 set watchdog pid as: 435 eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.1.2: del 33:33:00:00:00:02 mcast address from vlan interface eth2.1.2: del 33:33:00:00:00:02 mcast address from master interface eth2.1.2: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.1.2: del 01:00:5e:00:00:01 mcast address from master interface eth2.1.2: del 33:33:00:00:00:01 mcast address from vlan interface eth2.1.2: del 33:33:00:00:00:01 mcast address from master interface br1: port 1(eth2.1.2) entering disabled state eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface eth2.4: del 33:33:00:00:00:01 mcast address from vlan interface eth2.4: del 33:33:00:00:00:01 mcast address from master interface eth2.4: del 33:33:00:00:00:02 mcast address from vlan interface eth2.4: del 33:33:00:00:00:02 mcast address from master interface eth2.4: del 01:00:5e:00:00:01 mcast address from vlan interface eth2.4: del 01:00:5e:00:00:01 mcast address from master interface eth2.4: Setting MAC address to e0 3f 49 96 10 08. eth2.4: add 01:00:5e:00:00:01 mcast address to master interface eth2.4: add 33:33:00:00:00:02 mcast address to master interface eth2.4: add 33:33:00:00:00:01 mcast address to master interface nf_conntrack_rtsp v0.6.21 loading nf_nat_rtsp v0.6.21 loading to raz jeszcze wiecej nic nie ma, tak czy siak idzie do żyda, grunt żeby na n450r działał LTE, tylko jak mam to stwierdzić skoro kolor diody to lipa


shibby	#9554 Dodano 25-07-2014 23:42
SysOp Posty: 17109 Dołączył: 15/01/2009 20:30	ok, pokaż jeszcze ifconfig (wrażliwe dane jak ip możesz ukryć jak chcesz). Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology SA6400 VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2


luckyluc	#9555 Dodano 27-07-2014 04:25
User Posty: 2 Dołączył: 17/12/2009 18:09	nie byłem w stanie przywrócić ustawień z pliku na nowym routerze pomimo zmiany maców na takie jak w starym routerze (jednego maca nie da się zmienić). Czy istnieje jakiś sposób na odczytanie ustawień QOS z pliku backup ?


Sigma	#9556 Dodano 27-07-2014 08:41
Power User Posty: 382 Dołączył: 01/09/2011 08:32	Plik cfg to archiwum, które otworzysz np. 7zipem. W środku jest plik tekstowy. A w nim są ustawienia. [small]Netgear WNR3500L powered by Tomato Firmware 1.28.0000 MIPSR2-130 K26 USB BTGui Netgear WNDR4300 powered by OpenWrt Chaos Calmer 15.05 (r47662) TP-Link TL-WDR4300 v1 powered by OpenWrt Chaos Calmer 15.05 (r47662) [b]TP-Link T


l200	#9557 Dodano 28-07-2014 08:15
User Posty: 2 Dołączył: 25/07/2014 12:23	44hunter. Switch your huawei e3272 to modem mode only. By dint of AT-command. Or when waiting Shibby insert the support USB Host side RNDIS driver ( rndis_host.ko ) in FW.


kamkil	#9558 Dodano 28-07-2014 09:32
User Posty: 11 Dołączył: 23/04/2012 14:56	Mam problem z Web serwerem nginx w wydaniu AIO. Zmodyfikowałem plik ręcznie i po każdym restarcie zmiany nie są zapamiętane. W zakładce Web Server mam zaznaczone "Keep Config Files" ale wygląda na to że to nie działa. Czy ktoś również ma z tym problem? A druga sprawa czy była by możliwość wyboru numeru portu dla WAN i LAN ? Chciałbym żeby serwer WWW ze strony WAN był na porcie 80 a w LAN na innym np. standardowy 85. Aktualnie zrobiłem przekierowanie portu 80 na port 85 ale w takim ustawieniu ze strony WAN serwer odpowiada na porcie 80 i 85. Asus RT-AC68U + FreshTomato Firmware 2021.7 K26ARM USB AIO-64K


compsjp	#9559 Dodano 28-07-2014 11:05
User Posty: 70 Dołączył: 25/05/2014 17:38	so i can handle more congestion, only if i dont use pptp, and weirdly 2.4ghz got to have a bug, cause 5ghz is flawless, i changed country codes, no different. mainly tried US and SG, and i would normally use SG 1 RT-AC68U 128 SHIBBY AIO ARM 1 RT-N16 128 SHIBBY AIO K26 1 RT-N12(B1) DD-WRT v24-sp2 (05/27/13) mega SOLD 1 rt-n12 128 SHIBBY MINI-IPV6 1 WNR2000V2 MIPSR2-128 K26 Mini ipv6 1 WNR2000V3 OpenWrt Barrier Breaker 14.07 / LuCI 0.12 Branch (0.12+git-15.


shibby	#9560 Dodano 28-07-2014 16:24
SysOp Posty: 17109 Dołączył: 15/01/2009 20:30	Cytat kamkil napisał(a): Mam problem z Web serwerem nginx w wydaniu AIO. Zmodyfikowałem plik ręcznie i po każdym restarcie zmiany nie są zapamiętane. W zakładce Web Server mam zaznaczone "Keep Config Files" ale wygląda na to że to nie działa. Czy ktoś również ma z tym problem? A druga sprawa czy była by możliwość wyboru numeru portu dla WAN i LAN ? Chciałbym żeby serwer WWW ze strony WAN był na porcie 80 a w LAN na innym np. standardowy 85. Aktualnie zrobiłem przekierowanie portu 80 na port 85 ale w takim ustawieniu ze strony WAN serwer odpowiada na porcie 80 i 85. Na porcie 80 masz domyślnie gui tomato. Zmień ten port na np. 81 i wtedy nginxa wystaw na porcie 80. Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+ VM Router: OpenWRT 22.03.4 VM NAS: Synology SA6400 VM VPS: Debian, WWW, Home Assistant Switch: Netgear MS510TXPP Switch: Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi: Ubiquiti U6-Lite - szt. 2

Strona 478 z 687: 1...475 476 477478479 480 481...687

Przejdź do forum

Zaloguj

Nie masz jeszcze konta? Zarejestruj się.

Zapomniałeś/aś hasła?

Aktualnie online

· Gości online: 91

· Użytkowników online: 0

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

Czat

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

Maniek91PL

06-11-2024 22:37

dzięki !

maxikaaz

29-10-2024 14:27

@Maniek91PL - Administration=> Admin Access, i tam masz "Allow Wireless Access" do zaznaczenia

Maniek91PL

26-10-2024 22:07

siemka! ktoś przypomni co się ustawiało jeśli nie mogę wejść od strony wifi do tomato? od lan działa

overflow2

04-10-2024 17:34

Kupowałem Asusy n10u albo n12d1 ale nie widzę ich, chyba już nie produkują, Chodzi o coś nowego i taniego. Transfery niewielkie.

maxikaaz

04-10-2024 09:38

@overflow2 patrząc po dostępności funkcji w nowych kompilacjach, to chyba nawet WRT54G/GL jeszcze ma OpenVPN, albo jakiś odpowiednik... zależy, na jakie transfery liczysz.

overflow2

30-09-2024 20:53

Jaki aktualnie najtańszy router do tomato do openvpn?

maxikaaz

27-07-2024 15:07

@servee - na początek router do rozebrania i obejrzenia, ciężko wróżyć tak tylko po objawach

maxikaaz

27-07-2024 14:55

@servee - cały kontroler nie pada tak sobie z powodu "zbiegu okoliczności",
więc prawdopodobnie gdzieś przepięcie.

servee

25-07-2024 13:33

@maxikaaz: działało, aż pewnego pięknego dnia przestało działać. W tym dniu była też burza, ale to raczej zbieg okoliczności.

maxikaaz

25-07-2024 11:38

@servee - o ile problem jest w obrębie samych wyjść (dławiki, warystory), to naprawialne, ale jeśli w samym SoC - to nienaprawialne ze względu na koszta. A co było przyczyną?

Archiwum shoutboksa