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

2016-08-06 05:47:52

Swoją drogą, ktoś to głupie powiedzenie włożył Einsteinowi w usta i teraz wszyscy, jak baranki, powtarzają to przy różnych okazjach.

2016-05-21 21:34:18

Mam to samo od dawna na WDR3600 (CC 15.05), u mnie jedynie na interfejsie 2.4GHz występują te błędy. Na szczęście w działaniu wifi to w ogóle nie przeszkadza, sieć działa dobrze, jedynie zawala logi (co kilka dni parę takich linijek). Gdzieś na dev.openwrt.org wisi odpowiedni ticket od wielu lat, ale jeszcze nikt tego nie naprawił.

2015-11-10 20:50:01

Dzięki Cezary, bardzo przydatne

2015-11-10 14:08:53

Jak to zrobić po ssh (nie mam luci) ? Jakiś skrypt zapewne, może ktoś udostępnić?

2015-11-01 07:19:59

Cześć,

Potrzebuję zainstalować na routerze TP-Link TL-WDR3600 z CC program iptraf, ale nie ma go nigdzie w repozytorium. W sieci jest za to pełno ticketów, że się nie kompiluje, albo że już w ogóle nie jest wspierany. Może jednak ktoś próbował i komuś udało się go skompilować? Widziałem tu na forum, że przewijał się w niektórych tematach.
A jeżeli nie, to czy jest jakaś sensowna alternatywa o podobnej funkcjonalności?

Pozdrawiam

2015-06-14 09:17:29

OK, dzięki za pomoc

Na razie zrobiłem sobie skrypt, który mi wygrepowuje ten syf z logread i po prostu odpalam go zamiast "czystego" polecenia logread. Chociaż to mi w sumie niewiele daje, bo logread ma określony bufor, więc i tak nie widzę całej reszty logów.
We flashu już mi brakuje miejsca, poszukam jakiegoś starego pendrive i zainstaluje tam ten syslog-ng.
Tylko ciekawe czy na zasilaczu 5V/2A (oryginalny był 2.5A) w ogóle zadziała USB i będzie stabilne...

2015-06-13 23:13:59

Ok, a mógłbyś mi coś poradzić, żeby po prostu te wpisy mi nie zawalały logów? Da się założyć na logread jakiś skrypt z odpowiednim filtrem, np wygrepować to co niepotrzebne?

2015-06-13 18:05:01

Według logów problem jest na interfejsie wl0, a on sam w sobie nie ma przypisanego IP. Czyli mam ustawić w tcpdumpie wl0, br-lan czy eth0.0? Nie za bardzo to ogarniam. Może mam coś skopane w konfiguracji? Chociaż to by było dziwne, bo przez kilka lat nie zmieniałem nic w konfiguracji sieci i nie było takich problemów.

root@OpenWrt:/etc/config# cat wireless
config wifi-device      "wl0"
    option type         "broadcom"
    option channel      "1"
    option disabled     "0"

config wifi-iface
    option device       "wl0"
    option network      lan
    option mode         "ap"
    option ssid         "xxx"
    option hidden       "0"
    option encryption   "psk2"
    option key          xxx

root@OpenWrt:/etc/config# cat network

config 'switch' 'eth0'
        option 'vlan0' '1 2 3 4 5*'
        option 'vlan1' '0 5'

config 'interface' 'loopback'
        option 'ifname' 'lo'
        option 'proto' 'static'
        option 'ipaddr' '127.0.0.1'
        option 'netmask' '255.0.0.0'

config 'interface' 'lan'
        option 'type' 'bridge'
        option 'ifname' 'eth0.0'
        option 'proto' 'static'
        option 'ipaddr' '192.168.1.1'
        option 'netmask' '255.255.255.0'
        option 'wireless' 'wl0'

config 'interface' 'wan'
        option 'ifname' 'eth0.1'
        option 'proto' 'dhcp'

