Tx qub on inactive peer - weiß jmd., was mir das sagen soll?

Forum zu den aktuellen LANCOM Wireless Accesspoint Serien

Moderator: Lancom-Systems Moderatoren

Antworten
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Tx qub on inactive peer - weiß jmd., was mir das sagen soll?

Beitrag von Jirka »

Hallo zusammen,

weiß jemand, was der AP mir mit diesem Bootlog sagen möchte?
(802.1X ist übrigens im AP nicht aktiv)

Code: Alles auswählen

08/20/2016 03:59:11  System boot after firmware upload

DEVICE:                LANCOM L-322agn dual Wireless
HW-RELEASE:            B
VERSION:               9.20.0683RU2 / 12.08.2016
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard

Vielen Dank und viele Grüße,
Jirka
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Re: Tx qub on inactive peer - weiß jmd., was mir das sagen s

Beitrag von Jirka »

Das Ganze habe ich inzwischen in verschiedenen Versionen, hier mal als Watchdog:

Code: Alles auswählen

08/28/2016 22:47:10  System boot after internal watchdog reset
 LR = 0x00000000            SP = 0x00000000

DEVICE:                LANCOM 1781VAW (over ISDN)
HW-RELEASE:            C
VERSION:               9.20.0683RU2 / 12.08.2016
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
CyberT
Beiträge: 260
Registriert: 17 Apr 2005, 14:36

Re: Watchdog WLAN-1-Driver ("Tx qub on inactive peer")

Beitrag von CyberT »

Hallo zusammen,
Jirka hat geschrieben:Das Ganze habe ich inzwischen in verschiedenen Versionen, hier mal als Watchdog:
Ja, das kann ich bestätigen! - Hier mal ein Auszug aus einem aktuellen Watchdog von einem L-460agn:

Code: Alles auswählen

DEVICE:                LANCOM L-460agn dual Wireless
HW-RELEASE:            B
VERSION:               9.20.0683RU2 / 12.08.2016
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> discard
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx
Tx qub on inactive peer
 -> EAPOL, Tx

****

09/01/2016 05:25:02  LCOS-Watchdog
Task name = WLAN-1-Driver  Type=directed frame without pLogDscr
[...]
Gruß.
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Re: Tx qub on inactive peer - weiß jmd., was mir das sagen s

Beitrag von Jirka »

Hi,

das Ganze wird anscheinend weiterentwickelt:

Code: Alles auswählen

08/30/2016 00:36:07  System boot after firmware upload

DEVICE:                LANCOM 1781VAW (over ISDN)
HW-RELEASE:            C
VERSION:               9.24.0066 / 26.08.2016
[08/30/2016 06:24:50] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[08/30/2016 08:28:18] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[08/31/2016 21:10:28] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/02/2016 18:59:44] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/02/2016 19:04:35] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/02/2016 23:26:48] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/03/2016 16:48:48] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 08:47:37] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 09:51:19] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 09:54:42] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 09:58:17] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 09:59:42] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 10:06:04] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 10:09:42] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 10:16:22] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 10:19:42] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 10:23:53] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 10:31:37] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 10:53:26] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/04/2016 11:13:54] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
Viele Grüße,
Jirka
Benutzeravatar
alf29
Moderator
Moderator
Beiträge: 6205
Registriert: 07 Nov 2004, 19:33
Wohnort: Aachen
Kontaktdaten:

Re: Tx qub on inactive peer - weiß jmd., was mir das sagen s

Beitrag von alf29 »

[08/30/2016 08:28:18] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
Kannst Du die Zeitstempel in diesen Meldungen mit irgendwelchen Ereignissen im WLAN-Log bzw Syslog korrelieren?

Gruß Alfred
“There is no death, there is just a change of our cosmic address."
-- Edgar Froese, 1944 - 2015
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Re: Tx qub on inactive peer - weiß jmd., was mir das sagen s

Beitrag von Jirka »

Hallo Alfred,

mal ein Versuch, das zu tun. Nehme etwas ältere und neuere Einträge mit rein, damit die Abgrenzung klar ist, also auf den Zeitstempel achten.

Hier das aktuelle Ende des Bootlogs:

Code: Alles auswählen

[09/04/2016 11:13:54] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/06/2016 18:12:10] WLAN-1: Tx qub on inactive peer 2c:8a:72:b7:ce:16:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/07/2016 18:47:56] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
[09/07/2016 18:59:55] WLAN-1: Tx qub on inactive peer bc:e6:3f:0a:cb:04:
  peer attached to WLAN-1
  peer is in our list
  client's state is 8, last event 0
 -> fixup
Hier dazu das WLAN-Log (Ausschnitt):

Code: Alles auswählen

