Polskie Forum Użytkowników Debiana

Polski portal użytkowników dystrybucji Debian GNU/Linux, dyskusje, artykuły, nowości, blog, porady, pomoc.
https://593930.wb34atkl.asia/

Punkt dost

https://593930.wb34atkl.asia/viewtopic.php?t=22828

Strona 1 z 1

Punkt dostępowy na karcie Atheros

: 26 kwietnia 2011, 18:40
autor: vascom
Witam.
Usiłuję skonfigurować sobie serwer, po problemach z ssh uparłem się na punkt dostępowy. W komputerze (serwer) są dwie karty sieciowe pierwsza:

Kod: Zaznacz cały

00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
ta karta jest połączona skrętką z liveboksem, oraz druga:

Kod: Zaznacz cały

00:0f.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)
ta karta ma robić za punkt dostępowy.

Całą konfiguracje przeprowadzałem zgodnie z opisem z tej strony:
http://blog.grzeszy.net/konfguracja-pro ... w-debianie
posiłkując się tym:
http://www.innozyt.pl/pldap/

Pierwszy restart serwera i dostałem kilka błędów, ogólnie to nie uruchomiło się nic. Po wydrapaniu z logów o co chodzi (drobne pomyłki moje jak i w opisie) kolejny restart i wszystko ładnie się uruchomiło.

Przestawiam konfiguracje laptopa by się połączył z nową siecią i zaczynają się schody.
Sytuacja wygląda tak że laptop łączy się z siecią ale mam brak internetu jak i dostępu do liveboksa. Ping wysłany do punktu dostępowego:

Kod: Zaznacz cały

┌─[vasco@vasco] - [~] - [wto kwi 26, 05:10]
└─[$]> ping 192.168.38.1
PING 192.168.38.1 (192.168.38.1) 56(84) bytes of data.
64 bytes from 192.168.38.1: icmp_req=1 ttl=64 time=1.99 ms
64 bytes from 192.168.38.1: icmp_req=4 ttl=64 time=1.98 ms
64 bytes from 192.168.38.1: icmp_req=5 ttl=64 time=25.8 ms
64 bytes from 192.168.38.1: icmp_req=9 ttl=64 time=26.8 ms
64 bytes from 192.168.38.1: icmp_req=10 ttl=64 time=1.97 ms
64 bytes from 192.168.38.1: icmp_req=13 ttl=64 time=96.4 ms
64 bytes from 192.168.38.1: icmp_req=14 ttl=64 time=1.97 ms
64 bytes from 192.168.38.1: icmp_req=17 ttl=64 time=208 ms
64 bytes from 192.168.38.1: icmp_req=18 ttl=64 time=421 ms
64 bytes from 192.168.38.1: icmp_req=19 ttl=64 time=1.96 ms
64 bytes from 192.168.38.1: icmp_req=23 ttl=64 time=1.95 ms
64 bytes from 192.168.38.1: icmp_req=28 ttl=64 time=1.98 ms

Kod: Zaznacz cały

ping wp.pl
ping: unknown host wp.pl
do liveboksa:

Kod: Zaznacz cały

 ping 192.168.1.1 
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.38.10 icmp_seq=2 Destination Host Unreachable
From 192.168.38.10 icmp_seq=3 Destination Host Unreachable
From 192.168.38.10 icmp_seq=4 Destination Host Unreachable
^C
Udało mi się za to połączyć z ssh ale wynik tego był taki, że po połączeniu nic nie mogłem wpisać.
Co mnie najbardziej zaciekawiło to to:

Kod: Zaznacz cały

 ifconfig 
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          UP 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:18 Base address:0x6c00 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:26069 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26069 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1461393 (1.3 Mb)  TX bytes:1461393 (1.3 Mb)

wlan0     Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          inet addr:192.168.38.10  Bcast:192.168.38.255  Mask:255.255.255.0
          inet6 addr: fe80::213:d4ff:fe59:ef63/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:432987 errors:0 dropped:6 overruns:0 frame:0
          TX packets:497101 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:71862798 (68.5 Mb)  TX bytes:275511923 (262.7 Mb)
Skąd on wytrzasnął tyle wysłanych i odebranych danych? Z samych pingów?

I jeszcze jedno z komputera klienta.