root@OpenWrt:/etc/config# cat dhcp
config dnsmasq
        option domainneeded     1
        option boguspriv        1
        option filterwin2k      '0'  #enable for dial on demand
        option localise_queries 1
        option local    '/lan/'
        option domain   'lan'
        option expandhosts      1
        option nonegcache       0
        option authoritative    1
        option readethers       1
        option leasefile        '/tmp/dhcp.leases'
        option resolvfile       '/tmp/resolv.conf.auto'

config dhcp lan
        option interface        lan
        option start    174
        option limit    25
        option leasetime        24h

config dhcp wan
        option interface        wan
        option ignore   1

Edit: w sieci na różnych forach czytam, że to częsty problem, ale nie ma jednoznacznego rozwiązania. Może to po prostu wina samego OpenWRT? Da się jakoś odfiltrować logread z tych wpisów? Bo szczerze mówiąc to nie mam czasu analizować tych wszystkich pakietów (może kiedyś, jak będę mieć więcej czasu to się tym pobawię).

2015-06-13 16:41:28

Jaką składnię wybrać dla tcpdumpa, żeby to sprawdzić?

Mój ifconfig wygląda tak:

root@OpenWrt:~# ifconfig -a
br-lan    Link encap:Ethernet  HWaddr 00:1E:8C:D3:8E:77
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:106325539 errors:0 dropped:0 overruns:0 frame:0
          TX packets:198560813 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2775974425 (2.5 GiB)  TX bytes:1800645014 (1.6 GiB)

eth0      Link encap:Ethernet  HWaddr 00:1E:8C:D3:8E:77
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:235576234 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130977130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3871720263 (3.6 GiB)  TX bytes:1176295689 (1.0 GiB)
          Interrupt:4

eth0.0    Link encap:Ethernet  HWaddr 00:1E:8C:D3:8E:77
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12256121 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25154518 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:775899467 (739.9 MiB)  TX bytes:271133592 (258.5 MiB)

eth0.1    Link encap:Ethernet  HWaddr 00:1E:8C:D3:8E:77
          inet addr: xx.xx.xx.xx  Bcast:255.255.255.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:223262982 errors:0 dropped:0 overruns:0 frame:0
          TX packets:105783213 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3074403203 (2.8 GiB)  TX bytes:210482564 (200.7 MiB)

eth1      Link encap:Ethernet  HWaddr 40:10:18:00:00:2D
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:5

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3140 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:299483 (292.4 KiB)  TX bytes:299483 (292.4 KiB)

wl0       Link encap:Ethernet  HWaddr 00:1E:8C:D3:8E:77
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:94980788 errors:759 dropped:0 overruns:0 frame:94744559
          TX packets:174557583 errors:107760 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4276189745 (3.9 GiB)  TX bytes:2377127067 (2.2 GiB)
          Interrupt:2 Base address:0x2000

Próbowałem dla br-lan i eth0.1 (to jest WAN, wyciąłem tylko mój zew. adres IP z powyższego) i w ogóle bez ustalania interfejsu, ale pokazuje tyle tego, że nie wiem czy po prostu żywcem to skopiować, czy można tam jakoś odfiltrować to co niepotrzebne? Jak potem interpretować te zrzuty?

Znalazłem na jakiejś stronie instrukcje, żeby zrzucać do pliku *.pcap i potem Wiresharkiem to sprawdzić, zaraz spróbuję.

Edit: ok, ogarnąłem to w Wiresharku, teraz tylko proszę o jakieś wskazówki na co patrzeć? Czy mam cały czas łapać pakiety tcpdumpem, czy tylko wtedy jak zobaczę, że te wpisy w logach się pojawiają (teraz np. już ich nie ma, ale pewnie za jakiś czas znowu zaleją mi logi), no i na jakim interfejsie słuchać tcpdumpem i co potem odfiltrowywać w Wiresharku?

2015-06-13 14:44:55

Ok, ale jak to sprawdzić/wykryć co sieje i się tego pozbyć? Jakiś sniffer się nada?

2015-06-13 14:27:21

Cześć,

Patrząc w logread i dmesg na routerze ASUS WL-500g Premium ze starym, ale stabilnym OpenWRT 8.09 (r14571 by obsy, kernel 2.4.35.4) zauważyłem pełno takich wpisów:

Jun 13 14:40:00 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:06 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:06 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:11 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:11 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:16 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:16 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:20 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:26 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:26 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:30 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:35 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:35 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:39 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:39 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:45 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:45 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:50 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:50 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:40:56 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:40:56 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:01 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:41:01 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:07 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:41:07 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:12 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:41:12 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:15 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:41:15 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:19 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:41:19 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:24 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:41:24 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:34 OpenWrt user.warn kernel: NET: 2 messages suppressed.
Jun 13 14:41:34 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:35 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:41 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:41:41 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:41:45 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:42:36 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:42:56 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:42:58 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:01 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:03 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:06 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:08 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:10 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:12 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:15 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:19 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:22 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:24 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:28 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:30 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:32 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:35 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:38 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:41 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:43 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:48 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:43:48 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:52 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:43:52 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:43:57 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:43:57 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:04 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:44:04 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:08 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:13 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:44:13 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:18 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:44:18 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:23 OpenWrt user.warn kernel: NET: 2 messages suppressed.
Jun 13 14:44:23 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:29 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:32 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:38 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:44:38 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:46 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:49 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:52 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:44:58 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:44:58 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:05 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:17 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:20 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:22 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:23 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:27 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:32 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:45:32 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:39 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:45 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:47 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:45:55 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:45:55 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:02 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:04 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:08 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:13 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:17 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:46:17 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:23 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:46:23 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:27 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:46:27 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:33 OpenWrt user.warn kernel: NET: 2 messages suppressed.
Jun 13 14:46:33 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:38 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:46:38 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:43 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:46:43 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:47 OpenWrt user.warn kernel: NET: 2 messages suppressed.
Jun 13 14:46:47 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:55 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:46:55 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:46:57 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:05 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:08 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:12 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:16 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:47:16 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:23 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:47:23 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:28 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:47:28 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:32 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:47:32 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:40 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:47:40 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:43 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:47 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:53 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:47:53 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:47:58 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:47:58 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:02 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:09 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:48:09 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:14 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:17 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:22 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:48:22 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:28 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:32 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:48:32 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:37 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:48:37 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:43 OpenWrt user.warn kernel: NET: 2 messages suppressed.
Jun 13 14:48:43 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:49 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:48:49 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:48:56 OpenWrt user.warn kernel: NET: 1 messages suppressed.
Jun 13 14:48:56 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:49:05 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:49:11 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:49:13 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:49:25 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:49:41 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:49:43 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:49:53 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:05 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:11 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:13 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:15 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:21 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:23 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:25 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:32 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:33 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:35 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:46 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 14:50:54 OpenWrt user.warn kernel: wl0: received packet with  own address as source address
Jun 13 15:12:03 OpenWrt authpriv.info dropbear[4921]: Child connection from 192.168.1.174:50789
Jun 13 15:12:08 OpenWrt authpriv.notice dropbear[4921]: password auth succeeded for 'root' from 192.168.1.174:50789
Jun 13 15:12:59 OpenWrt authpriv.info dropbear[4921]: exit after auth (root): Exited normally
Jun 13 15:13:53 OpenWrt authpriv.info dropbear[4938]: Child connection from 192.168.1.174:50823
Jun 13 15:13:58 OpenWrt authpriv.notice dropbear[4938]: password auth succeeded for 'root' from 192.168.1.174:50823

Obecnie zajmuje to całe miejsce w logread.
dmesg pokazuje podobne wpisy:

wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 2 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
NET: 1 messages suppressed.
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address
wl0: received packet with  own address as source address

Mimo tego sieć działa dobrze.
Do routera obecnie jest podłączony tylko jeden komputer po Wi-Fi. Przeważnie jest jeszcze kilka komputerów, smartfonów i TV po Wi-Fi, czasem coś po kablu. Często mam uruchomione irssi na screenie, czasem podłączam dysk pod USB i odpalę rTorrent. Ogólnie OpenWRT skonfigurowałem kilka lat temu i działa bez zarzutu (raz musiałem wymienić zasilacz, bo oryginalny padł). Wcześniej takie wpisy pojawiały się sporadycznie, ale teraz, gdy cały log jest nimi zawalony zacząłem się niepokoić.