Index Time                Interface Event                                                               Address      Reason                                        
======----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1079  09/08/2016 00:32:38 WLAN-1    Determined IPv4 address for station bc:e6:3f:0a:cb:04               bce63f0acb04 192.168.0.65                                  
1078  09/08/2016 00:32:37 WLAN-1    Determined IPv6 address for station bc:e6:3f:0a:cb:04               bce63f0acb04 fe80::bee6:3fff:fe0a:cb04                     
1077  09/08/2016 00:32:34 WLAN-1    Connected WLAN station bc:e6:3f:0a:cb:04                            bce63f0acb04                                               
1076  09/08/2016 00:32:34 WLAN-1    Key handshake with peer bc:e6:3f:0a:cb:04 successfully completed    bce63f0acb04                                               
1075  09/08/2016 00:32:34 WLAN-1    Associated WLAN station bc:e6:3f:0a:cb:04                           bce63f0acb04                                               
1074  09/08/2016 00:32:34 WLAN-1    Authenticated WLAN station bc:e6:3f:0a:cb:04                        bce63f0acb04                                               
1073  09/07/2016 19:24:49 WLAN-1    Disassociated WLAN station 2c:8a:72:b7:ce:16 due to idle timeout    2c8a72b7ce16                                               
1072  09/07/2016 18:59:52 WLAN-1    Determined IPv4 address for station bc:e6:3f:0a:cb:04               bce63f0acb04 192.168.0.65                                  
1071  09/07/2016 18:59:51 WLAN-1    Determined IPv6 address for station bc:e6:3f:0a:cb:04               bce63f0acb04 fe80::bee6:3fff:fe0a:cb04                     
1070  09/07/2016 18:59:50 WLAN-1    Connected WLAN station bc:e6:3f:0a:cb:04                            bce63f0acb04                                               
1069  09/07/2016 18:59:50 WLAN-1    Key handshake with peer bc:e6:3f:0a:cb:04 successfully completed    bce63f0acb04                                               
1068  09/07/2016 18:59:50 WLAN-1    Associated WLAN station bc:e6:3f:0a:cb:04                           bce63f0acb04                                               
1067  09/07/2016 18:59:50 WLAN-1    last message repeated 2 times                                       bce63f0acb04 first repetition at 09/07/2016 18:58:39       
1066  09/07/2016 18:58:34 WLAN-1    Authenticated WLAN station bc:e6:3f:0a:cb:04                        bce63f0acb04                                               
1065  09/07/2016 18:55:31 WLAN-1    Timeout in key handshake with peer bc:e6:3f:0a:cb:04                bce63f0acb04                                               
1064  09/07/2016 18:55:11 WLAN-1    Associated WLAN station bc:e6:3f:0a:cb:04                           bce63f0acb04                                               
1063  09/07/2016 18:55:11 WLAN-1    Authenticated WLAN station bc:e6:3f:0a:cb:04                        bce63f0acb04                                               
1062  09/07/2016 18:48:01 WLAN-1    Deauthenticated WLAN station bc:e6:3f:0a:cb:04                      bce63f0acb04 Deauthenticated because sending station is leaving (has left) IBSS or ESS
1061  09/07/2016 18:48:01 WLAN-1    Disassociated WLAN station bc:e6:3f:0a:cb:04 due to station request bce63f0acb04 Deauthenticated because sending station is leaving (has left) IBSS or ESS
1060  09/07/2016 18:47:51 WLAN-1    Associated WLAN station bc:e6:3f:0a:cb:04                           bce63f0acb04                                               
1059  09/07/2016 18:47:51 WLAN-1    Authenticated WLAN station bc:e6:3f:0a:cb:04                        bce63f0acb04                                               
1058  09/07/2016 18:47:31 WLAN-1    Timeout in key handshake with peer bc:e6:3f:0a:cb:04                bce63f0acb04                                               
1057  09/07/2016 18:47:11 WLAN-1    Associated WLAN station bc:e6:3f:0a:cb:04                           bce63f0acb04                                               
1056  09/07/2016 18:47:11 WLAN-1    Authenticated WLAN station bc:e6:3f:0a:cb:04                        bce63f0acb04                                               
1055  09/07/2016 18:27:56 WLAN-1    Determined IPv4 address for station bc:e6:3f:0a:cb:04               bce63f0acb04 192.168.0.65                                  
1054  09/07/2016 18:27:55 WLAN-1    Determined IPv6 address for station bc:e6:3f:0a:cb:04               bce63f0acb04 fe80::bee6:3fff:fe0a:cb04                     
1053  09/07/2016 18:27:55 WLAN-1    Connected WLAN station bc:e6:3f:0a:cb:04                            bce63f0acb04                                               
1052  09/07/2016 18:27:55 WLAN-1    Key handshake with peer bc:e6:3f:0a:cb:04 successfully completed    bce63f0acb04                                               
1051  09/07/2016 18:27:55 WLAN-1    Associated WLAN station bc:e6:3f:0a:cb:04                           bce63f0acb04                                               
1050  09/07/2016 18:27:55 WLAN-1    Authenticated WLAN station bc:e6:3f:0a:cb:04                        bce63f0acb04                                               
Vielen Dank und viele Grüße,
Jirka
Antworten