Kod: Zaznacz cały

┌─[vasco@vasco] - [~] - [wto kwi 26, 05:21]
└─[$]> iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"VHS"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: zz:zz:zz:zz:zz:zz   
          Bit Rate=1 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr :o ff   Fragment thr :o ff
          Power Management :o ff
          Link Quality=52/70  Signal level=-58 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:1   Missed beacon:0

┌─[vasco@vasco] - [~] - [wto kwi 26, 05:21]
└─[$]> iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bg  ESSID :o ff/any  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr :o ff   Fragment thr :o ff
          Power Management :o ff
          
┌─[vasco@vasco] - [~] - [wto kwi 26, 05:21]
└─[$]> iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bg  ESSID :o ff/any  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr :o ff   Fragment thr :o ff
          Power Management :o ff
          
┌─[vasco@vasco] - [~] - [wto kwi 26, 05:22]
└─[$]> iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"VHS"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: zz:zz:zz:zz:zz:zz   
          Bit Rate=1 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr :o ff   Fragment thr :o ff
          Power Management :o ff
          Link Quality=58/70  Signal level=-52 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:4   Missed beacon:0
To by było w sumie wszystko z komputera klient.
Ze strony serwera wygląda to tak.
Po wpisaniu:

Kod: Zaznacz cały

hostapd -dd /etc/hostapd/hostapd.conf >>test
dostaje stale takim oto błędem w konsoli

Kod: Zaznacz cały

ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
ioctl[IEEE80211_IOCTL_DELKEY]:No such file or directory
ioctl[IEEE80211_IOCTL_DELKEY]:No such file or directory
ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
 ioctl[IEEE80211_IOCTL_DELKEY]:No such file or directory
 ioctl[IEEE80211_IOCTL_DELKEY]:No such file or directory
ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
  ioctl[IEEE80211_IOCTL_DELKEY]:No such file or directory
  ioctl[IEEE80211_IOCTL_DELKEY]:No such file or directory
oraz plik
http://wklej.org/id/519346/ (nie wklejałem całego pliku bo ma ponad 7000 linii, a i tak się powtarza).
Sama karta Wifi też się dziwnie zachowuje bo obie kontrolki stale migają równocześnie a wydaje mi się, że jedna powinna być zapalona a druga migać.

Będę wdzięczny za pomoc.
Pozdrawiam.


Edycja:
Dodam kilka logów
Przefiltrowany kern.log

Kod: Zaznacz cały

vhs kernel: [    8.417467] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) 
vhs kernel: [    8.417592] 8139cp 0000:00:0e.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
vhs kernel: [    8.419003] 8139cp 0000:00:0e.0: Try the "8139too" driver instead. 
vhs kernel: [    8.579307] 8139too Fast Ethernet driver 0.9.28
vhs kernel: [    8.579499] PCI: setting IRQ 10 as level-triggered
vhs kernel: [    8.579520] PCI: Found IRQ 10 for device 0000:00:0e.0
vhs kernel: [    8.582686] eth0: RealTek RTL8139 at 0x6800, xx:xx:xx:xx:xx:xx, IRQ 10
vhs kernel: [    8.582707] eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
vhs kernel: [   25.493474] ath_hal: module license 'Proprietary' taints kernel.
vhs kernel: [   25.508884] AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417)
vhs kernel: [   26.159276] PCI: setting IRQ 9 as level-triggered
vhs kernel: [   26.159304] PCI: Found IRQ 9 for device 0000:00:0f.0
vhs kernel: [   26.742385] MadWifi: ath_attach: Switching rfkill capability off.
vhs kernel: [   28.714294] wifi0: Atheros AR2414 chip found (MAC 7.9, PHY 2112A 4.5, Radio 5.6)
vhs kernel: [   28.875083] ath_pci: wifi0: Atheros 5212: mem=0xe0400000, irq=9
vhs kernel: [   35.917581] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
vhs kernel: [   40.146595] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [   50.519778] NET: Registered protocol family 10
vhs kernel: [   50.523623] lo: Disabled Privacy Extensions
vhs kernel: [   55.237712] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [   56.671368] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [   60.614669] eth0: no IPv6 routers present
vhs kernel: [   65.634892] ath0: no IPv6 routers present
vhs kernel: [ 2250.275146] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 4847.473940] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 4849.010528] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 4853.393799] ath0: no IPv6 routers present
vhs kernel: [ 5015.399962] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 5016.298610] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 5025.163589] ath0: no IPv6 routers present
vhs kernel: [ 5095.271072] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 5104.824134] ath0: no IPv6 routers present
vhs kernel: [ 5441.992728] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 5562.178197] ath0: no IPv6 routers present 
vhs kernel: [ 5648.790870] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
vhs kernel: [ 5657.951654] ath0: no IPv6 routers present
koncówka z syslog ale ogolnie w całości tak wygląda prócz ostatniej linijki