Co może być przyczyną takich informacji w logach? Ktoś mi "aircrackuje" sieć?

Jeżeli to nic złego to jak wyfiltrować te wpisy? Często patrzę w logread, żeby wiedzieć co się dzieje w mojej sieci, OpenWRT używam tylko z konsoli, bez gui.

BTW. Jest sens aktualizować na tym sprzęcie aktualizować OpenWRT do 10.03, lub nowszego, jeżeli ten router jest jeszcze wspierany? Zostawiłem 8.09, bo te parę lat temu na tym kernelu najlepiej działało Wi-Fi, a potem już nie kombinowałem z nowszymi wersjami, zgodnie z zasadą "jeżeli działa to nie ruszać" ;-)

2015-04-28 16:56:50

Jak dla mnie wystarczy napisać odpowiednie pismo i powołać się na to, że ich oprogramowanie w routerach nie daje możliwości włączenia trybu bridge (wyjątkiem jest ten Ubee), co wyklucza zagwarantowane uzyskanie publicznego IP na pierwszym urządzeniu użytkownika, a oprócz tego jest dziurawe:
http://niebezpiecznik.pl/post/kolejna-p … on-twg870/
Można jeszcze coś tam wspomnieć o prywatności i bezpieczeństwie swojej wewnętrznej sieci i wtedy jak BOK dostanie takie pismo z jak największą ilością technicznych informacji to bez problemu powinien zezwolić na instalację modemu Cisco. Czasem mówią, że do niższych pakietów nie dają modemów Cisco, ale w regulaminie nie ma takiego zapisu (chociaż lepiej to wcześniej sprawdzić, bo mogą go do woli modyfikować).

Sprawdzone u kilku różnych osób podczas instalacji nowej usługi lub zmianie starej, takie pismo pomaga załatwić modem bez problemu. Tylko nie ma co się wdawać w dyskusje telefoniczne, lepiej wszystko załatwiać mailami, a jak sami zadzwonią to mówić, że wszystko jest w piśmie, które się wysłało. Kiedyś po instalacji u znajomego, babka do niego dzwoniła jeszcze kilka razy namawiając go jednak na wymianę na Technicolora, argumentując to złym działaniem jego modemu, podczas gdy sprzęt działał dobrze, bez problemów. Widocznie same modemy są dla nich bardzo cenne i za wszelką cenę wolą je mieć u siebie w magazynach, niż u klientów.

Co do tego sprzętu Ubee... teraz jest ta opcja bridge, ale co jak znowu ją nieodwracalnie wyłączą, jak w przypadku Thomsonów? Wtedy będzie lipa, więc dla pewności lepiej po prostu z góry załatwić sobie modem bez funkcji routera i nie mieć tego problemu.

2015-02-06 00:37:53

Faktycznie router zaczął działać normalnie na 5V/2A od starego D-Linka, ciekawe ile czasu wytrzyma i jak stabilny będzie.

2015-02-05 11:36:05

A ile może być najmniej tych amperów, tak żeby działał stabilnie 24/7? Do USB nic nie będzie podłączane. Jeden komp po Ethernecie i kilka po Wi-Fi.

2015-02-05 02:54:31

Cześć,