Kod: Zaznacz cały

Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: pairwise  key handshake completed  (RSN)                                                           
Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  deauthenticated due to local deauth  request                                              
Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  associated                                                                                
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  associated                                                                                
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  associated                                                                                
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx;xx:xx:xx:xx WPA: pairwise  key handshake completed  (RSN)                                                           
Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:Xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  deauthenticated due to local deauth  request                                              
Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
Apr 26 17:36:48 vhs dhcpd: receive_packet failed on ath0: Network is down
debug

Kod: Zaznacz cały

Apr 26 17:04:45 vhs kernel: [ 5562.178197] ath0: no IPv6 routers  present                                                                                        
Apr 26 17:06:21 vhs kernel: [ 5657.951654] ath0: no IPv6 routers  present                                                                                        
Apr 26 17:11:12 vhs kernel: [ 5949.120244] ath0: no IPv6 routers  present                                                                                        
Apr 26 17:13:42 vhs kernel: [ 6098.444755] ath0: no IPv6 routers present
deamon.log

Kod: Zaznacz cały

Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:37 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:38 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
 Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
 Apr 26 17:25:39 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: pairwise  key handshake completed  (RSN)                                                           
 Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  deauthenticated due to local deauth  request                                              
 Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
 Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
 Apr 26 17:25:40 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  associated                                                                                
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  associated                                                                                
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  associated                                                                                
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:42 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:43 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key 2/4 Pairwise with unexpected replay  counter                                   
 Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
 Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx WPA: received  EAPOL-Key with invalid  MIC                                                              
 Apr 26 17:25:44 vhs hostapd: ath0: STA xx:xx;xx:xx:xx:xx WPA: pairwise  key handshake completed  (RSN)                                                           
 Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:Xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
 Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  deauthenticated due to local deauth  request                                              
 Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated                                                                             
 Apr 26 17:25:45 vhs hostapd: ath0: STA xx:xx:xx:xx:xx:xx IEEE 802.11:  disassociated
Oczywiście logi są z serwera. Jeśli chodzi o deamon.log i syslog to masa tego jest a co najgorsze nie mogę na to znaleźć odpowiedzi. Odnośnie tego wpisu:

Kod: Zaznacz cały

ath0: no IPv6 routers present
w debug to napisali aby się nie przejmować.

Edycja:
No i w sumie koniec zabawy. Połączenie działa widzę co jest między liveboksem a serwerem i tak samo mam dostęp za liveboksa, nie wiem czemu komputer miedzy serwerem a internetem mnie nie widzi ale to już zapewne kwestia iptables.

Nie mniej jakby ktoś kto to przeczytał i miał dobry adres z wytłumaczeniem iptables (najlepiej po polsku) to byłbym wdzięczny za podesłanie.

: 27 kwietnia 2011, 00:00
autor: fnmirk
vascom, nie zrozum tego opacznie. Zadając pytanie na forum należy dostarczyć tylko tyle informacji ile jest wymagane. Przy takiej ilości, nie wiem, czy komuś się będzie chciało to dokładnie przejrzeć.
Wystarczyłby schemat połączeń (najlepiej rysunek) i do tego informacja o sprzęcie. Dużo nie znaczy dobrze.

Znowu nie skorzystałeś z podstawowej zasady: zanim założysz temat przejrzyj forum.

http://debian.linux.pl/threads/5676-Prz ... -napiszesz!
O iptables jest bardzo dużo na forum i portalu.
Strefa czasowa UTC+01:00
Strona 1 z 1

Technologię dostarcza phpBB® Forum Software © phpBB Limited

Polski pakiet językowy dostarcza phpBB.pl