Mam problem z routerem ASUS WL-500g Premium. Działał sobie przez kilka lat bez zarzutu na OpenWRT 10.03 (kernel 2.4), nagle zaczął się wieszać i w końcu przestał reagować na cokolwiek i nie wstaje. Nie daje się wejść w failsafe. Po podłączeniu zasilania świecą się diody WAN, LAN 1,2,3,4 i AIR (nawet jak nic nie jest podłączone pod LAN, jak podłączam kompa to w ogóle nie widzi połączenia, Wi-Fi też nie działa.

Pierwsze co pomyślałem, że zasilacz wysiadł, ale obskoczyłem wszystkie sklepy elektroniczne w okolicy i nigdzie nie mają podobnego zasilacza (output: 5V, 2.5A), są tylko o mniejszym amperażu. Router już dawno po gwarancji. Jest jakaś możliwość sprawdzenia (np przez PoE?) bootloga, albo czegokolwiek co da mi jakieś info co wysiadło?

Pozdrawiam

2011-01-24 07:19:56

Ja tak kiedyś robiłem na PC, że postawiłem lokalny serwer proxy (squid) i po prostu odpowiednio skonfigurowałem soft, żeby korzystał z jednego łącza, albo z drugiego.
Więc pod OpenWRT też się pewnie da, kwestia skonfigurowania interfejsów sieciowych no i tego proxy.

2011-01-13 22:47:19

W configu Irssi jest jeszcze term_charset, pobaw się tym.

2011-01-10 21:05:58

Zobacz programem FileZilla.
Co do prędkości to zależy na czym te dane leżą, ale generalnie to dosyć wolno.

2010-11-23 03:41:06

Wystarczy napisać prosty skrypt powłoki (sh), który by sprawdzał po kolei usługi i porównywał je do wyników z ps i wszystko wypisywał na ekranie (i ewentualnie włączał/wyłączał daną usługę jeżeli jest taka potrzeba). Nie używam LuCI, ale domyślam się, że właśnie tak to jest tam zrobione, więc to nie problem przenieść sobie coś takiego do konsoli.

2010-11-15 05:59:17

Do Ventrilo nie ma źródeł, więc jest serwer pod Linuksa tylko pod x86, więc pod routery równierz polecam Mumble, chociaż zawsze możesz wykupić sobie jakiegoś taniego shella i na nim odpalić Ventrilo (lub bezpośrednio konto dedykowane pod Venta).

2010-11-09 04:35:52

Może rTorrent zamiast Transmission?

2010-11-02 05:58:40

Podłączę się do pytania o kartę Wi-Fi 802.11n na miniPCI i antenę kierunkową lub panelową (która lepsza?), która pozwoli na połączenie do innego routera, oddalonego o 200m (żadnych przeszkód po drodze). Koszty na razie nie grają roli, bo waśnie muszę się zorientować w cenach. No i nie wiem czy na taką odległość inwestować w 2.4GHz czy już lepiej 5GHz?

2010-09-12 11:14:14

Tak na szybko to przychodzi mi do głowy odpowiedni skrypt z regułkami iptables i wrzucasz go do crona, żeby się wykonywał wtedy kiedy chcesz.

Zanim zapytasz wpisz w Google hasła iptables, cron.

2010-09-09 04:27:57

Znajomy ma właśnie Tomato na tym modelu i wyciąga ~35 Mbps. Na oryginalnym firmware było 10 Mbps mniej.

2010-08-23 01:13:38

Wyłącz sprawdzanie haszy i zobacz jak będzie.

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

Opcje wyszukiwania (Strona 1 z 4)

Znalezione posty: 1 do 25 z 77

1 Odpowiedź przez KeFaS 2016-08-06 05:47:52

Odp: Dwie rzeczy nie mają granic: wszechświat i ludzka głupota... (3 odpowiedzi, napisanych Inne)

2 Odpowiedź przez KeFaS 2016-05-21 21:34:18

Odp: ath: phy0: Timeout while waiting for nf to load (2 odpowiedzi, napisanych Oprogramowanie / Software)

3 Odpowiedź przez KeFaS 2015-11-10 20:50:01

Odp: wyłączenie diod ? (4 odpowiedzi, napisanych Oprogramowanie / Software)

4 Odpowiedź przez KeFaS 2015-11-10 14:08:53

Odp: wyłączenie diod ? (4 odpowiedzi, napisanych Oprogramowanie / Software)

5 Temat przez KeFaS 2015-11-01 07:19:59

Temat: IPTraf (lub alternatywa) dla OpenWRT 15.05 (2 odpowiedzi, napisanych Oprogramowanie / Software)

6 Odpowiedź przez KeFaS 2015-06-14 09:17:29

Odp: Logi routera zawalone niepokojącymi wpisami (10 odpowiedzi, napisanych Oprogramowanie / Software)

7 Odpowiedź przez KeFaS 2015-06-13 23:13:59

Odp: Logi routera zawalone niepokojącymi wpisami (10 odpowiedzi, napisanych Oprogramowanie / Software)

8 Odpowiedź przez KeFaS 2015-06-13 18:05:01

Odp: Logi routera zawalone niepokojącymi wpisami (10 odpowiedzi, napisanych Oprogramowanie / Software)

9 Odpowiedź przez KeFaS 2015-06-13 16:41:28

Odp: Logi routera zawalone niepokojącymi wpisami (10 odpowiedzi, napisanych Oprogramowanie / Software)

10 Odpowiedź przez KeFaS 2015-06-13 14:44:55

Odp: Logi routera zawalone niepokojącymi wpisami (10 odpowiedzi, napisanych Oprogramowanie / Software)

11 Temat przez KeFaS 2015-06-13 14:27:21

Temat: Logi routera zawalone niepokojącymi wpisami (10 odpowiedzi, napisanych Oprogramowanie / Software)

12 Odpowiedź przez KeFaS 2015-04-28 16:56:50

Odp: UPC i OpenWRT (163 odpowiedzi, napisanych Oprogramowanie / Software)

13 Odpowiedź przez KeFaS 2015-02-06 00:37:53

Odp: Uszkodzony Asus WL-500gP (4 odpowiedzi, napisanych Oprogramowanie / Software)

14 Odpowiedź przez KeFaS 2015-02-05 11:36:05

Odp: Uszkodzony Asus WL-500gP (4 odpowiedzi, napisanych Oprogramowanie / Software)

15 Temat przez KeFaS 2015-02-05 02:54:31

Temat: Uszkodzony Asus WL-500gP (4 odpowiedzi, napisanych Oprogramowanie / Software)

16 Odpowiedź przez KeFaS 2011-01-24 07:19:56

Odp: Jak złączyć dwa porty WAN, balansowanie sieci (4 odpowiedzi, napisanych Oprogramowanie / Software)

17 Odpowiedź przez KeFaS 2011-01-13 22:47:19

Odp: Kodowanie IRSSI (13 odpowiedzi, napisanych Oprogramowanie / Software)

18 Odpowiedź przez KeFaS 2011-01-10 21:05:58

Odp: WinSCP - zatrzymanie transferu po 476 MB (26 odpowiedzi, napisanych Oprogramowanie / Software)

19 Odpowiedź przez KeFaS 2010-11-23 03:41:06

Odp: watchdog itp. glupie pytania :-) (11 odpowiedzi, napisanych Oprogramowanie / Software)

20 Odpowiedź przez KeFaS 2010-11-15 05:59:17

Odp: Serwer ventrillo? (6 odpowiedzi, napisanych Oprogramowanie / Software)

21 Odpowiedź przez KeFaS 2010-11-09 04:35:52

Odp: Problem TL-WR1043ND transmission restarty - chłodzenie Atheros? (25 odpowiedzi, napisanych Oprogramowanie / Software)

22 Odpowiedź przez KeFaS 2010-11-02 05:58:40

Odp: OpenWRT - jaki sprzęt jest najleszy (5 odpowiedzi, napisanych Oprogramowanie / Software)

23 Odpowiedź przez KeFaS 2010-09-12 11:14:14

Odp: WRT160nl - filtrowanie mac adres (26 odpowiedzi, napisanych Oprogramowanie / Software)

24 Odpowiedź przez KeFaS 2010-09-09 04:27:57

Odp: Jaki maksymalna szybkość WAN (bandwidth) dla WRT54GL z OpenWRT? (9 odpowiedzi, napisanych Oprogramowanie / Software)

25 Odpowiedź przez KeFaS 2010-08-23 01:13:38

Odp: Problem z rTorrent 0.8.6 r1165-1 na Backfire 10.03 (14 odpowiedzi, napisanych Oprogramowanie / Software)

Znalezione posty: 1 do 25 z 77