Menu
▾
▴
openpana-users — Information and support
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(9) |
Jul
(10) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(6) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: souhail s. <sou...@ya...> - 2015-09-30 09:52:27
|
Hello, I need to implement the The EAP-PSK Protocol with a Pre-Shared Key method, in ordrer to make just the authentification It seems that open papa is large project and englobes many points further such as wpa_supplicant, Radius.... Can you support me how to deploy just the authentification process based on EAP-PSK method Thanks in advance for you support |
|
From: Suyog B. <bs...@gm...> - 2014-12-19 09:03:45
|
Hello,
config.xml properly set with ssl certificates and interface is
loopback adapter but after all getting EAP authentiaction fail in openpac
EAP: EAP entering state RECEIVED
EAP: Received EAP-Failure
EAP: EAP entering state FAILURE
CTRL-EVENT-EAP-FAILURE EAP authentication failed
PANA: Finished txEAP function
.
PANA: Entering state: WAIT_EAP_RESULT_CLOSE (Session ID: 994452845).
PANA: There's an eapFail.
PANA: Trying a transition...
PANA: Session ID: 994452845, current state: WAIT_EAP_RESULT_CLOSE.
PANA: Tx PAN.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: insertAVPs function used without AVP.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: --C--- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X3B46256D |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X177BD09B |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 5555.
PANA: Sent 16 bytes to 127.0.0.1.
PANA: sessionTimerStop function.
PANA: sessionTimerStop finished.
PANA: disconnect function.
PANA: freeing key_id.
PANA: freeing msk_key.
PANA: freeing I_PAR.
PANA: freeing I_PAN.
PANA: freeing PAA_Nonce.
PANA: freeing PaC_Nonce.
PANA: Client disconnected.
Please give solution for it.
|
|
From: Suyog B. <bs...@gm...> - 2014-12-19 07:09:23
|
Hello,
I am getting following error, i properly setup certification files
in config.xml. But fail to get EAP.
Here Details of openpaa running.
suyog@suyog-ThinkPad-X60:$ bin/openpaa
EAP: Server state machine created
PANA: rtxTimerStop function.
PANA: There isn't any session associated.
PANA: thread '-184387840' as worker manager.
PANA: Starting thread '-184387840'.
hostapd_logger: Authentication server 127.0.0.1:1812
RADIUS local address: 127.0.0.1:45593
PANA: add_task: added task.
PANA: thread '-184387840' tries to get a task.
PANA: Trying to get a task..
EAP: Server state machine created
PANA: Session Id 1802306558 generated with port 53159 and ip 127.0.0.1.
PANA: Trying to delete session with id: 1802306558.
PANA: Update session with the following message:.
Pana Message Name: PCI
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength:
16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: ------ | MessageType:
1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PCI message.
PANA: Session updated with message:.
PANA: PCI.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: INITIAL.
PANA: generatePanaSa function.
PANA: Tx PAR.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: RS---- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Integrity-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:3 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 07
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: PRF-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:6 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 02
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 53159.
PANA: Sent 40 bytes to 127.0.0.1.
PANA: Entering state: INITIAL (Session ID: 1802306558).
PANA: Starting to check EAP status (check_eap_status).
PANA: Finished EAP check.
PANA: PANA message treatment finished.
PANA: add_task: added task.
PANA: thread '-184387840' tries to get a task.
PANA: Trying to get a task..
PANA: Session Id 1802306558 generated with port 53159 and ip 127.0.0.1.
PANA: add_session: added session: 0X6B6D03FE.
PANA: Session-Id added to the list is: 1802306558.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: -S---- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Integrity-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:3 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 07
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: PRF-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:6 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 02
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PANA-Auth message.
PANA: Hex2Dec: received:.
00 00 00 02
PANA: Hex2Dec: calculated 2.
PANA: Hex2Dec: received:.
00 00 00 07
PANA: Hex2Dec: calculated 7.
PANA: Session updated with message:.
PANA: PAN.
PANA: There isn't any Nonce AVP in the message.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: INITIAL.
PANA: eapRestart function.
EAP: EAP entering state INITIALIZE
CTRL-EVENT-EAP-STARTED 00:00:00:00:00:00
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: no identity known yet -> CONTINUE
EAP: EAP entering state PROPOSE_METHOD
EAP: getNextMethod: vendor 0 type 1
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1
EAP: EAP entering state METHOD_REQUEST
EAP: building EAP-Request: Identifier 189
EAP: EAP entering state SEND_REQUEST
EAP: EAP entering state IDLE
EAP: retransmit timeout 3 seconds (from dynamic back off; retransCount=0)
PANA: eapReStart: EAP has been properly restarted.
.
PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802306558).
PANA: Starting to check EAP status (check_eap_status).
PANA: There's an EAPRequest.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_EAP_MSG.
PANA: EAP_REQ found.
PANA: Tx PAR.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 60 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: R----- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 5 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Nonce
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:5 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 20 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: CA F3 8F 5C A2 E9 2D 14 BD 12 63 00 C7 3A 77 44 4E
D4 F2 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 53159.
PANA: Sent 60 bytes to 127.0.0.1.
PANA: rtxTimerStart function.
PANA: Entering state: WAIT_PAN_OR_PAR (Session ID: 1802306558).
PANA: Finished EAP check.
PANA: PANA message treatment finished.
PANA: add_task: added task.
PANA: thread '-184387840' tries to get a task.
PANA: Trying to get a task..
PANA: It's gonna search id: 1802306558.
PANA: Trying to get session of id: 1802306558.
PANA: Checking id: 1802306558.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 64 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: ------ | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 10 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Nonce
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:5 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 20 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: CA F3 8F 5C A2 E9 2D 14 BD 12 63 00 C7 3A 77 44 4E
D4 F2 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PANA-Auth message.
PANA: Session updated with message:.
PANA: PAN.
PANA: It's been detected a Nonce AVP.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_PAN_OR_PAR.
PANA: txEAP function.
EAP: EAP entering state RECEIVED
EAP: parseEapResp: rxResp=1 respId=189 respMethod=1 respVendor=0
respVendorMethod=0
EAP: EAP entering state INTEGRITY_CHECK
EAP: EAP entering state METHOD_RESPONSE
EAP-Identity: Peer identity - hexdump_ascii(len=5):
75 73 65 72 31 user1
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: -> PASSTHROUGH
EAP: EAP entering state INITIALIZE_PASSTHROUGH
EAP: EAP entering state AAA_REQUEST
EAP: EAP entering state AAA_IDLE
Encapsulating EAP message into a RADIUS packet
Learned identity from EAP-Response-Identity - hexdump(len=5): 75 73 65 72 31
hostapd_logger: Sending RADIUS message to authentication server
RADIUS message: code=1 (Access-Request) identifier=0 length=103
Attribute 1 (User-Name) length=7
Value: 'user1'
Attribute 4 (NAS-IP-Address) length=6
Value: 127.0.0.1
Attribute 31 (Calling-Station-Id) length=19
Value: '00-00-00-00-00-00'
Attribute 12 (Framed-MTU) length=6
Value: 1400
Attribute 61 (NAS-Port-Type) length=6
Value: 19
Attribute 77 (Connect-Info) length=9
Value: 'CONNECT'
Attribute 79 (EAP-Message) length=12
Value: 02 bd 00 0a 01 75 73 65 72 31
Attribute 80 (Message-Authenticator) length=18
Value: cc a6 9f 9d 38 f3 a0 ea a7 18 be 6d 34 66 df 0a
hostapd_logger: Next RADIUS client retransmit in 3 seconds
PANA: Finished txEAP function
.
PANA: rtxTimerStop function.
PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802306558).
PANA: Starting to check EAP status (check_eap_status).
PANA: Finished EAP check.
PANA: PANA message treatment finished.
PANA: add_task: added task.
PANA: thread '-184387840' tries to get a task.
PANA: Trying to get a task..
PANA: Getting an alarm session in radius function with id: 1802306558
.
PANA: Generating new session id with ip: 127.0.0.1 and port: 53159
.
hostapd_logger: Received RADIUS message
RADIUS message: code=11 (Access-Challenge) identifier=0 length=80
Attribute 79 (EAP-Message) length=24
Value: 01 be 00 16 04 10 4e a7 63 c4 f1 c9 ef 15 9d ac c3 a4 c8 97 3a
98
Attribute 80 (Message-Authenticator) length=18
Value: 04 6d 1f 6d 5b 45 9d 37 0f 8a 4f af 60 a6 ab d4
Attribute 24 (State) length=18
Value: 76 1a 02 7a 76 a4 06 e1 1e af 04 1f ae e3 3e 66
hostapd_logger: STA 00:00:00:00:00:00 - Received RADIUS packet matched with
a pending request, round trip time 0.05 sec
RADIUS packet matching with station
decapsulated EAP packet (code=1 id=190 len=22) from RADIUS server:
EAP-Request-MD5 (4)
EAP: EAP entering state AAA_RESPONSE
EAP: getId: id=190
EAP: EAP entering state SEND_REQUEST2
EAP: EAP entering state IDLE2
EAP: retransmit timeout 3 seconds (from dynamic back off; retransCount=0)
PANA: There's an eap request in RADIUS.
PANA: Trying to make a transition with the message from RADIUS.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_EAP_MSG.
PANA: EAP_REQ found.
PANA: Tx PAR.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: R----- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 22 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 53159.
PANA: Sent 48 bytes to 127.0.0.1.
PANA: rtxTimerStart function.
PANA: Entering state: WAIT_PAN_OR_PAR (Session ID: 1802306558).
PANA: add_task: added task.
PANA: thread '-184387840' tries to get a task.
PANA: Trying to get a task..
PANA: It's gonna search id: 1802306558.
PANA: Trying to get session of id: 1802306558.
PANA: Checking id: 1802306558.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: ------ | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 22 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PANA-Auth message.
PANA: Session updated with message:.
PANA: PAN.
PANA: There isn't any Nonce AVP in the message.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_PAN_OR_PAR.
PANA: txEAP function.
EAP: EAP entering state RECEIVED2
EAP: parseEapResp: rxResp=1 respId=190 respMethod=4 respVendor=0
respVendorMethod=0
EAP: EAP entering state AAA_REQUEST
EAP: EAP entering state AAA_IDLE
Encapsulating EAP message into a RADIUS packet
Copied RADIUS State Attribute
hostapd_logger: Sending RADIUS message to authentication server
RADIUS message: code=1 (Access-Request) identifier=1 length=133
Attribute 1 (User-Name) length=7
Value: 'user1'
Attribute 4 (NAS-IP-Address) length=6
Value: 127.0.0.1
Attribute 31 (Calling-Station-Id) length=19
Value: '00-00-00-00-00-00'
Attribute 12 (Framed-MTU) length=6
Value: 1400
Attribute 61 (NAS-Port-Type) length=6
Value: 19
Attribute 77 (Connect-Info) length=9
Value: 'CONNECT'
Attribute 79 (EAP-Message) length=24
Value: 02 be 00 16 04 10 ab 6f 4f 20 6a 24 b3 e8 4f 68 46 c9 bf 9e d5
44
Attribute 24 (State) length=18
Value: 76 1a 02 7a 76 a4 06 e1 1e af 04 1f ae e3 3e 66
Attribute 80 (Message-Authenticator) length=18
Value: 68 b7 35 e9 52 3e 6d 89 52 b8 7d a2 6f 76 4c ee
hostapd_logger: Next RADIUS client retransmit in 3 seconds
PANA: Finished txEAP function
.
PANA: rtxTimerStop function.
PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802306558).
PANA: Starting to check EAP status (check_eap_status).
PANA: Finished EAP check.
PANA: PANA message treatment finished.
PANA: add_task: added task.
PANA: thread '-184387840' tries to get a task.
PANA: Trying to get a task..
PANA: Getting an alarm session in radius function with id: 1802306558
.
PANA: Generating new session id with ip: 127.0.0.1 and port: 53159
.
hostapd_logger: Received RADIUS message
RADIUS message: code=3 (Access-Reject) identifier=1 length=44
Attribute 79 (EAP-Message) length=6
Value: 04 be 00 04
Attribute 80 (Message-Authenticator) length=18
Value: c5 40 44 41 e8 d8 6c b9 30 0b e0 6a c6 26 09 d8
hostapd_logger: STA 00:00:00:00:00:00 - Received RADIUS packet matched with
a pending request, round trip time 1.00 sec
RADIUS packet matching with station
decapsulated EAP packet (code=4 id=190 len=4) from RADIUS server: EAP
Failure
EAP: EAP entering state FAILURE2
PANA: There's an eap fail in RADIUS.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_EAP_MSG.
PANA: EAP_FAILURE = TRUE.
PANA: Tx PAR.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: R-C--- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Result-Code
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:7 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 01
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 53159.
PANA: Sent 40 bytes to 127.0.0.1.
PANA: rtxTimerStart function.
PANA: sessionTimerStop function.
PANA: Session with id 1802306558 not found in the alarm list.
PANA: sessionTimerStop finished.
PANA: Entering state: WAIT_FAIL_PAN (Session ID: 1802306558).
PANA: add_task: added task.
PANA: thread '-184387840' tries to get a task.
PANA: Trying to get a task..
PANA: It's gonna search id: 1802306558.
PANA: Trying to get session of id: 1802306558.
PANA: Checking id: 1802306558.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: --C--- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PANA-Auth message.
PANA: Session updated with message:.
PANA: PAN.
PANA: There isn't any Nonce AVP in the message.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_FAIL_PAN.
PANA: rtxTimerStop function.
PANA: disconnect function.
PANA: Entering state: CLOSED (Session ID: 1802306558).
PANA: Starting to check EAP status (check_eap_status).
PANA: Finished EAP check.
PANA: Trying to delete session with id: 1802306558.
PANA: Found and deleted session with id: 1802306558.
Here Details of openpac running.PANA: Loading client/ca.pem from config
directory.
PANA: Loading client/client.pem from config directory.
PANA: Loading client/client.pk8 from config directory.
PANA: rtxTimerStop function.
PANA: There isn't any session associated.
PANA: Trying a transition...
PANA: Session ID: 0, current state: INITIAL.
PANA: Sending PCI.
PANA: Tx PCI.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: insertAVPs function used without AVP.
PANA: Message to be sent.
Pana Message Name: PCI
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: ------ | MessageType: 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 5555.
PANA: Sent 16 bytes to 127.0.0.1.
PANA: rtxTimerStart function.
PANA: sessionTimerReStart function. Timeout: 150.
PANA: Session with id 0 not found in the alarm list.
PANA: Entering state: INITIAL (Session ID: 0).
PANA: I'm gonna start listening!.
PANA: My state is: INITIAL.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: RS---- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Integrity-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:3 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 07
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: PRF-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:6 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 02
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Client's session updated with Session Id from PAA: 1802306558.
PANA: Received PANA-Auth message.
PANA: Hex2Dec: received:.
00 00 00 02
PANA: Hex2Dec: calculated 2.
PANA: Hex2Dec: received:.
00 00 00 07
PANA: Hex2Dec: calculated 7.
PANA: Session updated with message:.
PANA: PAR.
PANA: There isn't any Nonce AVP in the message.
PANA: My state to begin a transition is: INITIAL.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: INITIAL.
PANA: eapRestart function.
PANA: eapReStart: EAP has been properly restarted.
.
PANA: sessionTimerReStart function. Timeout: 150.
PANA: generatePanaSa function.
PANA: Tx PAN.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: -S---- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Integrity-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:3 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 07
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: PRF-Algorithm
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:6 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 02
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 5555.
PANA: Sent 40 bytes to 127.0.0.1.
PANA: Entering state: WAIT_PAA (Session ID: 1802306558).
PANA: I'm gonna start listening!.
PANA: My state is: WAIT_PAA.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 60 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: R----- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 5 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Nonce
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:5 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 20 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: CA F3 8F 5C A2 E9 2D 14 BD 12 63 00 C7 3A 77 44 4E
D4 F2 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PANA-Auth message.
PANA: Session updated with message:.
PANA: PAR.
PANA: It's been detected a Nonce AVP.
PANA: My state to begin a transition is: WAIT_PAA.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_PAA.
PANA: eapPiggyback function.
PANA: eapPiggyback function.
PANA: rtxTimerStop function.
PANA: txEAP function.
EAP: EAP entering state IDLE
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=189 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=5):
75 73 65 72 31 user1
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
PANA: Finished txEAP function
.
PANA: eapRespTimerStart function.
PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802306558).
PANA: There's an EAPResponse.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_EAP_MSG.
PANA: eapPiggyback function.
PANA: eapRespTimerStop function.
PANA: Tx PAN.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 64 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: ------ | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 10 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Nonce
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:5 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 20 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: CA F3 8F 5C A2 E9 2D 14 BD 12 63 00 C7 3A 77 44 4E
D4 F2 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 5555.
PANA: Sent 64 bytes to 127.0.0.1.
PANA: Entering state: WAIT_PAA (Session ID: 1802306558).
PANA: I'm gonna start listening!.
PANA: My state is: WAIT_PAA.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: R----- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 22 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PANA-Auth message.
PANA: Session updated with message:.
PANA: PAR.
PANA: There isn't any Nonce AVP in the message.
PANA: My state to begin a transition is: WAIT_PAA.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_PAA.
PANA: eapPiggyback function.
PANA: eapPiggyback function.
PANA: rtxTimerStop function.
PANA: Session with id 1802306558 not found in the alarm list.
PANA: txEAP function.
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=190 method=4 vendor=0 vendorMethod=0
EAP: EAP entering state GET_METHOD
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=4
EAP: Initialize selected EAP method: vendor 0 method 4 (MD5)
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 4 (MD5) selected
EAP: EAP entering state METHOD
EAP-MD5: Generating Challenge Response
EAP: method process -> ignore=FALSE methodState=DONE decision=COND_SUCC
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
PANA: Finished txEAP function
.
PANA: eapRespTimerStart function.
PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802306558).
PANA: There's an EAPResponse.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_EAP_MSG.
PANA: eapPiggyback function.
PANA: eapRespTimerStop function.
PANA: Tx PAN.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: ------ | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 22 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 5555.
PANA: Sent 48 bytes to 127.0.0.1.
PANA: Entering state: WAIT_PAA (Session ID: 1802306558).
PANA: I'm gonna start listening!.
PANA: My state is: WAIT_PAA.
PANA: Update session with the following message:.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: R-C--- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: EAP-Payload
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:2 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: EAP-Payload omitted.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AVP Name: Result-Code
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code:7 | AVP Flags:0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Length: 4 | Reserved: 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value: 00 00 00 01
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Received PANA-Auth message.
PANA: Session updated with message:.
PANA: PAR.
PANA: There isn't any Nonce AVP in the message.
PANA: My state to begin a transition is: WAIT_PAA.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_PAA.
PANA: Hex2Dec: received:.
00 00 00 01
PANA: Hex2Dec: calculated 1.
PANA: txEAP function.
EAP: EAP entering state RECEIVED
EAP: Received EAP-Failure
EAP: EAP entering state FAILURE
CTRL-EVENT-EAP-FAILURE EAP authentication failed
PANA: Finished txEAP function
.
PANA: Entering state: WAIT_EAP_RESULT_CLOSE (Session ID: 1802306558).
PANA: There's an eapFail.
PANA: Trying a transition...
PANA: Session ID: 1802306558, current state: WAIT_EAP_RESULT_CLOSE.
PANA: Tx PAN.
PANA: KeyAvailable: AUTH KEY equals NULL.
PANA: insertAVPs function used without AVP.
PANA: Message to be sent.
Pana Message Name: PANA-Auth
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved:0 | MessageLength: 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags: --C--- | MessageType: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session Identifier: 0X6B6D03FE |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number: 0X142DE9A6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PANA: Sent to IP: 127.0.0.1 , port 5555.
PANA: Sent 16 bytes to 127.0.0.1.
PANA: sessionTimerStop function.
PANA: sessionTimerStop finished.
PANA: disconnect function.
PANA: freeing key_id.
PANA: freeing msk_key.
PANA: freeing I_PAR.
PANA: freeing I_PAN.
PANA: freeing PAA_Nonce.
PANA: freeing PaC_Nonce.
PANA: Client disconnected.
Can you please tell me what is the problem here
|
|
From: Francisco V. M. <f.v...@um...> - 2014-06-06 16:21:49
|
Hi Apurva, for relayed messages in multihop environments you only need a PRE between the unauthenticated node and the authenticated network. Suppose the following scenario where JN stands for Joining Node and AN stands for Authenticated Node: JN --- PRE(AN) --- AN ... AN ... PAA Here, the PRE will encapsulate the messages from JN and send them in the multihop environment given that it's an authenticated node. Is this your case? otherwise I don't see why you need multiple PREs. Regards, Paco 2014-06-06 14:46 GMT+02:00 Apurva Mhetre <apu...@pe...>: > Hi, > > I was setting up a scenario in cooja with PANATIKI,OPENPANA and > Free-radius 2.0.2 , in which I kept two PREs between Pac and PAA. > > In this scenario, PAA was showing following error: > > > > EAP: Server state machine created > > hostapd_logger: Authentication server 127.0.0.1:1812 > > RADIUS local address: 127.0.0.1:47172 > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > PANA: ERROR: Tried to send a message from an unauthenticated client. > > > > Does open pana support multiple PREs between PAA and Pac (i.e. > multi-hopped pana relayed messages ) > > And if not, is it possible to configure PAA to support the above scenario? > > I am attaching wireshark traces of the above scenario. > > > > > > Thanks > > Apurva > > > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If > you are not the intended recipient, you are not authorized to read, retain, > copy, print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for > virus infected mails. > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/NeoTech > _______________________________________________ > Openpana-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openpana-users > > |
|
From: Sapana K. <sap...@pe...> - 2014-06-05 08:44:23
|
Hi Pedro Finally I solved this problem. Issue was because of UIP buffer size defined in Contiki-config.h file. Default value is 240 bytes, we changed it 500 and now PaC-PRE is working fine. Thanks for your support. Sapana From: Sapana Khemkar Sent: Thursday, June 05, 2014 11:50 AM To: 'Pedro Moreno-Sanchez' Cc: ope...@li... Subject: RE: [Openpana-users] PAC via PRE in PANATIKI not working Hi Pedro Thanks for your reply. Please find attached wireshark messages and log messages of nodes. (ID1 is Boarder router, ID2 is PRE and ID3 is PaC ) From these logs, PRE is not receiving EAP message(148 Request, Identity) Appreciate your help to resolve this issue. Thanks Sapana From: ped...@gm... [mailto:ped...@gm...] On Behalf Of Pedro Moreno-Sanchez Sent: Wednesday, June 04, 2014 1:10 PM To: Sapana Khemkar Cc: ope...@li... Subject: Re: [Openpana-users] PAC via PRE in PANATIKI not working Hello Sapana, I will answer you inline. On 3 June 2014 13:12, Sapana Khemkar <sap...@pe...<mailto:sap...@pe...>> wrote: Hi I was trying to play with PaC and PRE on PANATIKI and PAA on OpenPANA. I have followed user manual provided by you. PaC only scenario is working properly. Now I am trying PaC-PRE scenario. But it is not working. I get below messages on PAA server PANA: Received PCI message. PANA: Entering state: INITIAL (Session ID: -1842277294). PANA: Received PANA-Auth message. EAP: EAP entering state INITIALIZE CTRL-EVENT-EAP-STARTED 00:00:00:00:00:00 EAP: EAP entering state SELECT_ACTION EAP: getDecision: no identity known yet -> CONTINUE EAP: EAP entering state PROPOSE_METHOD EAP: getNextMethod: vendor 0 type 1 CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 EAP: EAP entering state METHOD_REQUEST EAP: building EAP-Request: Identifier 224 EAP: EAP entering state SEND_REQUEST EAP: EAP entering state IDLE EAP: retransmit timeout 3 seconds (from dynamic back off; retransCount=0) PANA: Entering state: WAIT_EAP_MSG (Session ID: -1842277294). PANA: Entering state: WAIT_PAN_OR_PAR (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: CLOSED (Session ID: -1842277294). Any idea why PAC via PRE is not working? With this information is hard for us to figure out which the problem could be. More debug information (e.g., Wireshark traces, config file, etc.) would be useful. In principle it seems that the PAA has sent PANA message including EAP payload but the PaC is not answering correctly. Thereby, the PAA get stuck in the WAIT_PAN_OR_PAR state. I have one more query on this PaC-PRE scenario. PaC sends authentication request via PRE. As per my understanding, node first authenticate itself with PAA then it can work as PRE. But in PANATIKI demo PRE node do not do self-authentication and just works as relay. Any comments on this? You are right. In PANATIKI demo we have implemented a basic scenario in which the PRE does not authenticate itself and just works as relay. However, this functionality is available if you use OpenPANA for all the entities (e.g., PaC, PRE and PAA). In this case, you might compile the OpenPANA software with the option --enable-relay in the configure command. Then, once the PaC is correctly authenticated it becomes PRE. Thanks Sapana Best, Pedro. DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ Openpana-users mailing list Ope...@li...<mailto:Ope...@li...> https://lists.sourceforge.net/lists/listinfo/openpana-users DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. |
|
From: Sapana K. <sap...@pe...> - 2014-06-05 06:20:08
|
1051 ID:2 Rime started with address 193.12.0.0.0.0.0.2 1064 ID:2 MAC c1:0c:00:00:00:00:00:02 Contiki 2.6 started. Node id is set to 2. 1074 ID:2 CSMA ContikiMAC, channel check rate 8 Hz, radio channel 26 1090 ID:2 Tentative link-local IPv6 address fe80:0000:0000:0000:c30c:0000:0000:0002 1094 ID:2 Starting 'UDP server process' 1096 ID:2 UDP server started 1104 ID:2 Server IPv6 addresses: aaaa::c30c:0:0:2 1109 ID:2 fe80::c30c:0:0:2 1201 ID:1 Rime started with address 193.12.0.0.0.0.0.1 1215 ID:1 MAC c1:0c:00:00:00:00:00:01 Contiki 2.6 started. Node id is set to 1. 1225 ID:1 CSMA ContikiMAC, channel check rate 8 Hz, radio channel 26 1242 ID:1 Tentative link-local IPv6 address fe80:0000:0000:0000:c30c:0000:0000:0001 1248 ID:1 Starting 'Border router process' 'Web server' 1255 ID:1 ?PGot configuration message of type P 1259 ID:1 Setting prefix aaaa:: 1715 ID:3 Rime started with address 193.12.0.0.0.0.0.3 1728 ID:3 MAC c1:0c:00:00:00:00:00:03 Contiki 2.6 started. Node id is set to 3. 1737 ID:3 CSMA ContikiMAC, channel check rate 8 Hz, radio channel 26 1754 ID:3 Tentative link-local IPv6 address fe80:0000:0000:0000:c30c:0000:0000:0003 1757 ID:3 Starting 'UDP client process' 1760 ID:3 UDP client process started 1768 ID:3 Client IPv6 addresses: aaaa::c30c:0:0:3 1773 ID:3 fe80::c30c:0:0:3 1788 ID:3 Created a connection with the server fe80::c30c:0:0:2 local/remote port 3001/3000 2249 ID:1 Server IPv6 addresses: 2254 ID:1 aaaa::c30c:0:0:1 2259 ID:1 fe80::c30c:0:0:1 36788 ID:3 Initiating (Re-)Authentication 36824 ID:2 Server received 16 bytes from PaC 36828 ID:2 PRE generated relayed message 36832 ID:2 message sent to PAA 36948 ID:1 FALLBACK: removing ext hdrs & setting proto 8 17 36956 ID:1 `L?"=.L4WD 37084 ID:2 Server received 92 bytes from PAA 37088 ID:2 message sent to PaC 37113 ID:3 Message 1 received 37129 ID:3 Sending response message 1 37203 ID:2 Server received 40 bytes from PaC 37206 ID:2 PRE generated relayed message 37213 ID:2 message sent to PAA 37318 ID:1 FALLBACK: removing ext hdrs & setting proto 0 34 37326 ID:1 `d?"=.dT\ 842183 ID:2 tcpip_ipv6_output: nbr cache entry stale moving to delay 846483 ID:1 ((@1RVtcpip_ipv6_output: nbr cache entry stale moving to delay 959480 ID:3 tcpip_ipv6_output: nbr cache entry stale moving to delay 964206 ID:2 tcpip_ipv6_output: nbr cache entry stale moving to delay |
|
From: Pedro Moreno-S. <s9p...@st...> - 2014-06-04 07:40:47
|
Hello Sapana, I will answer you inline. On 3 June 2014 13:12, Sapana Khemkar <sap...@pe...> wrote: > Hi > > > > I was trying to play with PaC and PRE on PANATIKI and PAA on OpenPANA. > > I have followed user manual provided by you. > > > > PaC only scenario is working properly. > > > > Now I am trying PaC-PRE scenario. But it is not working. I get below > messages on PAA server > > > > PANA: Received PCI message. > > PANA: Entering state: INITIAL (Session ID: -1842277294). > > PANA: Received PANA-Auth message. > > EAP: EAP entering state INITIALIZE > > CTRL-EVENT-EAP-STARTED 00:00:00:00:00:00 > > EAP: EAP entering state SELECT_ACTION > > EAP: getDecision: no identity known yet -> CONTINUE > > EAP: EAP entering state PROPOSE_METHOD > > EAP: getNextMethod: vendor 0 type 1 > > CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 > > EAP: EAP entering state METHOD_REQUEST > > EAP: building EAP-Request: Identifier 224 > > EAP: EAP entering state SEND_REQUEST > > EAP: EAP entering state IDLE > > EAP: retransmit timeout 3 seconds (from dynamic back off; retransCount=0) > > PANA: Entering state: WAIT_EAP_MSG (Session ID: -1842277294). > > PANA: Entering state: WAIT_PAN_OR_PAR (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: NO CHANGE (Session ID: -1842277294). > > PANA: Entering state: CLOSED (Session ID: -1842277294). > > > > Any idea why PAC via PRE is not working? > With this information is hard for us to figure out which the problem could be. More debug information (e.g., Wireshark traces, config file, etc.) would be useful. In principle it seems that the PAA has sent PANA message including EAP payload but the PaC is not answering correctly. Thereby, the PAA get stuck in the WAIT_PAN_OR_PAR state. > > > I have one more query on this PaC-PRE scenario. PaC sends authentication > request via PRE. > > As per my understanding, node first authenticate itself with PAA then it > can work as PRE. But in PANATIKI demo PRE node do not do > self-authentication and just works as relay. Any comments on this? > You are right. In PANATIKI demo we have implemented a basic scenario in which the PRE does not authenticate itself and just works as relay. However, this functionality is available if you use OpenPANA for all the entities (e.g., PaC, PRE and PAA). In this case, you might compile the OpenPANA software with the option --enable-relay in the configure command. Then, once the PaC is correctly authenticated it becomes PRE. > > > Thanks > > Sapana > Best, Pedro. > > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If > you are not the intended recipient, you are not authorized to read, retain, > copy, print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for > virus infected mails. > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/NeoTech > _______________________________________________ > Openpana-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openpana-users > > |
|
From: Sapana K. <sap...@pe...> - 2014-06-03 11:12:26
|
Hi I was trying to play with PaC and PRE on PANATIKI and PAA on OpenPANA. I have followed user manual provided by you. PaC only scenario is working properly. Now I am trying PaC-PRE scenario. But it is not working. I get below messages on PAA server PANA: Received PCI message. PANA: Entering state: INITIAL (Session ID: -1842277294). PANA: Received PANA-Auth message. EAP: EAP entering state INITIALIZE CTRL-EVENT-EAP-STARTED 00:00:00:00:00:00 EAP: EAP entering state SELECT_ACTION EAP: getDecision: no identity known yet -> CONTINUE EAP: EAP entering state PROPOSE_METHOD EAP: getNextMethod: vendor 0 type 1 CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 EAP: EAP entering state METHOD_REQUEST EAP: building EAP-Request: Identifier 224 EAP: EAP entering state SEND_REQUEST EAP: EAP entering state IDLE EAP: retransmit timeout 3 seconds (from dynamic back off; retransCount=0) PANA: Entering state: WAIT_EAP_MSG (Session ID: -1842277294). PANA: Entering state: WAIT_PAN_OR_PAR (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: NO CHANGE (Session ID: -1842277294). PANA: Entering state: CLOSED (Session ID: -1842277294). Any idea why PAC via PRE is not working? I have one more query on this PaC-PRE scenario. PaC sends authentication request via PRE. As per my understanding, node first authenticate itself with PAA then it can work as PRE. But in PANATIKI demo PRE node do not do self-authentication and just works as relay. Any comments on this? Thanks Sapana DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. |
|
From: Bourgeois g. <gil...@gm...> - 2014-02-18 06:33:15
|
Hello,
I am willing to re-play with the panatiki / openPANA implementation you
propose.
I follow user manual instruction, including users, default and eap.conf
files copy from openPana to FreeRadius directory.
Then, PANA/EAP exchange starts well, and I get radius reject because of no
AUTH-TYPE found :
Any idea about this reject (which surely comes from any misconfiguration
or something on my side, but I can't figure out..)
Thanks
**********************
rad_recv: Access-Request packet from host 127.0.0.1 port 47462, id=0,
length=103
User-Name = "usera"
NAS-IP-Address = 127.0.0.1
Calling-Station-Id = "00-00-00-00-00-00"
Framed-MTU = 1400
NAS-Port-Type = Wireless-802.11
Connect-Info = "CONNECT"
EAP-Message = 0x0249000a017573657261
Message-Authenticator = 0xf338498fefb32b0cb5f94bc46f13
fa09
# Executing section authorize from file
/home/gilles/freeradius-server-2.2.3/etc/raddb/sites-enabled/default
+group authorize {
++[preprocess] = ok
++[chap] = noop
++[mschap] = noop
[suffix] No '@' in User-Name = "usera", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] = noop
++[unix] = notfound
++[files] = noop
++[expiration] = noop
++[logintime] = noop
+} # group authorize = ok
*ERROR: No authenticate method (Auth-Type) found for the request: Rejecting
the user*
Failed to authenticate the user.
|
|
From: anmolmeet s. m. <anm...@ym...> - 2013-07-11 19:47:42
|
hello I am trying to do the experimental EAP-PSK for mutual authentication with openpana . i am installing freeradius with rlm_eap2 . after running radiusd -X i get this erroR failed to link with module rlm_eap2 file not found . i think i do mistake in this step Edit file freeradius/src/modules/rlm eap2/Makefile. Within the Makefile, the following variables must be set: – HOSTAP = path-to-hostapd-library – TARGET = rlm eap2 PLEASE CAN ANYONE CAN EXPLAIN THIS STEP IN BRIEFLY . i had already my hostap with libeap . i dont know how to edit make file . as i am using like this makefile=--HOSTAP=/home/hostap/hostapd --TARGET=rlm_eap2 thankyou On 3 Jul 2013, at 21:37, Pedro Moreno Sánchez wrote: > great! Could you explain what was the problem and how you fixed it? It would be very useful for other OpenPANA users and for us in order to fix it in the next release. > > Thank you in advance, > Pedro > > > On 3 July 2013 19:18, anmolmeet singh malhi <anm...@ym...> wrote: > hello > i finish with my openpana implementation and solve the malloc() error using valgrind . > On 1 Jul 2013, at 19:14, Pedro Moreno Sánchez wrote: > > > Hi Anmol, > > > > In principle there should not be any problem in setting up two virtual machines as authenticator and server respectively as long as the setting is correctly performed. Could you send us the following information? > > * the same config.xml you are using when you get the error > > * the networking information (i.e. ifconfig command's output in every machine) > > * The debug error message > > > > I would encourage you to follow Francisco's suggestion in order to study the problem by yourself while we find some time to fix it: "I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial." > > > > Regards, > > Pedro Moreno Sanchez. > > > > > > > -- > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > ---------------------------------------------------------------------------- > > > > > |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-07-04 08:11:46
|
Yes sure actually it was problem in loadconfig.c session.c and two more programs. when i try to run ./openpaa from authenticator it give me glibc detected malloc() error which is the memory leakage problem due to virtual ubuntu . so i use VALGRIND application in linux These Valgrind tools can automatically detect many memory management and threading bugs, and profile the programs in detail. www.valgrind.org . this valgrind tool shows me 11 bugs which is memeory error in c programs but this tool make my program run proper . and now i am trying to fix malloc error one by one . On 3 Jul 2013, at 21:37, Pedro Moreno Sánchez wrote: > great! Could you explain what was the problem and how you fixed it? It would be very useful for other OpenPANA users and for us in order to fix it in the next release. > > Thank you in advance, > Pedro > > > On 3 July 2013 19:18, anmolmeet singh malhi <anm...@ym...> wrote: > hello > i finish with my openpana implementation and solve the malloc() error using valgrind . > On 1 Jul 2013, at 19:14, Pedro Moreno Sánchez wrote: > > > Hi Anmol, > > > > In principle there should not be any problem in setting up two virtual machines as authenticator and server respectively as long as the setting is correctly performed. Could you send us the following information? > > * the same config.xml you are using when you get the error > > * the networking information (i.e. ifconfig command's output in every machine) > > * The debug error message > > > > I would encourage you to follow Francisco's suggestion in order to study the problem by yourself while we find some time to fix it: "I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial." > > > > Regards, > > Pedro Moreno Sanchez. > > > > > > > -- > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > ---------------------------------------------------------------------------- > > > > > |
|
From: Pedro M. S. <p.m...@um...> - 2013-07-03 20:37:53
|
great! Could you explain what was the problem and how you fixed it? It would be very useful for other OpenPANA users and for us in order to fix it in the next release. Thank you in advance, Pedro On 3 July 2013 19:18, anmolmeet singh malhi <anm...@ym...> wrote: > hello > i finish with my openpana implementation and solve the malloc() error > using valgrind . > On 1 Jul 2013, at 19:14, Pedro Moreno Sánchez wrote: > > > Hi Anmol, > > > > In principle there should not be any problem in setting up two virtual > machines as authenticator and server respectively as long as the setting is > correctly performed. Could you send us the following information? > > * the same config.xml you are using when you get the error > > * the networking information (i.e. ifconfig command's output in every > machine) > > * The debug error message > > > > I would encourage you to follow Francisco's suggestion in order to study > the problem by yourself while we find some time to fix it: "I suggest you > to track down the error in an iterative way. OpenPANA has proven to work > well between virtual machines if configures appropiately. Once you get the > PaC working in a VirtualMachine, adding another client from any other > device which can communicate is trivial." > > > > Regards, > > Pedro Moreno Sanchez. > > > > -- ---------------------------------------------------------------------------- Pedro Moreno Sánchez - MSc Computer Engineer Networks and Telematics Faculty of Computer Science - University of Murcia 30100 - Murcia - Spain email: p.m...@um... ---------------------------------------------------------------------------- |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-07-03 17:18:56
|
hello i finish with my openpana implementation and solve the malloc() error using valgrind . On 1 Jul 2013, at 19:14, Pedro Moreno Sánchez wrote: > Hi Anmol, > > In principle there should not be any problem in setting up two virtual machines as authenticator and server respectively as long as the setting is correctly performed. Could you send us the following information? > * the same config.xml you are using when you get the error > * the networking information (i.e. ifconfig command's output in every machine) > * The debug error message > > I would encourage you to follow Francisco's suggestion in order to study the problem by yourself while we find some time to fix it: "I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial." > > Regards, > Pedro Moreno Sanchez. > |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-07-01 19:21:38
|
thats my error in this case ip address of radius server is 192.168.0.21 PANA: warning: Loading config.xml from current directory. EAP: Server state machine created PANA: DEBUG: rtxTimerStop function. PANA: DEBUG: There isn't any session associated. hostapd_logger: Authentication server 192.168.0.21:1812 RADIUS local address: 192.168.0.9:48634 PANA: DEBUG: thread '0' as worker manager. PANA: DEBUG: Starting thread '0'. PANA: DEBUG: add_task: added task. PANA: DEBUG: thread '0' tries to get a task. PANA: DEBUG: Trying to get a task.. PANA: warning: Loading config.xml from current directory. *** glibc detected *** ./openpaa: malloc(): memory corruption: 0x093edb28 *** ======= Backtrace: ========= /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2] /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e] /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498] /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c] /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743 ] /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f] /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee] ./openpaa[0x8054a36] ./openpaa[0x8054c38] ./openpaa[0x8054c38] ./openpaa[0x8054c38] ./openpaa[0x8055327] ./openpaa[0x8049a60] ./openpaa[0x8052437]./openpaa[0x8052f50] /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31] /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce] ======= Memory map: ======== 00110000-00257000 r-xp 00000000 08:01 297593 /usr/lib/libxml2.so.2.7.8 00257000-0025b000 r--p 00147000 08:01 297593 /usr/lib/libxml2.so.2.7.8 0025b000-0025c000 rw-p 0014b000 08:01 297593 /usr/lib/libxml2.so.2.7.8 0025c000-0025d000 rw-p 00000000 00:00 0 0025d000-00270000 r-xp 00000000 08:01 134695 linux-gnu/libz.so.1.2.3.4 00270000-00271000 r--p 00012000 08:01 134695 linux-gnu/libz.so.1.2.3.4 00271000-00272000 rw-p 00013000 08:01 134695 linux-gnu/libz.so.1.2.3.4 002b9000-002e1000 r-xp 00000000 08:01 134642 linux-gnu/libm-2.13.so 002e1000-002e2000 r--p 00028000 08:01 134642 linux-gnu/libm-2.13.so 002e2000-002e3000 rw-p 00029000 08:01 134642 linux-gnu/libm-2.13.so 00304000-00322000 r-xp 00000000 08:01 134599 linux-gnu/ld-2.13.so 00322000-00323000 r--p 0001d000 08:01 134599 linux-gnu/ld-2.13.so 00323000-00324000 rw-p 0001e000 08:01 134599 linux-gnu/ld-2.13.so 0035a000-004e7000 r-xp 00000000 08:01 139154 linux-gnu/libcrypto.so.1.0.0 004e7000-004f5000 r--p 0018d000 08:01 139154 linux-gnu/libcrypto.so.1.0.0 004f5000-004fb000 rw-p 0019b000 08:01 139154 linux-gnu/libcrypto.so.1.0.0 004fb000-004fe000 rw-p 00000000 00:00 0 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- linux-gnu/libpthread-2.13.so 00618000-00619000 r--p 00016000 08:01 134672 linux-gnu/libpthread-2.13.so 00619000-0061a000 rw-p 00017000 08:01 134672 linux-gnu/libpthread-2.13.so 0061a000-0061c000 rw-p 00000000 00:00 0 0061c000-00792000 r-xp 00000000 08:01 134612 linux-gnu/libc-2.13.so 00792000-00794000 r--p 00176000 08:01 134612 linux-gnu/libc-2.13.so 00794000-00795000 rw-p 00178000 08:01 134612 linux-gnu/libc-2.13.so 00795000-00798000 rw-p 00000000 00:00 0 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso] 007bf000-007c2000 r-xp 00000000 08:01 134623 linux-gnu/libdl-2.13.so 007c2000-007c3000 r--p 00002000 08:01 134623 linux-gnu/libdl-2.13.so 007c3000-007c4000 rw-p 00003000 08:01 134623 linux-gnu/libdl-2.13.so 00e49000-00e65000 r-xp 00000000 08:01 134633 linux-gnu/libgcc_s.so.1 00e65000-00e66000 r--p 0001b000 08:01 134633 linux-gnu/libgcc_s.so.1 00e66000-00e67000 rw-p 0001c000 08:01 134633 linux-gnu/libgcc_s.so.1 /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- /lib/i386- 08048000-0809f000 r-xp 00000000 08:01 39668 /home/anmolm/trunk/src/openpaa 0809f000-080a0000 r--p 00056000 08:01 39668 /home/anmolm/trunk/src/openpaa 080a0000-080a1000 rw-p 00057000 08:01 39668 /home/anmolm/trunk/src/openpaa 093de000-093ff000 rw-p 00000000 00:00 0 b6600000-b6621000 rw-p 00000000 00:00 0 b6621000-b6700000 ---p 00000000 00:00 0 b67ed000-b67ee000 ---p 00000000 00:00 0 b67ee000-b6fee000 rw-p 00000000 00:00 0 [heap] b6fee000-b6fef000 ---p 00000000 00:00 0 b6fef000-b77f2000 rw-p 00000000 00:00 0 b7802000-b7805000 rw-p 00000000 00:00 0 bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack] On 1 Jul 2013, at 19:14, Pedro Moreno Sánchez wrote: > Hi Anmol, > > In principle there should not be any problem in setting up two virtual machines as authenticator and server respectively as long as the setting is correctly performed. Could you send us the following information? > * the same config.xml you are using when you get the error > * the networking information (i.e. ifconfig command's output in every machine) > * The debug error message > > I would encourage you to follow Francisco's suggestion in order to study the problem by yourself while we find some time to fix it: "I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial." > > Regards, > Pedro Moreno Sanchez. > |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-07-01 19:03:33
|
1. CONFIGURATION FILE
My configuration file i attached which i use same in my pac raspberry pi .
2. IFCONFIG
a. My client raspberry pi (PAC)
eth0 Link encap:Ethernet HWaddr b8:27:eb:fd:55:ec
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:66480 errors:0 dropped:0 overruns:0 frame:0
TX packets:22856 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50788810 (48.4 MiB) TX bytes:8475499 (8.0 MiB)
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
b. Authenticator (PAA) (vb UBUNTU 1)
eth0 Link encap:Ethernet HWaddr 08:00:27:5e:a4:3f
inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe5e:a43f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2541 errors:0 dropped:0 overruns:0 frame:0
TX packets:837 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:293803 (293.8 KB) TX bytes:125313 (125.3 KB)
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:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2119 (2.1 KB) TX bytes:2119 (2.1 KB)
c. Radius server (as my server ) (vb UBUNTU 2)
eth0 Link encap:Ethernet HWaddr 08:00:27:of:eb:80
inet addr:192.168.0.21 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe5e:a43f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:293803 (293.8 KB) TX bytes:125313 (125.3 KB)
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:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2119 (2.1 KB) TX bytes:2119 (2.1 KB)
On 1 Jul 2013, at 19:14, Pedro Moreno Sánchez wrote:
> Hi Anmol,
>
> In principle there should not be any problem in setting up two virtual machines as authenticator and server respectively as long as the setting is correctly performed. Could you send us the following information?
> * the same config.xml you are using when you get the error
> * the networking information (i.e. ifconfig command's output in every machine)
> * The debug error message
>
> I would encourage you to follow Francisco's suggestion in order to study the problem by yourself while we find some time to fix it: "I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial."
>
> Regards,
> Pedro Moreno Sanchez.
>
|
|
From: Pedro M. S. <p.m...@um...> - 2013-07-01 18:14:40
|
Hi Anmol, In principle there should not be any problem in setting up two virtual machines as authenticator and server respectively as long as the setting is correctly performed. Could you send us the following information? * the same config.xml you are using when you get the error * the networking information (i.e. ifconfig command's output in every machine) * The debug error message I would encourage you to follow Francisco's suggestion in order to study the problem by yourself while we find some time to fix it: "I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial." Regards, Pedro Moreno Sanchez. |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-07-01 18:02:53
|
I agree with you but in my case using raspberry pi is working perfectly with tls but in my case the problem for me is my authenticator and my radius server both are on virtualbox with two diffrent ubuntu as virtual machines lets say ubuntu 1 as authenticator ubuntu 2 as radius server . in config.xml when i configure with pac address as my raspberry pi , authenticator ip address(ubuntu 1) and server ip address(ubuntu2) than i got memory allocation error other wise if i use any windows or mac ip address in place of ubuntu2 as radius server than everything is working fine . i didnot understand is there the problem two virtual machines cannot talk as authenticator and server ? On 1 Jul 2013, at 18:47, Francisco Vidal Meca wrote: > Hi Anmolmeet Singh Malhi, > > I went over the traces and your setup and the only thing that looks completely "unknown" for us is the usage of the RaspberryPi as PaC. > > Since OpenPANA is the result of work done for the University degree and lots of free-time (it was September 2011), we did not test it extensively. The code is proven to work on Virtual machines, x86 computers, some constrained devices (See PANATiki project http://sourceforge.net/projects/panatiki/ ) and there are some efforts that made it work on a Linksys WRT54G with OpenWRT firmware (reference in Spanish http://www.josevelasco.org/tag/openpana ). OpenPANA has evolved during this 2 years because of projects interested on it, PANATiki aimed to put it in an IoT environment for example. > > Unfortunately, we cannot test every OS or architecture. I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial. > > I will try to find some time to set an scenario myself with VMs, but right now it is quite difficult for me to get anytime. Anyhow, I cannot promise that it is going to be anytime soon. > > All the best, > Francisco Vidal Meca > > > 2013/7/1 anmolmeet singh malhi <anm...@ym...> > i still dont understand why i get the malloc error when config.xml file is loaded even i change the config.xml file and also i did reinstall openpana several times . > the malloc memory corruption error suppose to come when i use the server ip address as in case of eap passthrough . how to solve this problem i alreadty spend lot of time in debugging and using malloc() but still i got same error . > > On 28 Jun 2013, at 18:20, Pedro Moreno Sánchez wrote: > >> The authenticator in the pass-through EAP mode (e.g. mode which is used in OpenPANA) needs only the RADIUS client. This RADIUS client is already included in the OpenPANA source code so that you do not need any extra RADIUS implementation for that. >> >> On the other hand, you need a RADIUS server implementation for the authentication server. As stated in the OpenPANA's manual, we have tested freeradius for that purpose and it correctly works. However, it is not mandatory to use freeradius. You could use any other available RADIUS implementation for this purpose. >> >> Hope it helps, >> Pedro. >> >> >> On 28 June 2013 16:42, anmolmeet singh malhi <anm...@ym...> wrote: >> do authenticator need freeradius >> >> On 27 Jun 2013, at 18:32, Pedro Moreno Sánchez wrote: >> >>> From the log you have reported in the last e-mail I can see that you have performed the following 3 steps: >>> 1. You have executed OpenPANA and it has run correctly. The client has not been authenticated because there is a communication problem between the PAA and the AS (note that in the log you can see: "PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.". This means that, given that there is not a correct communication between PAA and AS, the RADIUS client (which is inside the PAA) is retransmitting the RADIUS message. >>> >>> 2. You have opened the config.xml (pico config.xml) and (presumably) you have changed the configuration values >>> >>> 3. You have executed OpenPANA again. In this case you get the malloc() error when configuration file config.xml is loaded. Thus, I would suggest you to use the same config.xml file that you used in the first execution and try to see why there is not communication between the PAA and the AS. >>> >>> >>> On the other hand, I have taken a look at the config.xml file that you have attached in your last e-mail and I have seen some strange configuration: >>> * In the PaC configuration data section, within the User's credentials you have set up: >>> <USER>anmolmeet</USER> <!-- User's credential --> >>> <PASSWORD>775i65gv</PASSWORD> >>> * In the PAA configuration data section, within the Radius Server Information you have set up: >>> <AUTH_SERVER> <!-- Radius Server information --> >>> <IP_VERSION_AUTH>4</IP_VERSION_AUTH> >>> <AS_IP>192.168.0.10</AS_IP> >>> <AS_PORT>1812</AS_PORT> >>> <SHARED_SECRET>775i65gv</SHARED_SECRET> >>> </AUTH_SERVER> >>> >>> This configuration means that the password used by the user to authenticate against the authentication server (i.e. in EAP-PSK authentication method) is the same as the key shared between the RADIUS client and the RADIUS server. Are you sure that your scenario's keys are really configured in such a way? >>> >>> Hope it helps, >>> Pedro. >>> >>> >>> On 27 June 2013 10:08, Anmol Malhi <anm...@ym...> wrote: >>> thankyou i attach my config.xml file >>> and my network setup is as >>> >>> i use raspberry pi(192.168.0.8) as my PAC >>> i use virtualbox Ubuntu1 (192.168.0.9) as my PAA >>> and i use virtualbox ubuntu2(192.168.0.10) as my AS >>> >>> when i use my AS server ip in my config.xml i got this error >>> >>> >>> Pana Message Name: PANA-Auth >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Reserved:0 | MessageLength: 68 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Flags: ------ | MessageType: 2 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Session Identifier: 0X6B706F69 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Sequence Number: 0XBA16B80 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> AVP Name: EAP-Payload >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Code:2 | AVP Flags:0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Length: 14 | Reserved: 0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Value: EAP-Payload omitted. >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> AVP Name: Nonce >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Code:5 | AVP Flags:0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Length: 20 | Reserved: 0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Value: 7E 6B A1 0B B3 C5 6B 7E D7 F7 31 41 AF 43 8F 64 63 >>> 5E 21 2D >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> PANA: Received PANA-Auth message. >>> PANA: DEBUG: Session updated with message:. >>> PANA: DEBUG: PAN. >>> PANA: DEBUG: It's been detected a Nonce AVP. >>> PANA: DEBUG: Trying a transition... >>> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_PAN_OR_PAR. >>> PANA: DEBUG: txEAP function. >>> EAP: EAP entering state RECEIVED >>> EAP: parseEapResp: rxResp=1 respId=179 respMethod=1 respVendor=0 respVendorMethod=0 >>> EAP: EAP entering state INTEGRITY_CHECK >>> EAP: EAP entering state METHOD_RESPONSE >>> EAP-Identity: Peer identity - hexdump_ascii(len=9): >>> 61 6e 6d 6f 6c 6d 65 65 74 anmolmeet >>> EAP: EAP entering state SELECT_ACTION >>> EAP: getDecision: -> PASSTHROUGH >>> EAP: EAP entering state INITIALIZE_PASSTHROUGH >>> EAP: EAP entering state AAA_REQUEST >>> EAP: EAP entering state AAA_IDLE >>> Encapsulating EAP message into a RADIUS packet >>> Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6d 6f 6c 6d 65 65 74 >>> hostapd_logger: Sending RADIUS message to authentication server >>> RADIUS message: code=1 (Access-Request) identifier=0 length=107 >>> Attribute 1 (User-Name) length=11 >>> Value: 'anmolmeet' >>> Attribute 4 (NAS-IP-Address) length=6 >>> Value: 127.0.0.1 >>> Attribute 31 (Calling-Station-Id) length=19 >>> Value: '00-00-00-00-00-00' >>> Attribute 12 (Framed-MTU) length=6 >>> Value: 1400 >>> Attribute 61 (NAS-Port-Type) length=6 >>> Value: 19 >>> Attribute 77 (Connect-Info) length=5 >>> Value: 'CON' >>> Attribute 79 (EAP-Message) length=16 >>> Value: 02 b3 00 0e 01 61 6e 6d 6f 6c 6d 65 65 74 >>> Attribute 80 (Message-Authenticator) length=18 >>> Value: 01 ab ae c8 e5 2c 36 52 5a aa ae 36 4d 33 84 f2 >>> hostapd_logger: Next RADIUS client retransmit in 3 seconds >>> >>> PANA: DEBUG: Finished txEAP function >>> . >>> PANA: DEBUG: rtxTimerStop function. >>> PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802530665). >>> PANA: DEBUG: Starting to check EAP status (check_eap_status). >>> PANA: DEBUG: Finished EAP check. >>> PANA: DEBUG: PANA message treatment finished. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: Trying a transition... >>> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_EAP_MSG. >>> PANA: DEBUG: sessionTimerStop function. >>> PANA: DEBUG: Session with id 1802530665 not found in the alarm list. >>> PANA: DEBUG: sessionTimerStop finished. >>> PANA: DEBUG: disconnect function. >>> PANA: Entering state: CLOSED (Session ID: 1802530665). >>> ^Z >>> [5]+ Stopped ./openpaa >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> Use "fg" to return to nano. >>> >>> [6]+ Stopped pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# ./openpaa >>> >>> OpenPANA Server - 0.2.4 >>> http://openpana.sf.net >>> >>> Copyright (C) 2011 Pedro Moreno Sánchez and Francisco Vidal Meca >>> This program comes with ABSOLUTELY NO WARRANTY. >>> This is free software, and you are welcome to redistribute it >>> under certain conditions, see COPYING for details. >>> >>> PANA: warning: Loading config.xml from current directory. >>> EAP: Server state machine created >>> PANA: DEBUG: rtxTimerStop function. >>> PANA: DEBUG: There isn't any session associated. >>> hostapd_logger: Authentication server 192.168.0.10:1812 >>> RADIUS local address: 192.168.0.9:48634 >>> PANA: DEBUG: thread '0' as worker manager. >>> PANA: DEBUG: Starting thread '0'. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: warning: Loading config.xml from current directory. >>> *** glibc detected *** ./openpaa: malloc(): memory corruption: 0x093edb28 *** >>> ======= Backtrace: ========= >>> /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2] >>> /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e] >>> /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498] >>> /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c] >>> /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743] >>> /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f] >>> /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee] >>> ./openpaa[0x8054a36] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8055327] >>> ./openpaa[0x8049a60] >>> ./openpaa[0x8052437] >>> ./openpaa[0x8052f50] >>> /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31] >>> /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce] >>> ======= Memory map: ======== >>> 00110000-00257000 r-xp 00000000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >>> 00257000-0025b000 r--p 00147000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >>> 0025b000-0025c000 rw-p 0014b000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >>> 0025c000-0025d000 rw-p 00000000 00:00 0 >>> 0025d000-00270000 r-xp 00000000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 00270000-00271000 r--p 00012000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 00271000-00272000 rw-p 00013000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 002b9000-002e1000 r-xp 00000000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >>> 002e1000-002e2000 r--p 00028000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >>> 002e2000-002e3000 rw-p 00029000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >>> 00304000-00322000 r-xp 00000000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >>> 00322000-00323000 r--p 0001d000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >>> 00323000-00324000 rw-p 0001e000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >>> 0035a000-004e7000 r-xp 00000000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004e7000-004f5000 r--p 0018d000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004f5000-004fb000 rw-p 0019b000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004fb000-004fe000 rw-p 00000000 00:00 0 >>> 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >>> 00618000-00619000 r--p 00016000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >>> 00619000-0061a000 rw-p 00017000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >>> 0061a000-0061c000 rw-p 00000000 00:00 0 >>> 0061c000-00792000 r-xp 00000000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >>> 00792000-00794000 r--p 00176000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >>> 00794000-00795000 rw-p 00178000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >>> 00795000-00798000 rw-p 00000000 00:00 0 >>> 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso] >>> 007bf000-007c2000 r-xp 00000000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >>> 007c2000-007c3000 r--p 00002000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >>> 007c3000-007c4000 rw-p 00003000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >>> 00e49000-00e65000 r-xp 00000000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >>> 00e65000-00e66000 r--p 0001b000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >>> 00e66000-00e67000 rw-p 0001c000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >>> 08048000-0809f000 r-xp 00000000 08:01 39668 /home/anmolm/trunk/src/openpaa >>> 0809f000-080a0000 r--p 00056000 08:01 39668 /home/anmolm/trunk/src/openpaa >>> 080a0000-080a1000 rw-p 00057000 08:01 39668 /home/anmolm/trunk/src/openpaa >>> 093de000-093ff000 rw-p 00000000 00:00 0 [heap] >>> b6600000-b6621000 rw-p 00000000 00:00 0 >>> b6621000-b6700000 ---p 00000000 00:00 0 >>> b67ed000-b67ee000 ---p 00000000 00:00 0 >>> b67ee000-b6fee000 rw-p 00000000 00:00 0 >>> b6fee000-b6fef000 ---p 00000000 00:00 0 >>> b6fef000-b77f2000 rw-p 00000000 00:00 0 >>> b7802000-b7805000 rw-p 00000000 00:00 0 >>> bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack] >>> Aborted >>> >>> >>> >>> From: Francisco Vidal Meca <f.v...@um...> >>> To: anmolmeet singh malhi <anm...@ym...> >>> Cc: Pedro Moreno Sánchez <p.m...@um...>; "ope...@li..." <ope...@li...> >>> Sent: Thursday, 27 June 2013, 8:44 >>> Subject: Re: [Openpana-users] openpana implementation >>> >>> Hi Anmolmeet Singh Malhi, >>> >>> With so few details it's difficult to have an idea of what's going on with your "config.xml". >>> >>> Some details about your network set up, where the different entities (PaC, PAA, RADIUS server) are located and the config.xml might help in determine if there is some error in your config.xml, wrong network setup or bugs in the OpenPANA implementation itself. Attaching the config.xml itself might also help. >>> >>> Please take a look at the documentation provided in [1] and compare your config.xml file with the one given by default. There car be some parsing problems such as introducing the IP with a wrong format. >>> >>> Best regards, >>> Francisco Vidal Meca >>> >>> [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/ >>> >>> >>> 2013/6/27 anmolmeet singh malhi <anm...@ym...> >>> hello sorry to interupt you >>> if i use my auth server ip address in config.xml i got memory error somthing like >>> >>> openpaa malloc() memory corruption >>> please help >>> On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez >>> >>>> Hi Anmol. >>>> >>>> Inside the configuration file (config.xml) you have three different sections (PaC, PAA and PRE configuration data). Inside the PAA Configuration Data section, you have the <AUTH_SERVER> subsection, where you can configure the values corresponding to the RADIUS server. In particular, you can configure: >>>> - <IP_VERSION_AUTH> IP version to be used in the communication between the PAA and the RADIUS server >>>> - <AS_IP> IP address in which the RADIUS server will be listening to incoming request >>>> - <AS_PORT> UDP port in which the RADIUS server will be listening to incoming request >>>> - <SHARED_SECRET> Shared secret between the RADIUS server and the RADIUS client (note that the former is included inside the PAA functionality). >>>> >>>> You can find more info about the configuration file and some other questions in the documentation of the OpenPANA's project, under the link: >>>> http://sourceforge.net/projects/openpana/files/docs/ >>>> >>>> Hope it helps, >>>> Pedro. >>>> >>>> >>>> On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...> wrote: >>>> I need help in configuration of config.xml . >>>> what should be the ip address of radius server is that my ip address of PAA ? >>>> please help i am doing research on pana protocol >>>> Thankyou >>>> ------------------------------------------------------------------------------ >>>> This SF.net email is sponsored by Windows: >>>> >>>> Build for Windows Store. >>>> >>>> http://p.sf.net/sfu/windows-dev2dev >>>> _______________________________________________ >>>> Openpana-users mailing list >>>> Ope...@li... >>>> https://lists.sourceforge.net/lists/listinfo/openpana-users >>>> >>>> >>>> >>>> -- >>>> ---------------------------------------------------------------------------- >>>> Pedro Moreno Sánchez - MSc Computer Engineer >>>> Networks and Telematics >>>> Faculty of Computer Science - University of Murcia >>>> 30100 - Murcia - Spain >>>> email: p.m...@um... >>>> ---------------------------------------------------------------------------- >>>> >>>> >>>> >>>> >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Openpana-users mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openpana-users >>> >>> >>> >>> >>> >>> >>> >>> -- >>> ---------------------------------------------------------------------------- >>> Pedro Moreno Sánchez - MSc Computer Engineer >>> Networks and Telematics >>> Faculty of Computer Science - University of Murcia >>> 30100 - Murcia - Spain >>> email: p.m...@um... >>> ---------------------------------------------------------------------------- >>> >>> >>> >>> >>> >> >> >> >> >> -- >> ---------------------------------------------------------------------------- >> Pedro Moreno Sánchez - MSc Computer Engineer >> Networks and Telematics >> Faculty of Computer Science - University of Murcia >> 30100 - Murcia - Spain >> email: p.m...@um... >> ---------------------------------------------------------------------------- >> >> >> >> >> > > |
|
From: Francisco V. M. <f.v...@um...> - 2013-07-01 17:48:11
|
Hi Anmolmeet Singh Malhi, I went over the traces and your setup and the only thing that looks completely "unknown" for us is the usage of the RaspberryPi as PaC. Since OpenPANA is the result of work done for the University degree and lots of free-time (it was September 2011), we did not test it extensively. The code is proven to work on Virtual machines, x86 computers, some constrained devices (See PANATiki project http://sourceforge.net/projects/panatiki/ ) and there are some efforts that made it work on a Linksys WRT54G with OpenWRT firmware (reference in Spanish http://www.josevelasco.org/tag/openpana ). OpenPANA has evolved during this 2 years because of projects interested on it, PANATiki aimed to put it in an IoT environment for example. Unfortunately, we cannot test every OS or architecture. I suggest you to track down the error in an iterative way. OpenPANA has proven to work well between virtual machines if configures appropiately. Once you get the PaC working in a VirtualMachine, adding another client from any other device which can communicate is trivial. I will try to find some time to set an scenario myself with VMs, but right now it is quite difficult for me to get anytime. Anyhow, I cannot promise that it is going to be anytime soon. All the best, Francisco Vidal Meca 2013/7/1 anmolmeet singh malhi <anm...@ym...> > i still dont understand why i get the malloc error when config.xml file is > loaded even i change the config.xml file and also i did reinstall openpana > several times . > the malloc memory corruption error suppose to come when i use the server > ip address as in case of eap passthrough . how to solve this problem i > alreadty spend lot of time in debugging and using malloc() but still i got > same error . > > On 28 Jun 2013, at 18:20, Pedro Moreno Sánchez wrote: > > The authenticator in the pass-through EAP mode (e.g. mode which is used > in OpenPANA) needs only the RADIUS client. This RADIUS client is already > included in the OpenPANA source code so that you do not need any extra > RADIUS implementation for that. > > On the other hand, you need a RADIUS server implementation for the > authentication server. As stated in the OpenPANA's manual, we have tested > freeradius for that purpose and it correctly works. However, it is not > mandatory to use freeradius. You could use any other available RADIUS > implementation for this purpose. > > Hope it helps, > Pedro. > > > On 28 June 2013 16:42, anmolmeet singh malhi <anm...@ym...> wrote: > >> do authenticator need freeradius >> >> On 27 Jun 2013, at 18:32, Pedro Moreno Sánchez wrote: >> >> From the log you have reported in the last e-mail I can see that you have >> performed the following 3 steps: >> 1. You have executed OpenPANA and it has run correctly. The client has >> not been authenticated because there is a communication problem between the >> PAA and the AS (note that in the log you can see: "PANA: DEBUG: An >> AAA_RETRANSMISSION alarm ocurred.". This means that, given that there is >> not a correct communication between PAA and AS, the RADIUS client (which >> is inside the PAA) is retransmitting the RADIUS message. >> >> 2. You have opened the config.xml (pico config.xml) and (presumably) you >> have changed the configuration values >> >> 3. You have executed OpenPANA again. In this case you get the malloc() >> error when configuration file config.xml is loaded. Thus, I would >> suggest you to use the same config.xml file that you used in the first >> execution and try to see why there is not communication between the PAAand the AS. >> >> >> On the other hand, I have taken a look at the config.xml file that you >> have attached in your last e-mail and I have seen some strange >> configuration: >> * In the PaC configuration data section, within the User's credentials >> you have set up: >> <USER>anmolmeet</USER> <!-- User's credential --> >> <PASSWORD>775i65gv</PASSWORD> >> * In the PAA configuration data section, within the Radius Server >> Information you have set up: >> <AUTH_SERVER> <!-- Radius Server information --> >> <IP_VERSION_AUTH>4</IP_VERSION_AUTH> >> <AS_IP>192.168.0.10</AS_IP> >> <AS_PORT>1812</AS_PORT> >> <SHARED_SECRET>775i65gv</SHARED_SECRET> >> </AUTH_SERVER> >> >> This configuration means that the password used by the user to >> authenticate against the authentication server (i.e. in EAP-PSKauthentication method) is the same as the key shared between the RADIUS >> client and the RADIUS server. Are you sure that your scenario's keys are >> really configured in such a way? >> >> Hope it helps, >> Pedro. >> >> >> On 27 June 2013 10:08, Anmol Malhi <anm...@ym...> wrote: >> >>> thankyou i attach my config.xml file >>> and my network setup is as >>> >>> i use raspberry pi(192.168.0.8) as my PAC >>> i use virtualbox Ubuntu1 (192.168.0.9) as my PAA >>> and i use virtualbox ubuntu2(192.168.0.10) as my AS >>> >>> when i use my AS server ip in my config.xml i got this error >>> >>> >>> Pana Message Name: PANA-Auth >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Reserved:0 | MessageLength: 68 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Flags: ------ | MessageType: 2 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Session Identifier: 0X6B706F69 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Sequence Number: 0XBA16B80 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> AVP Name: EAP-Payload >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Code:2 | AVP Flags:0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Length: 14 | Reserved: 0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Value: EAP-Payload omitted. >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> AVP Name: Nonce >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Code:5 | AVP Flags:0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Length: 20 | Reserved: 0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Value: 7E 6B A1 0B B3 C5 6B 7E D7 F7 31 41 AF 43 8F 64 63 >>> 5E 21 2D >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> PANA: Received PANA-Auth message. >>> PANA: DEBUG: Session updated with message:. >>> PANA: DEBUG: PAN. >>> PANA: DEBUG: It's been detected a Nonce AVP. >>> PANA: DEBUG: Trying a transition... >>> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_PAN_OR_PAR. >>> PANA: DEBUG: txEAP function. >>> EAP: EAP entering state RECEIVED >>> EAP: parseEapResp: rxResp=1 respId=179 respMethod=1 respVendor=0 >>> respVendorMethod=0 >>> EAP: EAP entering state INTEGRITY_CHECK >>> EAP: EAP entering state METHOD_RESPONSE >>> EAP-Identity: Peer identity - hexdump_ascii(len=9): >>> 61 6e 6d 6f 6c 6d 65 65 74 anmolmeet >>> EAP: EAP entering state SELECT_ACTION >>> EAP: getDecision: -> PASSTHROUGH >>> EAP: EAP entering state INITIALIZE_PASSTHROUGH >>> EAP: EAP entering state AAA_REQUEST >>> EAP: EAP entering state AAA_IDLE >>> Encapsulating EAP message into a RADIUS packet >>> Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6d >>> 6f 6c 6d 65 65 74 >>> hostapd_logger: Sending RADIUS message to authentication server >>> RADIUS message: code=1 (Access-Request) identifier=0 length=107 >>> Attribute 1 (User-Name) length=11 >>> Value: 'anmolmeet' >>> Attribute 4 (NAS-IP-Address) length=6 >>> Value: 127.0.0.1 >>> Attribute 31 (Calling-Station-Id) length=19 >>> Value: '00-00-00-00-00-00' >>> Attribute 12 (Framed-MTU) length=6 >>> Value: 1400 >>> Attribute 61 (NAS-Port-Type) length=6 >>> Value: 19 >>> Attribute 77 (Connect-Info) length=5 >>> Value: 'CON' >>> Attribute 79 (EAP-Message) length=16 >>> Value: 02 b3 00 0e 01 61 6e 6d 6f 6c 6d 65 65 74 >>> Attribute 80 (Message-Authenticator) length=18 >>> Value: 01 ab ae c8 e5 2c 36 52 5a aa ae 36 4d 33 84 f2 >>> hostapd_logger: Next RADIUS client retransmit in 3 seconds >>> >>> PANA: DEBUG: Finished txEAP function >>> . >>> PANA: DEBUG: rtxTimerStop function. >>> PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802530665). >>> PANA: DEBUG: Starting to check EAP status (check_eap_status). >>> PANA: DEBUG: Finished EAP check. >>> PANA: DEBUG: PANA message treatment finished. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: Trying a transition... >>> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_EAP_MSG. >>> PANA: DEBUG: sessionTimerStop function. >>> PANA: DEBUG: Session with id 1802530665 not found in the alarm list. >>> PANA: DEBUG: sessionTimerStop finished. >>> PANA: DEBUG: disconnect function. >>> PANA: Entering state: CLOSED (Session ID: 1802530665). >>> ^Z >>> [5]+ Stopped ./openpaa >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> Use "fg" to return to nano. >>> >>> [6]+ Stopped pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# ./openpaa >>> >>> OpenPANA Server - 0.2.4 >>> http://openpana.sf.net >>> >>> Copyright (C) 2011 Pedro Moreno Sánchez and Francisco Vidal Meca >>> This program comes with ABSOLUTELY NO WARRANTY. >>> This is free software, and you are welcome to redistribute it >>> under certain conditions, see COPYING for details. >>> >>> PANA: warning: Loading config.xml from current directory. >>> EAP: Server state machine created >>> PANA: DEBUG: rtxTimerStop function. >>> PANA: DEBUG: There isn't any session associated. >>> hostapd_logger: Authentication server 192.168.0.10:1812 >>> RADIUS local address: 192.168.0.9:48634 >>> PANA: DEBUG: thread '0' as worker manager. >>> PANA: DEBUG: Starting thread '0'. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: warning: Loading config.xml from current directory. >>> *** glibc detected *** ./openpaa: malloc(): memory corruption: >>> 0x093edb28 *** >>> ======= Backtrace: ========= >>> /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2] >>> /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e] >>> /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498] >>> /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c] >>> /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743] >>> /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f] >>> /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee] >>> ./openpaa[0x8054a36] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8055327] >>> ./openpaa[0x8049a60] >>> ./openpaa[0x8052437] >>> ./openpaa[0x8052f50] >>> /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31] >>> /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce] >>> ======= Memory map: ======== >>> 00110000-00257000 r-xp 00000000 08:01 297593 >>> /usr/lib/libxml2.so.2.7.8 >>> 00257000-0025b000 r--p 00147000 08:01 297593 >>> /usr/lib/libxml2.so.2.7.8 >>> 0025b000-0025c000 rw-p 0014b000 08:01 297593 >>> /usr/lib/libxml2.so.2.7.8 >>> 0025c000-0025d000 rw-p 00000000 00:00 0 >>> 0025d000-00270000 r-xp 00000000 08:01 134695 >>> /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 00270000-00271000 r--p 00012000 08:01 134695 >>> /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 00271000-00272000 rw-p 00013000 08:01 134695 >>> /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 002b9000-002e1000 r-xp 00000000 08:01 134642 /lib/i386-linux-gnu/ >>> libm-2.13.so >>> 002e1000-002e2000 r--p 00028000 08:01 134642 /lib/i386-linux-gnu/ >>> libm-2.13.so >>> 002e2000-002e3000 rw-p 00029000 08:01 134642 /lib/i386-linux-gnu/ >>> libm-2.13.so >>> 00304000-00322000 r-xp 00000000 08:01 134599 /lib/i386-linux-gnu/ >>> ld-2.13.so >>> 00322000-00323000 r--p 0001d000 08:01 134599 /lib/i386-linux-gnu/ >>> ld-2.13.so >>> 00323000-00324000 rw-p 0001e000 08:01 134599 /lib/i386-linux-gnu/ >>> ld-2.13.so >>> 0035a000-004e7000 r-xp 00000000 08:01 139154 >>> /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004e7000-004f5000 r--p 0018d000 08:01 139154 >>> /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004f5000-004fb000 rw-p 0019b000 08:01 139154 >>> /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004fb000-004fe000 rw-p 00000000 00:00 0 >>> 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386-linux-gnu/ >>> libpthread-2.13.so >>> 00618000-00619000 r--p 00016000 08:01 134672 /lib/i386-linux-gnu/ >>> libpthread-2.13.so >>> 00619000-0061a000 rw-p 00017000 08:01 134672 /lib/i386-linux-gnu/ >>> libpthread-2.13.so >>> 0061a000-0061c000 rw-p 00000000 00:00 0 >>> 0061c000-00792000 r-xp 00000000 08:01 134612 /lib/i386-linux-gnu/ >>> libc-2.13.so >>> 00792000-00794000 r--p 00176000 08:01 134612 /lib/i386-linux-gnu/ >>> libc-2.13.so >>> 00794000-00795000 rw-p 00178000 08:01 134612 /lib/i386-linux-gnu/ >>> libc-2.13.so >>> 00795000-00798000 rw-p 00000000 00:00 0 >>> 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso] >>> 007bf000-007c2000 r-xp 00000000 08:01 134623 /lib/i386-linux-gnu/ >>> libdl-2.13.so >>> 007c2000-007c3000 r--p 00002000 08:01 134623 /lib/i386-linux-gnu/ >>> libdl-2.13.so >>> 007c3000-007c4000 rw-p 00003000 08:01 134623 /lib/i386-linux-gnu/ >>> libdl-2.13.so >>> 00e49000-00e65000 r-xp 00000000 08:01 134633 >>> /lib/i386-linux-gnu/libgcc_s.so.1 >>> 00e65000-00e66000 r--p 0001b000 08:01 134633 >>> /lib/i386-linux-gnu/libgcc_s.so.1 >>> 00e66000-00e67000 rw-p 0001c000 08:01 134633 >>> /lib/i386-linux-gnu/libgcc_s.so.1 >>> 08048000-0809f000 r-xp 00000000 08:01 39668 >>> /home/anmolm/trunk/src/openpaa >>> 0809f000-080a0000 r--p 00056000 08:01 39668 >>> /home/anmolm/trunk/src/openpaa >>> 080a0000-080a1000 rw-p 00057000 08:01 39668 >>> /home/anmolm/trunk/src/openpaa >>> 093de000-093ff000 rw-p 00000000 00:00 0 [heap] >>> b6600000-b6621000 rw-p 00000000 00:00 0 >>> b6621000-b6700000 ---p 00000000 00:00 0 >>> b67ed000-b67ee000 ---p 00000000 00:00 0 >>> b67ee000-b6fee000 rw-p 00000000 00:00 0 >>> b6fee000-b6fef000 ---p 00000000 00:00 0 >>> b6fef000-b77f2000 rw-p 00000000 00:00 0 >>> b7802000-b7805000 rw-p 00000000 00:00 0 >>> bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack] >>> Aborted >>> >>> >>> >>> ------------------------------ >>> *From:* Francisco Vidal Meca <f.v...@um...> >>> *To:* anmolmeet singh malhi <anm...@ym...> >>> *Cc:* Pedro Moreno Sánchez <p.m...@um...>; " >>> ope...@li..." < >>> ope...@li...> >>> *Sent:* Thursday, 27 June 2013, 8:44 >>> *Subject:* Re: [Openpana-users] openpana implementation >>> >>> Hi Anmolmeet Singh Malhi, >>> >>> With so few details it's difficult to have an idea of what's going on >>> with your "config.xml". >>> >>> Some details about your network set up, where the different entities >>> (PaC, PAA, RADIUS server) are located and the config.xml might help in >>> determine if there is some error in your config.xml, wrong network setup or >>> bugs in the OpenPANA implementation itself. Attaching the config.xml itself >>> might also help. >>> >>> Please take a look at the documentation provided in [1] and compare your >>> config.xml file with the one given by default. There car be some parsing >>> problems such as introducing the IP with a wrong format. >>> >>> Best regards, >>> Francisco Vidal Meca >>> >>> [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/ >>> >>> >>> 2013/6/27 anmolmeet singh malhi <anm...@ym...> >>> >>> hello sorry to interupt you >>> if i use my auth server ip address in config.xml i got memory error >>> somthing like >>> >>> openpaa malloc() memory corruption >>> please help >>> On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez >>> >>> Hi Anmol. >>> >>> Inside the configuration file (config.xml) you have three different >>> sections (PaC, PAA and PRE configuration data). Inside the PAAConfiguration Data section, you have the < >>> AUTH_SERVER> subsection, where you can configure the values >>> corresponding to the RADIUS server. In particular, you can configure: >>> - <IP_VERSION_AUTH> IP version to be used in the communication >>> between the PAA and the RADIUS server >>> - <AS_IP> IP address in which the RADIUS server will be listening to >>> incoming request >>> - <AS_PORT> UDP port in which the RADIUS server will be listening to >>> incoming request >>> - <SHARED_SECRET> Shared secret between the RADIUS server and the >>> RADIUS client (note that the former is included inside the PAAfunctionality). >>> >>> You can find more info about the configuration file and some other >>> questions in the documentation of the OpenPANA's project, under the >>> link: >>> http://sourceforge.net/projects/openpana/files/docs/ >>> >>> Hope it helps, >>> Pedro. >>> >>> >>> On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...>wrote: >>> >>> I need help in configuration of config.xml . >>> what should be the ip address of radius server is that my ip address >>> of PAA ? >>> please help i am doing research on pana protocol >>> Thankyou >>> >>> ------------------------------------------------------------------------------ >>> This SF.net <http://sf.net/> email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Openpana-users mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openpana-users >>> >>> >>> >>> >>> -- >>> >>> ---------------------------------------------------------------------------- >>> Pedro Moreno Sánchez - MSc Computer Engineer >>> Networks and Telematics >>> Faculty of Computer Science - University of Murcia >>> 30100 - Murcia - Spain >>> email: p.m...@um... >>> >>> ---------------------------------------------------------------------------- >>> >>> >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Openpana-users mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openpana-users >>> >>> >>> >>> >>> >> >> >> -- >> >> ---------------------------------------------------------------------------- >> Pedro Moreno Sánchez - MSc Computer Engineer >> Networks and Telematics >> Faculty of Computer Science - University of Murcia >> 30100 - Murcia - Spain >> email: p.m...@um... >> >> ---------------------------------------------------------------------------- >> >> >> >> >> >> >> > > > -- > > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > > ---------------------------------------------------------------------------- > > > > > > > |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-07-01 16:12:58
|
i still dont understand why i get the malloc error when config.xml file is loaded even i change the config.xml file and also i did reinstall openpana several times . the malloc memory corruption error suppose to come when i use the server ip address as in case of eap passthrough . how to solve this problem i alreadty spend lot of time in debugging and using malloc() but still i got same error . On 28 Jun 2013, at 18:20, Pedro Moreno Sánchez wrote: > The authenticator in the pass-through EAP mode (e.g. mode which is used in OpenPANA) needs only the RADIUS client. This RADIUS client is already included in the OpenPANA source code so that you do not need any extra RADIUS implementation for that. > > On the other hand, you need a RADIUS server implementation for the authentication server. As stated in the OpenPANA's manual, we have tested freeradius for that purpose and it correctly works. However, it is not mandatory to use freeradius. You could use any other available RADIUS implementation for this purpose. > > Hope it helps, > Pedro. > > > On 28 June 2013 16:42, anmolmeet singh malhi <anm...@ym...> wrote: > do authenticator need freeradius > > On 27 Jun 2013, at 18:32, Pedro Moreno Sánchez wrote: > >> From the log you have reported in the last e-mail I can see that you have performed the following 3 steps: >> 1. You have executed OpenPANA and it has run correctly. The client has not been authenticated because there is a communication problem between the PAA and the AS (note that in the log you can see: "PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.". This means that, given that there is not a correct communication between PAA and AS, the RADIUS client (which is inside the PAA) is retransmitting the RADIUS message. >> >> 2. You have opened the config.xml (pico config.xml) and (presumably) you have changed the configuration values >> >> 3. You have executed OpenPANA again. In this case you get the malloc() error when configuration file config.xml is loaded. Thus, I would suggest you to use the same config.xml file that you used in the first execution and try to see why there is not communication between the PAA and the AS. >> >> >> On the other hand, I have taken a look at the config.xml file that you have attached in your last e-mail and I have seen some strange configuration: >> * In the PaC configuration data section, within the User's credentials you have set up: >> <USER>anmolmeet</USER> <!-- User's credential --> >> <PASSWORD>775i65gv</PASSWORD> >> * In the PAA configuration data section, within the Radius Server Information you have set up: >> <AUTH_SERVER> <!-- Radius Server information --> >> <IP_VERSION_AUTH>4</IP_VERSION_AUTH> >> <AS_IP>192.168.0.10</AS_IP> >> <AS_PORT>1812</AS_PORT> >> <SHARED_SECRET>775i65gv</SHARED_SECRET> >> </AUTH_SERVER> >> >> This configuration means that the password used by the user to authenticate against the authentication server (i.e. in EAP-PSK authentication method) is the same as the key shared between the RADIUS client and the RADIUS server. Are you sure that your scenario's keys are really configured in such a way? >> >> Hope it helps, >> Pedro. >> >> >> On 27 June 2013 10:08, Anmol Malhi <anm...@ym...> wrote: >> thankyou i attach my config.xml file >> and my network setup is as >> >> i use raspberry pi(192.168.0.8) as my PAC >> i use virtualbox Ubuntu1 (192.168.0.9) as my PAA >> and i use virtualbox ubuntu2(192.168.0.10) as my AS >> >> when i use my AS server ip in my config.xml i got this error >> >> >> Pana Message Name: PANA-Auth >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Reserved:0 | MessageLength: 68 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Flags: ------ | MessageType: 2 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Session Identifier: 0X6B706F69 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Sequence Number: 0XBA16B80 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> AVP Name: EAP-Payload >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Code:2 | AVP Flags:0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Length: 14 | Reserved: 0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Value: EAP-Payload omitted. >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> AVP Name: Nonce >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Code:5 | AVP Flags:0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Length: 20 | Reserved: 0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Value: 7E 6B A1 0B B3 C5 6B 7E D7 F7 31 41 AF 43 8F 64 63 >> 5E 21 2D >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> PANA: Received PANA-Auth message. >> PANA: DEBUG: Session updated with message:. >> PANA: DEBUG: PAN. >> PANA: DEBUG: It's been detected a Nonce AVP. >> PANA: DEBUG: Trying a transition... >> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_PAN_OR_PAR. >> PANA: DEBUG: txEAP function. >> EAP: EAP entering state RECEIVED >> EAP: parseEapResp: rxResp=1 respId=179 respMethod=1 respVendor=0 respVendorMethod=0 >> EAP: EAP entering state INTEGRITY_CHECK >> EAP: EAP entering state METHOD_RESPONSE >> EAP-Identity: Peer identity - hexdump_ascii(len=9): >> 61 6e 6d 6f 6c 6d 65 65 74 anmolmeet >> EAP: EAP entering state SELECT_ACTION >> EAP: getDecision: -> PASSTHROUGH >> EAP: EAP entering state INITIALIZE_PASSTHROUGH >> EAP: EAP entering state AAA_REQUEST >> EAP: EAP entering state AAA_IDLE >> Encapsulating EAP message into a RADIUS packet >> Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6d 6f 6c 6d 65 65 74 >> hostapd_logger: Sending RADIUS message to authentication server >> RADIUS message: code=1 (Access-Request) identifier=0 length=107 >> Attribute 1 (User-Name) length=11 >> Value: 'anmolmeet' >> Attribute 4 (NAS-IP-Address) length=6 >> Value: 127.0.0.1 >> Attribute 31 (Calling-Station-Id) length=19 >> Value: '00-00-00-00-00-00' >> Attribute 12 (Framed-MTU) length=6 >> Value: 1400 >> Attribute 61 (NAS-Port-Type) length=6 >> Value: 19 >> Attribute 77 (Connect-Info) length=5 >> Value: 'CON' >> Attribute 79 (EAP-Message) length=16 >> Value: 02 b3 00 0e 01 61 6e 6d 6f 6c 6d 65 65 74 >> Attribute 80 (Message-Authenticator) length=18 >> Value: 01 ab ae c8 e5 2c 36 52 5a aa ae 36 4d 33 84 f2 >> hostapd_logger: Next RADIUS client retransmit in 3 seconds >> >> PANA: DEBUG: Finished txEAP function >> . >> PANA: DEBUG: rtxTimerStop function. >> PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802530665). >> PANA: DEBUG: Starting to check EAP status (check_eap_status). >> PANA: DEBUG: Finished EAP check. >> PANA: DEBUG: PANA message treatment finished. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: Trying a transition... >> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_EAP_MSG. >> PANA: DEBUG: sessionTimerStop function. >> PANA: DEBUG: Session with id 1802530665 not found in the alarm list. >> PANA: DEBUG: sessionTimerStop finished. >> PANA: DEBUG: disconnect function. >> PANA: Entering state: CLOSED (Session ID: 1802530665). >> ^Z >> [5]+ Stopped ./openpaa >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >> Use "fg" to return to nano. >> >> [6]+ Stopped pico config.xml >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# ./openpaa >> >> OpenPANA Server - 0.2.4 >> http://openpana.sf.net >> >> Copyright (C) 2011 Pedro Moreno Sánchez and Francisco Vidal Meca >> This program comes with ABSOLUTELY NO WARRANTY. >> This is free software, and you are welcome to redistribute it >> under certain conditions, see COPYING for details. >> >> PANA: warning: Loading config.xml from current directory. >> EAP: Server state machine created >> PANA: DEBUG: rtxTimerStop function. >> PANA: DEBUG: There isn't any session associated. >> hostapd_logger: Authentication server 192.168.0.10:1812 >> RADIUS local address: 192.168.0.9:48634 >> PANA: DEBUG: thread '0' as worker manager. >> PANA: DEBUG: Starting thread '0'. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: warning: Loading config.xml from current directory. >> *** glibc detected *** ./openpaa: malloc(): memory corruption: 0x093edb28 *** >> ======= Backtrace: ========= >> /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2] >> /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e] >> /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498] >> /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c] >> /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743] >> /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f] >> /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee] >> ./openpaa[0x8054a36] >> ./openpaa[0x8054c38] >> ./openpaa[0x8054c38] >> ./openpaa[0x8054c38] >> ./openpaa[0x8055327] >> ./openpaa[0x8049a60] >> ./openpaa[0x8052437] >> ./openpaa[0x8052f50] >> /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31] >> /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce] >> ======= Memory map: ======== >> 00110000-00257000 r-xp 00000000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >> 00257000-0025b000 r--p 00147000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >> 0025b000-0025c000 rw-p 0014b000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >> 0025c000-0025d000 rw-p 00000000 00:00 0 >> 0025d000-00270000 r-xp 00000000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >> 00270000-00271000 r--p 00012000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >> 00271000-00272000 rw-p 00013000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >> 002b9000-002e1000 r-xp 00000000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >> 002e1000-002e2000 r--p 00028000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >> 002e2000-002e3000 rw-p 00029000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >> 00304000-00322000 r-xp 00000000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >> 00322000-00323000 r--p 0001d000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >> 00323000-00324000 rw-p 0001e000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >> 0035a000-004e7000 r-xp 00000000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >> 004e7000-004f5000 r--p 0018d000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >> 004f5000-004fb000 rw-p 0019b000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >> 004fb000-004fe000 rw-p 00000000 00:00 0 >> 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >> 00618000-00619000 r--p 00016000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >> 00619000-0061a000 rw-p 00017000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >> 0061a000-0061c000 rw-p 00000000 00:00 0 >> 0061c000-00792000 r-xp 00000000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >> 00792000-00794000 r--p 00176000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >> 00794000-00795000 rw-p 00178000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >> 00795000-00798000 rw-p 00000000 00:00 0 >> 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso] >> 007bf000-007c2000 r-xp 00000000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >> 007c2000-007c3000 r--p 00002000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >> 007c3000-007c4000 rw-p 00003000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >> 00e49000-00e65000 r-xp 00000000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >> 00e65000-00e66000 r--p 0001b000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >> 00e66000-00e67000 rw-p 0001c000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >> 08048000-0809f000 r-xp 00000000 08:01 39668 /home/anmolm/trunk/src/openpaa >> 0809f000-080a0000 r--p 00056000 08:01 39668 /home/anmolm/trunk/src/openpaa >> 080a0000-080a1000 rw-p 00057000 08:01 39668 /home/anmolm/trunk/src/openpaa >> 093de000-093ff000 rw-p 00000000 00:00 0 [heap] >> b6600000-b6621000 rw-p 00000000 00:00 0 >> b6621000-b6700000 ---p 00000000 00:00 0 >> b67ed000-b67ee000 ---p 00000000 00:00 0 >> b67ee000-b6fee000 rw-p 00000000 00:00 0 >> b6fee000-b6fef000 ---p 00000000 00:00 0 >> b6fef000-b77f2000 rw-p 00000000 00:00 0 >> b7802000-b7805000 rw-p 00000000 00:00 0 >> bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack] >> Aborted >> >> >> >> From: Francisco Vidal Meca <f.v...@um...> >> To: anmolmeet singh malhi <anm...@ym...> >> Cc: Pedro Moreno Sánchez <p.m...@um...>; "ope...@li..." <ope...@li...> >> Sent: Thursday, 27 June 2013, 8:44 >> Subject: Re: [Openpana-users] openpana implementation >> >> Hi Anmolmeet Singh Malhi, >> >> With so few details it's difficult to have an idea of what's going on with your "config.xml". >> >> Some details about your network set up, where the different entities (PaC, PAA, RADIUS server) are located and the config.xml might help in determine if there is some error in your config.xml, wrong network setup or bugs in the OpenPANA implementation itself. Attaching the config.xml itself might also help. >> >> Please take a look at the documentation provided in [1] and compare your config.xml file with the one given by default. There car be some parsing problems such as introducing the IP with a wrong format. >> >> Best regards, >> Francisco Vidal Meca >> >> [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/ >> >> >> 2013/6/27 anmolmeet singh malhi <anm...@ym...> >> hello sorry to interupt you >> if i use my auth server ip address in config.xml i got memory error somthing like >> >> openpaa malloc() memory corruption >> please help >> On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez >> >>> Hi Anmol. >>> >>> Inside the configuration file (config.xml) you have three different sections (PaC, PAA and PRE configuration data). Inside the PAA Configuration Data section, you have the <AUTH_SERVER> subsection, where you can configure the values corresponding to the RADIUS server. In particular, you can configure: >>> - <IP_VERSION_AUTH> IP version to be used in the communication between the PAA and the RADIUS server >>> - <AS_IP> IP address in which the RADIUS server will be listening to incoming request >>> - <AS_PORT> UDP port in which the RADIUS server will be listening to incoming request >>> - <SHARED_SECRET> Shared secret between the RADIUS server and the RADIUS client (note that the former is included inside the PAA functionality). >>> >>> You can find more info about the configuration file and some other questions in the documentation of the OpenPANA's project, under the link: >>> http://sourceforge.net/projects/openpana/files/docs/ >>> >>> Hope it helps, >>> Pedro. >>> >>> >>> On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...> wrote: >>> I need help in configuration of config.xml . >>> what should be the ip address of radius server is that my ip address of PAA ? >>> please help i am doing research on pana protocol >>> Thankyou >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Openpana-users mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openpana-users >>> >>> >>> >>> -- >>> ---------------------------------------------------------------------------- >>> Pedro Moreno Sánchez - MSc Computer Engineer >>> Networks and Telematics >>> Faculty of Computer Science - University of Murcia >>> 30100 - Murcia - Spain >>> email: p.m...@um... >>> ---------------------------------------------------------------------------- >>> >>> >>> >>> >>> >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Openpana-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openpana-users >> >> >> >> >> >> >> >> -- >> ---------------------------------------------------------------------------- >> Pedro Moreno Sánchez - MSc Computer Engineer >> Networks and Telematics >> Faculty of Computer Science - University of Murcia >> 30100 - Murcia - Spain >> email: p.m...@um... >> ---------------------------------------------------------------------------- >> >> >> >> >> > > > > > -- > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > ---------------------------------------------------------------------------- > > > > > |
|
From: ANmol M. <anm...@ym...> - 2013-06-28 20:09:35
|
thankyou. so much Sent from my iPad On 28 Jun 2013, at 06:20 PM, Pedro Moreno Sánchez <p.m...@um...> wrote: The authenticator in the pass-through EAP mode (e.g. mode which is used in OpenPANA) needs only the RADIUS client. This RADIUS client is already included in the OpenPANA source code so that you do not need any extra RADIUS implementation for that. On the other hand, you need a RADIUS server implementation for the authentication server. As stated in the OpenPANA's manual, we have tested freeradius for that purpose and it correctly works. However, it is not mandatory to use freeradius. You could use any other available RADIUS implementation for this purpose. Hope it helps, Pedro. On 28 June 2013 16:42, anmolmeet singh malhi <anm...@ym...> wrote: > do authenticator need freeradius > > On 27 Jun 2013, at 18:32, Pedro Moreno Sánchez wrote: > >> From the log you have reported in the last e-mail I can see that you have performed the following 3 steps: >> 1. You have executed OpenPANA and it has run correctly. The client has not been authenticated because there is a communication problem between the PAA and the AS (note that in the log you can see: "PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.". This means that, given that there is not a correct communication between PAA and AS, the RADIUS client (which is inside the PAA) is retransmitting the RADIUS message. >> >> 2. You have opened the config.xml (pico config.xml) and (presumably) you have changed the configuration values >> >> 3. You have executed OpenPANA again. In this case you get the malloc() error when configuration file config.xml is loaded. Thus, I would suggest you to use the same config.xml file that you used in the first execution and try to see why there is not communication between the PAA and the AS. >> >> >> On the other hand, I have taken a look at the config.xml file that you have attached in your last e-mail and I have seen some strange configuration: >> * In the PaC configuration data section, within the User's credentials you have set up: >> <USER>anmolmeet</USER> <!-- User's credential --> >> <PASSWORD>775i65gv</PASSWORD> >> * In the PAA configuration data section, within the Radius Server Information you have set up: >> <AUTH_SERVER> <!-- Radius Server information --> >> <IP_VERSION_AUTH>4</IP_VERSION_AUTH> >> <AS_IP>192.168.0.10</AS_IP> >> <AS_PORT>1812</AS_PORT> >> <SHARED_SECRET>775i65gv</SHARED_SECRET> >> </AUTH_SERVER> >> >> This configuration means that the password used by the user to authenticate against the authentication server (i.e. in EAP-PSK authentication method) is the same as the key shared between the RADIUS client and the RADIUS server. Are you sure that your scenario's keys are really configured in such a way? >> >> Hope it helps, >> Pedro. >> >> >> On 27 June 2013 10:08, Anmol Malhi <anm...@ym...> wrote: >>> thankyou i attach my config.xml file >>> and my network setup is as >>> >>> i use raspberry pi(192.168.0.8) as my PAC >>> i use virtualbox Ubuntu1 (192.168.0.9) as my PAA >>> and i use virtualbox ubuntu2(192.168.0.10) as my AS >>> >>> when i use my AS server ip in my config.xml i got this error >>> >>> >>> Pana Message Name: PANA-Auth >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Reserved:0 | MessageLength: 68 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Flags: ------ | MessageType: 2 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Session Identifier: 0X6B706F69 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Sequence Number: 0XBA16B80 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> AVP Name: EAP-Payload >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Code:2 | AVP Flags:0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Length: 14 | Reserved: 0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Value: EAP-Payload omitted. >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> AVP Name: Nonce >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Code:5 | AVP Flags:0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | AVP Length: 20 | Reserved: 0 | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Value: 7E 6B A1 0B B3 C5 6B 7E D7 F7 31 41 AF 43 8F 64 63 >>> 5E 21 2D >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> PANA: Received PANA-Auth message. >>> PANA: DEBUG: Session updated with message:. >>> PANA: DEBUG: PAN. >>> PANA: DEBUG: It's been detected a Nonce AVP. >>> PANA: DEBUG: Trying a transition... >>> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_PAN_OR_PAR. >>> PANA: DEBUG: txEAP function. >>> EAP: EAP entering state RECEIVED >>> EAP: parseEapResp: rxResp=1 respId=179 respMethod=1 respVendor=0 respVendorMethod=0 >>> EAP: EAP entering state INTEGRITY_CHECK >>> EAP: EAP entering state METHOD_RESPONSE >>> EAP-Identity: Peer identity - hexdump_ascii(len=9): >>> 61 6e 6d 6f 6c 6d 65 65 74 anmolmeet >>> EAP: EAP entering state SELECT_ACTION >>> EAP: getDecision: -> PASSTHROUGH >>> EAP: EAP entering state INITIALIZE_PASSTHROUGH >>> EAP: EAP entering state AAA_REQUEST >>> EAP: EAP entering state AAA_IDLE >>> Encapsulating EAP message into a RADIUS packet >>> Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6d 6f 6c 6d 65 65 74 >>> hostapd_logger: Sending RADIUS message to authentication server >>> RADIUS message: code=1 (Access-Request) identifier=0 length=107 >>> Attribute 1 (User-Name) length=11 >>> Value: 'anmolmeet' >>> Attribute 4 (NAS-IP-Address) length=6 >>> Value: 127.0.0.1 >>> Attribute 31 (Calling-Station-Id) length=19 >>> Value: '00-00-00-00-00-00' >>> Attribute 12 (Framed-MTU) length=6 >>> Value: 1400 >>> Attribute 61 (NAS-Port-Type) length=6 >>> Value: 19 >>> Attribute 77 (Connect-Info) length=5 >>> Value: 'CON' >>> Attribute 79 (EAP-Message) length=16 >>> Value: 02 b3 00 0e 01 61 6e 6d 6f 6c 6d 65 65 74 >>> Attribute 80 (Message-Authenticator) length=18 >>> Value: 01 ab ae c8 e5 2c 36 52 5a aa ae 36 4d 33 84 f2 >>> hostapd_logger: Next RADIUS client retransmit in 3 seconds >>> >>> PANA: DEBUG: Finished txEAP function >>> . >>> PANA: DEBUG: rtxTimerStop function. >>> PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802530665). >>> PANA: DEBUG: Starting to check EAP status (check_eap_status). >>> PANA: DEBUG: Finished EAP check. >>> PANA: DEBUG: PANA message treatment finished. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >>> PANA: DEBUG: Trying a transition... >>> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_EAP_MSG. >>> PANA: DEBUG: sessionTimerStop function. >>> PANA: DEBUG: Session with id 1802530665 not found in the alarm list. >>> PANA: DEBUG: sessionTimerStop finished. >>> PANA: DEBUG: disconnect function. >>> PANA: Entering state: CLOSED (Session ID: 1802530665). >>> ^Z >>> [5]+ Stopped ./openpaa >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> Use "fg" to return to nano. >>> >>> [6]+ Stopped pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >>> root@anmolm-VirtualBox:/home/anmolm/trunk/src# ./openpaa >>> >>> OpenPANA Server - 0.2.4 >>> http://openpana.sf.net >>> >>> Copyright (C) 2011 Pedro Moreno Sánchez and Francisco Vidal Meca >>> This program comes with ABSOLUTELY NO WARRANTY. >>> This is free software, and you are welcome to redistribute it >>> under certain conditions, see COPYING for details. >>> >>> PANA: warning: Loading config.xml from current directory. >>> EAP: Server state machine created >>> PANA: DEBUG: rtxTimerStop function. >>> PANA: DEBUG: There isn't any session associated. >>> hostapd_logger: Authentication server 192.168.0.10:1812 >>> RADIUS local address: 192.168.0.9:48634 >>> PANA: DEBUG: thread '0' as worker manager. >>> PANA: DEBUG: Starting thread '0'. >>> PANA: DEBUG: add_task: added task. >>> PANA: DEBUG: thread '0' tries to get a task. >>> PANA: DEBUG: Trying to get a task.. >>> PANA: warning: Loading config.xml from current directory. >>> *** glibc detected *** ./openpaa: malloc(): memory corruption: 0x093edb28 *** >>> ======= Backtrace: ========= >>> /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2] >>> /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e] >>> /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498] >>> /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c] >>> /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743] >>> /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f] >>> /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee] >>> ./openpaa[0x8054a36] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8054c38] >>> ./openpaa[0x8055327] >>> ./openpaa[0x8049a60] >>> ./openpaa[0x8052437] >>> ./openpaa[0x8052f50] >>> /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31] >>> /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce] >>> ======= Memory map: ======== >>> 00110000-00257000 r-xp 00000000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >>> 00257000-0025b000 r--p 00147000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >>> 0025b000-0025c000 rw-p 0014b000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >>> 0025c000-0025d000 rw-p 00000000 00:00 0 >>> 0025d000-00270000 r-xp 00000000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 00270000-00271000 r--p 00012000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 00271000-00272000 rw-p 00013000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 >>> 002b9000-002e1000 r-xp 00000000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >>> 002e1000-002e2000 r--p 00028000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >>> 002e2000-002e3000 rw-p 00029000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so >>> 00304000-00322000 r-xp 00000000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >>> 00322000-00323000 r--p 0001d000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >>> 00323000-00324000 rw-p 0001e000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so >>> 0035a000-004e7000 r-xp 00000000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004e7000-004f5000 r--p 0018d000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004f5000-004fb000 rw-p 0019b000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 >>> 004fb000-004fe000 rw-p 00000000 00:00 0 >>> 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >>> 00618000-00619000 r--p 00016000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >>> 00619000-0061a000 rw-p 00017000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so >>> 0061a000-0061c000 rw-p 00000000 00:00 0 >>> 0061c000-00792000 r-xp 00000000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >>> 00792000-00794000 r--p 00176000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >>> 00794000-00795000 rw-p 00178000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so >>> 00795000-00798000 rw-p 00000000 00:00 0 >>> 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso] >>> 007bf000-007c2000 r-xp 00000000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >>> 007c2000-007c3000 r--p 00002000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >>> 007c3000-007c4000 rw-p 00003000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so >>> 00e49000-00e65000 r-xp 00000000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >>> 00e65000-00e66000 r--p 0001b000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >>> 00e66000-00e67000 rw-p 0001c000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 >>> 08048000-0809f000 r-xp 00000000 08:01 39668 /home/anmolm/trunk/src/openpaa >>> 0809f000-080a0000 r--p 00056000 08:01 39668 /home/anmolm/trunk/src/openpaa >>> 080a0000-080a1000 rw-p 00057000 08:01 39668 /home/anmolm/trunk/src/openpaa >>> 093de000-093ff000 rw-p 00000000 00:00 0 [heap] >>> b6600000-b6621000 rw-p 00000000 00:00 0 >>> b6621000-b6700000 ---p 00000000 00:00 0 >>> b67ed000-b67ee000 ---p 00000000 00:00 0 >>> b67ee000-b6fee000 rw-p 00000000 00:00 0 >>> b6fee000-b6fef000 ---p 00000000 00:00 0 >>> b6fef000-b77f2000 rw-p 00000000 00:00 0 >>> b7802000-b7805000 rw-p 00000000 00:00 0 >>> bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack] >>> Aborted >>> >>> >>> >>> From: Francisco Vidal Meca <f.v...@um...> >>> To: anmolmeet singh malhi <anm...@ym...> >>> Cc: Pedro Moreno Sánchez <p.m...@um...>; "ope...@li..." <ope...@li...> >>> Sent: Thursday, 27 June 2013, 8:44 >>> Subject: Re: [Openpana-users] openpana implementation >>> >>> Hi Anmolmeet Singh Malhi, >>> >>> With so few details it's difficult to have an idea of what's going on with your "config.xml". >>> >>> Some details about your network set up, where the different entities (PaC, PAA, RADIUS server) are located and the config.xml might help in determine if there is some error in your config.xml, wrong network setup or bugs in the OpenPANA implementation itself. Attaching the config.xml itself might also help. >>> >>> Please take a look at the documentation provided in [1] and compare your config.xml file with the one given by default. There car be some parsing problems such as introducing the IP with a wrong format. >>> >>> Best regards, >>> Francisco Vidal Meca >>> >>> [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/ >>> >>> >>> 2013/6/27 anmolmeet singh malhi <anm...@ym...> >>> hello sorry to interupt you >>> if i use my auth server ip address in config.xml i got memory error somthing like >>> >>> openpaa malloc() memory corruption >>> please help >>> On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez >>> >>>> Hi Anmol. >>>> >>>> Inside the configuration file (config.xml) you have three different sections (PaC, PAA and PRE configuration data). Inside the PAA Configuration Data section, you have the <AUTH_SERVER> subsection, where you can configure the values corresponding to the RADIUS server. In particular, you can configure: >>>> - <IP_VERSION_AUTH> IP version to be used in the communication between the PAA and the RADIUS server >>>> - <AS_IP> IP address in which the RADIUS server will be listening to incoming request >>>> - <AS_PORT> UDP port in which the RADIUS server will be listening to incoming request >>>> - <SHARED_SECRET> Shared secret between the RADIUS server and the RADIUS client (note that the former is included inside the PAA functionality). >>>> >>>> You can find more info about the configuration file and some other questions in the documentation of the OpenPANA's project, under the link: >>>> http://sourceforge.net/projects/openpana/files/docs/ >>>> >>>> Hope it helps, >>>> Pedro. >>>> >>>> >>>> On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...> wrote: >>>> I need help in configuration of config.xml . >>>> what should be the ip address of radius server is that my ip address of PAA ? >>>> please help i am doing research on pana protocol >>>> Thankyou >>>> ------------------------------------------------------------------------------ >>>> This SF.net email is sponsored by Windows: >>>> >>>> Build for Windows Store. >>>> >>>> http://p.sf.net/sfu/windows-dev2dev >>>> _______________________________________________ >>>> Openpana-users mailing list >>>> Ope...@li... >>>> https://lists.sourceforge.net/lists/listinfo/openpana-users >>>> >>>> >>>> >>>> -- >>>> ---------------------------------------------------------------------------- >>>> Pedro Moreno Sánchez - MSc Computer Engineer >>>> Networks and Telematics >>>> Faculty of Computer Science - University of Murcia >>>> 30100 - Murcia - Spain >>>> email: p.m...@um... >>>> ---------------------------------------------------------------------------- >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Openpana-users mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openpana-users >> >> >> >> -- >> ---------------------------------------------------------------------------- >> Pedro Moreno Sánchez - MSc Computer Engineer >> Networks and Telematics >> Faculty of Computer Science - University of Murcia >> 30100 - Murcia - Spain >> email: p.m...@um... >> ---------------------------------------------------------------------------- -- ---------------------------------------------------------------------------- Pedro Moreno Sánchez - MSc Computer Engineer Networks and Telematics Faculty of Computer Science - University of Murcia 30100 - Murcia - Spain email: p.m...@um... ---------------------------------------------------------------------------- |
|
From: Pedro M. S. <p.m...@um...> - 2013-06-28 17:20:46
|
The authenticator in the pass-through EAP mode (e.g. mode which is used in OpenPANA) needs only the RADIUS client. This RADIUS client is already included in the OpenPANA source code so that you do not need any extra RADIUS implementation for that. On the other hand, you need a RADIUS server implementation for the authentication server. As stated in the OpenPANA's manual, we have tested freeradius for that purpose and it correctly works. However, it is not mandatory to use freeradius. You could use any other available RADIUS implementation for this purpose. Hope it helps, Pedro. On 28 June 2013 16:42, anmolmeet singh malhi <anm...@ym...> wrote: > do authenticator need freeradius > > On 27 Jun 2013, at 18:32, Pedro Moreno Sánchez wrote: > > From the log you have reported in the last e-mail I can see that you have > performed the following 3 steps: > 1. You have executed OpenPANA and it has run correctly. The client has > not been authenticated because there is a communication problem between the > PAA and the AS (note that in the log you can see: "PANA: DEBUG: An > AAA_RETRANSMISSION alarm ocurred.". This means that, given that there is > not a correct communication between PAA and AS, the RADIUS client (which > is inside the PAA) is retransmitting the RADIUS message. > > 2. You have opened the config.xml (pico config.xml) and (presumably) you > have changed the configuration values > > 3. You have executed OpenPANA again. In this case you get the malloc() > error when configuration file config.xml is loaded. Thus, I would suggest > you to use the same config.xml file that you used in the first execution > and try to see why there is not communication between the PAA and the AS. > > > On the other hand, I have taken a look at the config.xml file that you > have attached in your last e-mail and I have seen some strange > configuration: > * In the PaC configuration data section, within the User's credentials > you have set up: > <USER>anmolmeet</USER> <!-- User's credential --> > <PASSWORD>775i65gv</PASSWORD> > * In the PAA configuration data section, within the Radius Server > Information you have set up: > <AUTH_SERVER> <!-- Radius Server information --> > <IP_VERSION_AUTH>4</IP_VERSION_AUTH> > <AS_IP>192.168.0.10</AS_IP> > <AS_PORT>1812</AS_PORT> > <SHARED_SECRET>775i65gv</SHARED_SECRET> > </AUTH_SERVER> > > This configuration means that the password used by the user to > authenticate against the authentication server (i.e. in EAP-PSKauthentication method) is the same as the key shared between the RADIUS > client and the RADIUS server. Are you sure that your scenario's keys are > really configured in such a way? > > Hope it helps, > Pedro. > > > On 27 June 2013 10:08, Anmol Malhi <anm...@ym...> wrote: > >> thankyou i attach my config.xml file >> and my network setup is as >> >> i use raspberry pi(192.168.0.8) as my PAC >> i use virtualbox Ubuntu1 (192.168.0.9) as my PAA >> and i use virtualbox ubuntu2(192.168.0.10) as my AS >> >> when i use my AS server ip in my config.xml i got this error >> >> >> Pana Message Name: PANA-Auth >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Reserved:0 | MessageLength: 68 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Flags: ------ | MessageType: 2 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Session Identifier: 0X6B706F69 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Sequence Number: 0XBA16B80 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> AVP Name: EAP-Payload >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Code:2 | AVP Flags:0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Length: 14 | Reserved: 0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Value: EAP-Payload omitted. >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> AVP Name: Nonce >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Code:5 | AVP Flags:0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | AVP Length: 20 | Reserved: 0 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Value: 7E 6B A1 0B B3 C5 6B 7E D7 F7 31 41 AF 43 8F 64 63 >> 5E 21 2D >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> PANA: Received PANA-Auth message. >> PANA: DEBUG: Session updated with message:. >> PANA: DEBUG: PAN. >> PANA: DEBUG: It's been detected a Nonce AVP. >> PANA: DEBUG: Trying a transition... >> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_PAN_OR_PAR. >> PANA: DEBUG: txEAP function. >> EAP: EAP entering state RECEIVED >> EAP: parseEapResp: rxResp=1 respId=179 respMethod=1 respVendor=0 >> respVendorMethod=0 >> EAP: EAP entering state INTEGRITY_CHECK >> EAP: EAP entering state METHOD_RESPONSE >> EAP-Identity: Peer identity - hexdump_ascii(len=9): >> 61 6e 6d 6f 6c 6d 65 65 74 anmolmeet >> EAP: EAP entering state SELECT_ACTION >> EAP: getDecision: -> PASSTHROUGH >> EAP: EAP entering state INITIALIZE_PASSTHROUGH >> EAP: EAP entering state AAA_REQUEST >> EAP: EAP entering state AAA_IDLE >> Encapsulating EAP message into a RADIUS packet >> Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6d 6f >> 6c 6d 65 65 74 >> hostapd_logger: Sending RADIUS message to authentication server >> RADIUS message: code=1 (Access-Request) identifier=0 length=107 >> Attribute 1 (User-Name) length=11 >> Value: 'anmolmeet' >> Attribute 4 (NAS-IP-Address) length=6 >> Value: 127.0.0.1 >> Attribute 31 (Calling-Station-Id) length=19 >> Value: '00-00-00-00-00-00' >> Attribute 12 (Framed-MTU) length=6 >> Value: 1400 >> Attribute 61 (NAS-Port-Type) length=6 >> Value: 19 >> Attribute 77 (Connect-Info) length=5 >> Value: 'CON' >> Attribute 79 (EAP-Message) length=16 >> Value: 02 b3 00 0e 01 61 6e 6d 6f 6c 6d 65 65 74 >> Attribute 80 (Message-Authenticator) length=18 >> Value: 01 ab ae c8 e5 2c 36 52 5a aa ae 36 4d 33 84 f2 >> hostapd_logger: Next RADIUS client retransmit in 3 seconds >> >> PANA: DEBUG: Finished txEAP function >> . >> PANA: DEBUG: rtxTimerStop function. >> PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802530665). >> PANA: DEBUG: Starting to check EAP status (check_eap_status). >> PANA: DEBUG: Finished EAP check. >> PANA: DEBUG: PANA message treatment finished. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. >> PANA: DEBUG: Trying a transition... >> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_EAP_MSG. >> PANA: DEBUG: sessionTimerStop function. >> PANA: DEBUG: Session with id 1802530665 not found in the alarm list. >> PANA: DEBUG: sessionTimerStop finished. >> PANA: DEBUG: disconnect function. >> PANA: Entering state: CLOSED (Session ID: 1802530665). >> ^Z >> [5]+ Stopped ./openpaa >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >> Use "fg" to return to nano. >> >> [6]+ Stopped pico config.xml >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml >> root@anmolm-VirtualBox:/home/anmolm/trunk/src# ./openpaa >> >> OpenPANA Server - 0.2.4 >> http://openpana.sf.net >> >> Copyright (C) 2011 Pedro Moreno Sánchez and Francisco Vidal Meca >> This program comes with ABSOLUTELY NO WARRANTY. >> This is free software, and you are welcome to redistribute it >> under certain conditions, see COPYING for details. >> >> PANA: warning: Loading config.xml from current directory. >> EAP: Server state machine created >> PANA: DEBUG: rtxTimerStop function. >> PANA: DEBUG: There isn't any session associated. >> hostapd_logger: Authentication server 192.168.0.10:1812 >> RADIUS local address: 192.168.0.9:48634 >> PANA: DEBUG: thread '0' as worker manager. >> PANA: DEBUG: Starting thread '0'. >> PANA: DEBUG: add_task: added task. >> PANA: DEBUG: thread '0' tries to get a task. >> PANA: DEBUG: Trying to get a task.. >> PANA: warning: Loading config.xml from current directory. >> *** glibc detected *** ./openpaa: malloc(): memory corruption: 0x093edb28 >> *** >> ======= Backtrace: ========= >> /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2] >> /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e] >> /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498] >> /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c] >> /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743] >> /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f] >> /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee] >> ./openpaa[0x8054a36] >> ./openpaa[0x8054c38] >> ./openpaa[0x8054c38] >> ./openpaa[0x8054c38] >> ./openpaa[0x8055327] >> ./openpaa[0x8049a60] >> ./openpaa[0x8052437] >> ./openpaa[0x8052f50] >> /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31] >> /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce] >> ======= Memory map: ======== >> 00110000-00257000 r-xp 00000000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >> 00257000-0025b000 r--p 00147000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >> 0025b000-0025c000 rw-p 0014b000 08:01 297593 /usr/lib/libxml2.so.2.7.8 >> 0025c000-0025d000 rw-p 00000000 00:00 0 >> 0025d000-00270000 r-xp 00000000 08:01 134695 >> /lib/i386-linux-gnu/libz.so.1.2.3.4 >> 00270000-00271000 r--p 00012000 08:01 134695 >> /lib/i386-linux-gnu/libz.so.1.2.3.4 >> 00271000-00272000 rw-p 00013000 08:01 134695 >> /lib/i386-linux-gnu/libz.so.1.2.3.4 >> 002b9000-002e1000 r-xp 00000000 08:01 134642 /lib/i386-linux-gnu/ >> libm-2.13.so >> 002e1000-002e2000 r--p 00028000 08:01 134642 /lib/i386-linux-gnu/ >> libm-2.13.so >> 002e2000-002e3000 rw-p 00029000 08:01 134642 /lib/i386-linux-gnu/ >> libm-2.13.so >> 00304000-00322000 r-xp 00000000 08:01 134599 /lib/i386-linux-gnu/ >> ld-2.13.so >> 00322000-00323000 r--p 0001d000 08:01 134599 /lib/i386-linux-gnu/ >> ld-2.13.so >> 00323000-00324000 rw-p 0001e000 08:01 134599 /lib/i386-linux-gnu/ >> ld-2.13.so >> 0035a000-004e7000 r-xp 00000000 08:01 139154 >> /lib/i386-linux-gnu/libcrypto.so.1.0.0 >> 004e7000-004f5000 r--p 0018d000 08:01 139154 >> /lib/i386-linux-gnu/libcrypto.so.1.0.0 >> 004f5000-004fb000 rw-p 0019b000 08:01 139154 >> /lib/i386-linux-gnu/libcrypto.so.1.0.0 >> 004fb000-004fe000 rw-p 00000000 00:00 0 >> 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386-linux-gnu/ >> libpthread-2.13.so >> 00618000-00619000 r--p 00016000 08:01 134672 /lib/i386-linux-gnu/ >> libpthread-2.13.so >> 00619000-0061a000 rw-p 00017000 08:01 134672 /lib/i386-linux-gnu/ >> libpthread-2.13.so >> 0061a000-0061c000 rw-p 00000000 00:00 0 >> 0061c000-00792000 r-xp 00000000 08:01 134612 /lib/i386-linux-gnu/ >> libc-2.13.so >> 00792000-00794000 r--p 00176000 08:01 134612 /lib/i386-linux-gnu/ >> libc-2.13.so >> 00794000-00795000 rw-p 00178000 08:01 134612 /lib/i386-linux-gnu/ >> libc-2.13.so >> 00795000-00798000 rw-p 00000000 00:00 0 >> 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso] >> 007bf000-007c2000 r-xp 00000000 08:01 134623 /lib/i386-linux-gnu/ >> libdl-2.13.so >> 007c2000-007c3000 r--p 00002000 08:01 134623 /lib/i386-linux-gnu/ >> libdl-2.13.so >> 007c3000-007c4000 rw-p 00003000 08:01 134623 /lib/i386-linux-gnu/ >> libdl-2.13.so >> 00e49000-00e65000 r-xp 00000000 08:01 134633 >> /lib/i386-linux-gnu/libgcc_s.so.1 >> 00e65000-00e66000 r--p 0001b000 08:01 134633 >> /lib/i386-linux-gnu/libgcc_s.so.1 >> 00e66000-00e67000 rw-p 0001c000 08:01 134633 >> /lib/i386-linux-gnu/libgcc_s.so.1 >> 08048000-0809f000 r-xp 00000000 08:01 39668 >> /home/anmolm/trunk/src/openpaa >> 0809f000-080a0000 r--p 00056000 08:01 39668 >> /home/anmolm/trunk/src/openpaa >> 080a0000-080a1000 rw-p 00057000 08:01 39668 >> /home/anmolm/trunk/src/openpaa >> 093de000-093ff000 rw-p 00000000 00:00 0 [heap] >> b6600000-b6621000 rw-p 00000000 00:00 0 >> b6621000-b6700000 ---p 00000000 00:00 0 >> b67ed000-b67ee000 ---p 00000000 00:00 0 >> b67ee000-b6fee000 rw-p 00000000 00:00 0 >> b6fee000-b6fef000 ---p 00000000 00:00 0 >> b6fef000-b77f2000 rw-p 00000000 00:00 0 >> b7802000-b7805000 rw-p 00000000 00:00 0 >> bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack] >> Aborted >> >> >> >> ------------------------------ >> *From:* Francisco Vidal Meca <f.v...@um...> >> *To:* anmolmeet singh malhi <anm...@ym...> >> *Cc:* Pedro Moreno Sánchez <p.m...@um...>; " >> ope...@li..." < >> ope...@li...> >> *Sent:* Thursday, 27 June 2013, 8:44 >> *Subject:* Re: [Openpana-users] openpana implementation >> >> Hi Anmolmeet Singh Malhi, >> >> With so few details it's difficult to have an idea of what's going on >> with your "config.xml". >> >> Some details about your network set up, where the different entities >> (PaC, PAA, RADIUS server) are located and the config.xml might help in >> determine if there is some error in your config.xml, wrong network setup or >> bugs in the OpenPANA implementation itself. Attaching the config.xml itself >> might also help. >> >> Please take a look at the documentation provided in [1] and compare your >> config.xml file with the one given by default. There car be some parsing >> problems such as introducing the IP with a wrong format. >> >> Best regards, >> Francisco Vidal Meca >> >> [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/ >> >> >> 2013/6/27 anmolmeet singh malhi <anm...@ym...> >> >> hello sorry to interupt you >> if i use my auth server ip address in config.xml i got memory error >> somthing like >> >> openpaa malloc() memory corruption >> please help >> On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez >> >> Hi Anmol. >> >> Inside the configuration file (config.xml) you have three different >> sections (PaC, PAA and PRE configuration data). Inside the PAAConfiguration Data section, you have the < >> AUTH_SERVER> subsection, where you can configure the values >> corresponding to the RADIUS server. In particular, you can configure: >> - <IP_VERSION_AUTH> IP version to be used in the communication between >> the PAA and the RADIUS server >> - <AS_IP> IP address in which the RADIUS server will be listening to >> incoming request >> - <AS_PORT> UDP port in which the RADIUS server will be listening to >> incoming request >> - <SHARED_SECRET> Shared secret between the RADIUS server and the >> RADIUS client (note that the former is included inside the PAAfunctionality). >> >> You can find more info about the configuration file and some other >> questions in the documentation of the OpenPANA's project, under the link: >> http://sourceforge.net/projects/openpana/files/docs/ >> >> Hope it helps, >> Pedro. >> >> >> On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...>wrote: >> >> I need help in configuration of config.xml . >> what should be the ip address of radius server is that my ip address of >> PAA ? >> please help i am doing research on pana protocol >> Thankyou >> >> ------------------------------------------------------------------------------ >> This SF.net <http://sf.net/> email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Openpana-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openpana-users >> >> >> >> >> -- >> >> ---------------------------------------------------------------------------- >> Pedro Moreno Sánchez - MSc Computer Engineer >> Networks and Telematics >> Faculty of Computer Science - University of Murcia >> 30100 - Murcia - Spain >> email: p.m...@um... >> >> ---------------------------------------------------------------------------- >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Openpana-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openpana-users >> >> >> >> >> > > > -- > > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > > ---------------------------------------------------------------------------- > > > > > > > -- ---------------------------------------------------------------------------- Pedro Moreno Sánchez - MSc Computer Engineer Networks and Telematics Faculty of Computer Science - University of Murcia 30100 - Murcia - Spain email: p.m...@um... ---------------------------------------------------------------------------- |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-06-28 14:42:46
|
do authenticator need freeradius On 27 Jun 2013, at 18:32, Pedro Moreno Sánchez wrote: > From the log you have reported in the last e-mail I can see that you have performed the following 3 steps: > 1. You have executed OpenPANA and it has run correctly. The client has not been authenticated because there is a communication problem between the PAA and the AS (note that in the log you can see: "PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.". This means that, given that there is not a correct communication between PAA and AS, the RADIUS client (which is inside the PAA) is retransmitting the RADIUS message. > > 2. You have opened the config.xml (pico config.xml) and (presumably) you have changed the configuration values > > 3. You have executed OpenPANA again. In this case you get the malloc() error when configuration file config.xml is loaded. Thus, I would suggest you to use the same config.xml file that you used in the first execution and try to see why there is not communication between the PAA and the AS. > > > On the other hand, I have taken a look at the config.xml file that you have attached in your last e-mail and I have seen some strange configuration: > * In the PaC configuration data section, within the User's credentials you have set up: > <USER>anmolmeet</USER> <!-- User's credential --> > <PASSWORD>775i65gv</PASSWORD> > * In the PAA configuration data section, within the Radius Server Information you have set up: > <AUTH_SERVER> <!-- Radius Server information --> > <IP_VERSION_AUTH>4</IP_VERSION_AUTH> > <AS_IP>192.168.0.10</AS_IP> > <AS_PORT>1812</AS_PORT> > <SHARED_SECRET>775i65gv</SHARED_SECRET> > </AUTH_SERVER> > > This configuration means that the password used by the user to authenticate against the authentication server (i.e. in EAP-PSK authentication method) is the same as the key shared between the RADIUS client and the RADIUS server. Are you sure that your scenario's keys are really configured in such a way? > > Hope it helps, > Pedro. > > > On 27 June 2013 10:08, Anmol Malhi <anm...@ym...> wrote: > thankyou i attach my config.xml file > and my network setup is as > > i use raspberry pi(192.168.0.8) as my PAC > i use virtualbox Ubuntu1 (192.168.0.9) as my PAA > and i use virtualbox ubuntu2(192.168.0.10) as my AS > > when i use my AS server ip in my config.xml i got this error > > > Pana Message Name: PANA-Auth > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Reserved:0 | MessageLength: 68 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Flags: ------ | MessageType: 2 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Session Identifier: 0X6B706F69 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Sequence Number: 0XBA16B80 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > AVP Name: EAP-Payload > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AVP Code:2 | AVP Flags:0 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AVP Length: 14 | Reserved: 0 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Value: EAP-Payload omitted. > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > AVP Name: Nonce > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AVP Code:5 | AVP Flags:0 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AVP Length: 20 | Reserved: 0 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Value: 7E 6B A1 0B B3 C5 6B 7E D7 F7 31 41 AF 43 8F 64 63 > 5E 21 2D > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > PANA: Received PANA-Auth message. > PANA: DEBUG: Session updated with message:. > PANA: DEBUG: PAN. > PANA: DEBUG: It's been detected a Nonce AVP. > PANA: DEBUG: Trying a transition... > PANA: DEBUG: Session ID: 1802530665, current state: WAIT_PAN_OR_PAR. > PANA: DEBUG: txEAP function. > EAP: EAP entering state RECEIVED > EAP: parseEapResp: rxResp=1 respId=179 respMethod=1 respVendor=0 respVendorMethod=0 > EAP: EAP entering state INTEGRITY_CHECK > EAP: EAP entering state METHOD_RESPONSE > EAP-Identity: Peer identity - hexdump_ascii(len=9): > 61 6e 6d 6f 6c 6d 65 65 74 anmolmeet > EAP: EAP entering state SELECT_ACTION > EAP: getDecision: -> PASSTHROUGH > EAP: EAP entering state INITIALIZE_PASSTHROUGH > EAP: EAP entering state AAA_REQUEST > EAP: EAP entering state AAA_IDLE > Encapsulating EAP message into a RADIUS packet > Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6d 6f 6c 6d 65 65 74 > hostapd_logger: Sending RADIUS message to authentication server > RADIUS message: code=1 (Access-Request) identifier=0 length=107 > Attribute 1 (User-Name) length=11 > Value: 'anmolmeet' > Attribute 4 (NAS-IP-Address) length=6 > Value: 127.0.0.1 > Attribute 31 (Calling-Station-Id) length=19 > Value: '00-00-00-00-00-00' > Attribute 12 (Framed-MTU) length=6 > Value: 1400 > Attribute 61 (NAS-Port-Type) length=6 > Value: 19 > Attribute 77 (Connect-Info) length=5 > Value: 'CON' > Attribute 79 (EAP-Message) length=16 > Value: 02 b3 00 0e 01 61 6e 6d 6f 6c 6d 65 65 74 > Attribute 80 (Message-Authenticator) length=18 > Value: 01 ab ae c8 e5 2c 36 52 5a aa ae 36 4d 33 84 f2 > hostapd_logger: Next RADIUS client retransmit in 3 seconds > > PANA: DEBUG: Finished txEAP function > . > PANA: DEBUG: rtxTimerStop function. > PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802530665). > PANA: DEBUG: Starting to check EAP status (check_eap_status). > PANA: DEBUG: Finished EAP check. > PANA: DEBUG: PANA message treatment finished. > PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. > PANA: DEBUG: add_task: added task. > PANA: DEBUG: thread '0' tries to get a task. > PANA: DEBUG: Trying to get a task.. > PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. > PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. > PANA: DEBUG: add_task: added task. > PANA: DEBUG: thread '0' tries to get a task. > PANA: DEBUG: Trying to get a task.. > PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. > PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. > PANA: DEBUG: add_task: added task. > PANA: DEBUG: thread '0' tries to get a task. > PANA: DEBUG: Trying to get a task.. > PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred. > PANA: DEBUG: Trying a transition... > PANA: DEBUG: Session ID: 1802530665, current state: WAIT_EAP_MSG. > PANA: DEBUG: sessionTimerStop function. > PANA: DEBUG: Session with id 1802530665 not found in the alarm list. > PANA: DEBUG: sessionTimerStop finished. > PANA: DEBUG: disconnect function. > PANA: Entering state: CLOSED (Session ID: 1802530665). > ^Z > [5]+ Stopped ./openpaa > root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml > root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml > Use "fg" to return to nano. > > [6]+ Stopped pico config.xml > root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml > root@anmolm-VirtualBox:/home/anmolm/trunk/src# ./openpaa > > OpenPANA Server - 0.2.4 > http://openpana.sf.net > > Copyright (C) 2011 Pedro Moreno Sánchez and Francisco Vidal Meca > This program comes with ABSOLUTELY NO WARRANTY. > This is free software, and you are welcome to redistribute it > under certain conditions, see COPYING for details. > > PANA: warning: Loading config.xml from current directory. > EAP: Server state machine created > PANA: DEBUG: rtxTimerStop function. > PANA: DEBUG: There isn't any session associated. > hostapd_logger: Authentication server 192.168.0.10:1812 > RADIUS local address: 192.168.0.9:48634 > PANA: DEBUG: thread '0' as worker manager. > PANA: DEBUG: Starting thread '0'. > PANA: DEBUG: add_task: added task. > PANA: DEBUG: thread '0' tries to get a task. > PANA: DEBUG: Trying to get a task.. > PANA: warning: Loading config.xml from current directory. > *** glibc detected *** ./openpaa: malloc(): memory corruption: 0x093edb28 *** > ======= Backtrace: ========= > /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2] > /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e] > /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498] > /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c] > /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743] > /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f] > /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee] > ./openpaa[0x8054a36] > ./openpaa[0x8054c38] > ./openpaa[0x8054c38] > ./openpaa[0x8054c38] > ./openpaa[0x8055327] > ./openpaa[0x8049a60] > ./openpaa[0x8052437] > ./openpaa[0x8052f50] > /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31] > /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce] > ======= Memory map: ======== > 00110000-00257000 r-xp 00000000 08:01 297593 /usr/lib/libxml2.so.2.7.8 > 00257000-0025b000 r--p 00147000 08:01 297593 /usr/lib/libxml2.so.2.7.8 > 0025b000-0025c000 rw-p 0014b000 08:01 297593 /usr/lib/libxml2.so.2.7.8 > 0025c000-0025d000 rw-p 00000000 00:00 0 > 0025d000-00270000 r-xp 00000000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 > 00270000-00271000 r--p 00012000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 > 00271000-00272000 rw-p 00013000 08:01 134695 /lib/i386-linux-gnu/libz.so.1.2.3.4 > 002b9000-002e1000 r-xp 00000000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so > 002e1000-002e2000 r--p 00028000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so > 002e2000-002e3000 rw-p 00029000 08:01 134642 /lib/i386-linux-gnu/libm-2.13.so > 00304000-00322000 r-xp 00000000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so > 00322000-00323000 r--p 0001d000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so > 00323000-00324000 rw-p 0001e000 08:01 134599 /lib/i386-linux-gnu/ld-2.13.so > 0035a000-004e7000 r-xp 00000000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 > 004e7000-004f5000 r--p 0018d000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 > 004f5000-004fb000 rw-p 0019b000 08:01 139154 /lib/i386-linux-gnu/libcrypto.so.1.0.0 > 004fb000-004fe000 rw-p 00000000 00:00 0 > 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so > 00618000-00619000 r--p 00016000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so > 00619000-0061a000 rw-p 00017000 08:01 134672 /lib/i386-linux-gnu/libpthread-2.13.so > 0061a000-0061c000 rw-p 00000000 00:00 0 > 0061c000-00792000 r-xp 00000000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so > 00792000-00794000 r--p 00176000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so > 00794000-00795000 rw-p 00178000 08:01 134612 /lib/i386-linux-gnu/libc-2.13.so > 00795000-00798000 rw-p 00000000 00:00 0 > 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso] > 007bf000-007c2000 r-xp 00000000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so > 007c2000-007c3000 r--p 00002000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so > 007c3000-007c4000 rw-p 00003000 08:01 134623 /lib/i386-linux-gnu/libdl-2.13.so > 00e49000-00e65000 r-xp 00000000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 > 00e65000-00e66000 r--p 0001b000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 > 00e66000-00e67000 rw-p 0001c000 08:01 134633 /lib/i386-linux-gnu/libgcc_s.so.1 > 08048000-0809f000 r-xp 00000000 08:01 39668 /home/anmolm/trunk/src/openpaa > 0809f000-080a0000 r--p 00056000 08:01 39668 /home/anmolm/trunk/src/openpaa > 080a0000-080a1000 rw-p 00057000 08:01 39668 /home/anmolm/trunk/src/openpaa > 093de000-093ff000 rw-p 00000000 00:00 0 [heap] > b6600000-b6621000 rw-p 00000000 00:00 0 > b6621000-b6700000 ---p 00000000 00:00 0 > b67ed000-b67ee000 ---p 00000000 00:00 0 > b67ee000-b6fee000 rw-p 00000000 00:00 0 > b6fee000-b6fef000 ---p 00000000 00:00 0 > b6fef000-b77f2000 rw-p 00000000 00:00 0 > b7802000-b7805000 rw-p 00000000 00:00 0 > bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack] > Aborted > > > > From: Francisco Vidal Meca <f.v...@um...> > To: anmolmeet singh malhi <anm...@ym...> > Cc: Pedro Moreno Sánchez <p.m...@um...>; "ope...@li..." <ope...@li...> > Sent: Thursday, 27 June 2013, 8:44 > Subject: Re: [Openpana-users] openpana implementation > > Hi Anmolmeet Singh Malhi, > > With so few details it's difficult to have an idea of what's going on with your "config.xml". > > Some details about your network set up, where the different entities (PaC, PAA, RADIUS server) are located and the config.xml might help in determine if there is some error in your config.xml, wrong network setup or bugs in the OpenPANA implementation itself. Attaching the config.xml itself might also help. > > Please take a look at the documentation provided in [1] and compare your config.xml file with the one given by default. There car be some parsing problems such as introducing the IP with a wrong format. > > Best regards, > Francisco Vidal Meca > > [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/ > > > 2013/6/27 anmolmeet singh malhi <anm...@ym...> > hello sorry to interupt you > if i use my auth server ip address in config.xml i got memory error somthing like > > openpaa malloc() memory corruption > please help > On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez > >> Hi Anmol. >> >> Inside the configuration file (config.xml) you have three different sections (PaC, PAA and PRE configuration data). Inside the PAA Configuration Data section, you have the <AUTH_SERVER> subsection, where you can configure the values corresponding to the RADIUS server. In particular, you can configure: >> - <IP_VERSION_AUTH> IP version to be used in the communication between the PAA and the RADIUS server >> - <AS_IP> IP address in which the RADIUS server will be listening to incoming request >> - <AS_PORT> UDP port in which the RADIUS server will be listening to incoming request >> - <SHARED_SECRET> Shared secret between the RADIUS server and the RADIUS client (note that the former is included inside the PAA functionality). >> >> You can find more info about the configuration file and some other questions in the documentation of the OpenPANA's project, under the link: >> http://sourceforge.net/projects/openpana/files/docs/ >> >> Hope it helps, >> Pedro. >> >> >> On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...> wrote: >> I need help in configuration of config.xml . >> what should be the ip address of radius server is that my ip address of PAA ? >> please help i am doing research on pana protocol >> Thankyou >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Openpana-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openpana-users >> >> >> >> -- >> ---------------------------------------------------------------------------- >> Pedro Moreno Sánchez - MSc Computer Engineer >> Networks and Telematics >> Faculty of Computer Science - University of Murcia >> 30100 - Murcia - Spain >> email: p.m...@um... >> ---------------------------------------------------------------------------- >> >> >> >> >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Openpana-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openpana-users > > > > > > > > -- > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > ---------------------------------------------------------------------------- > > > > > |
|
From: Pedro M. S. <p.m...@um...> - 2013-06-27 17:33:13
|
>From the log you have reported in the last e-mail I can see that you have
performed the following 3 steps:
1. You have executed OpenPANA and it has run correctly. The client has not
been authenticated because there is a communication problem between
the PAAand the AS (note that in the log you can see: "
PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.". This means that, given
that there is not a correct communication between PAA and AS, the RADIUS
client (which is inside the PAA) is retransmitting the RADIUS message.
2. You have opened the config.xml (pico config.xml) and (presumably) you
have changed the configuration values
3. You have executed OpenPANA again. In this case you get the malloc()
error when configuration file config.xml is loaded. Thus, I would suggest
you to use the same config.xml file that you used in the first execution
and try to see why there is not communication between the PAA and the AS.
On the other hand, I have taken a look at the config.xml file that you have
attached in your last e-mail and I have seen some strange configuration:
* In the PaC configuration data section, within the User's credentials you
have set up:
<USER>anmolmeet</USER> <!-- User's credential -->
<PASSWORD>775i65gv</PASSWORD>
* In the PAA configuration data section, within the Radius Server
Information you have set up:
<AUTH_SERVER> <!-- Radius Server information -->
<IP_VERSION_AUTH>4</IP_VERSION_AUTH>
<AS_IP>192.168.0.10</AS_IP>
<AS_PORT>1812</AS_PORT>
<SHARED_SECRET>775i65gv</SHARED_SECRET>
</AUTH_SERVER>
This configuration means that the password used by the user to authenticate
against the authentication server (i.e. in EAP-PSK authentication method)
is the same as the key shared between the RADIUS client and the RADIUS
server. Are you sure that your scenario's keys are really configured in
such a way?
Hope it helps,
Pedro.
On 27 June 2013 10:08, Anmol Malhi <anm...@ym...> wrote:
> thankyou i attach my config.xml file
> and my network setup is as
>
> i use raspberry pi(192.168.0.8) as my PAC
> i use virtualbox Ubuntu1 (192.168.0.9) as my PAA
> and i use virtualbox ubuntu2(192.168.0.10) as my AS
>
> when i use my AS server ip in my config.xml i got this error
>
>
> Pana Message Name: PANA-Auth
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Reserved:0 | MessageLength: 68 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Flags: ------ | MessageType: 2 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Session Identifier: 0X6B706F69 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Sequence Number: 0XBA16B80 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> AVP Name: EAP-Payload
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | AVP Code:2 | AVP Flags:0 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | AVP Length: 14 | Reserved: 0 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Value: EAP-Payload omitted.
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> AVP Name: Nonce
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | AVP Code:5 | AVP Flags:0 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | AVP Length: 20 | Reserved: 0 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Value: 7E 6B A1 0B B3 C5 6B 7E D7 F7 31 41 AF 43 8F 64 63
> 5E 21 2D
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> PANA: Received PANA-Auth message.
> PANA: DEBUG: Session updated with message:.
> PANA: DEBUG: PAN.
> PANA: DEBUG: It's been detected a Nonce AVP.
> PANA: DEBUG: Trying a transition...
> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_PAN_OR_PAR.
> PANA: DEBUG: txEAP function.
> EAP: EAP entering state RECEIVED
> EAP: parseEapResp: rxResp=1 respId=179 respMethod=1 respVendor=0
> respVendorMethod=0
> EAP: EAP entering state INTEGRITY_CHECK
> EAP: EAP entering state METHOD_RESPONSE
> EAP-Identity: Peer identity - hexdump_ascii(len=9):
> 61 6e 6d 6f 6c 6d 65 65 74 anmolmeet
> EAP: EAP entering state SELECT_ACTION
> EAP: getDecision: -> PASSTHROUGH
> EAP: EAP entering state INITIALIZE_PASSTHROUGH
> EAP: EAP entering state AAA_REQUEST
> EAP: EAP entering state AAA_IDLE
> Encapsulating EAP message into a RADIUS packet
> Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6d 6f
> 6c 6d 65 65 74
> hostapd_logger: Sending RADIUS message to authentication server
> RADIUS message: code=1 (Access-Request) identifier=0 length=107
> Attribute 1 (User-Name) length=11
> Value: 'anmolmeet'
> Attribute 4 (NAS-IP-Address) length=6
> Value: 127.0.0.1
> Attribute 31 (Calling-Station-Id) length=19
> Value: '00-00-00-00-00-00'
> Attribute 12 (Framed-MTU) length=6
> Value: 1400
> Attribute 61 (NAS-Port-Type) length=6
> Value: 19
> Attribute 77 (Connect-Info) length=5
> Value: 'CON'
> Attribute 79 (EAP-Message) length=16
> Value: 02 b3 00 0e 01 61 6e 6d 6f 6c 6d 65 65 74
> Attribute 80 (Message-Authenticator) length=18
> Value: 01 ab ae c8 e5 2c 36 52 5a aa ae 36 4d 33 84 f2
> hostapd_logger: Next RADIUS client retransmit in 3 seconds
>
> PANA: DEBUG: Finished txEAP function
> .
> PANA: DEBUG: rtxTimerStop function.
> PANA: Entering state: WAIT_EAP_MSG (Session ID: 1802530665).
> PANA: DEBUG: Starting to check EAP status (check_eap_status).
> PANA: DEBUG: Finished EAP check.
> PANA: DEBUG: PANA message treatment finished.
> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.
> PANA: DEBUG: add_task: added task.
> PANA: DEBUG: thread '0' tries to get a task.
> PANA: DEBUG: Trying to get a task..
> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.
> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.
> PANA: DEBUG: add_task: added task.
> PANA: DEBUG: thread '0' tries to get a task.
> PANA: DEBUG: Trying to get a task..
> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.
> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.
> PANA: DEBUG: add_task: added task.
> PANA: DEBUG: thread '0' tries to get a task.
> PANA: DEBUG: Trying to get a task..
> PANA: DEBUG: An AAA_RETRANSMISSION alarm ocurred.
> PANA: DEBUG: Trying a transition...
> PANA: DEBUG: Session ID: 1802530665, current state: WAIT_EAP_MSG.
> PANA: DEBUG: sessionTimerStop function.
> PANA: DEBUG: Session with id 1802530665 not found in the alarm list.
> PANA: DEBUG: sessionTimerStop finished.
> PANA: DEBUG: disconnect function.
> PANA: Entering state: CLOSED (Session ID: 1802530665).
> ^Z
> [5]+ Stopped ./openpaa
> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml
> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml
> Use "fg" to return to nano.
>
> [6]+ Stopped pico config.xml
> root@anmolm-VirtualBox:/home/anmolm/trunk/src# pico config.xml
> root@anmolm-VirtualBox:/home/anmolm/trunk/src# ./openpaa
>
> OpenPANA Server - 0.2.4
> http://openpana.sf.net
>
> Copyright (C) 2011 Pedro Moreno Sánchez and Francisco Vidal Meca
> This program comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions, see COPYING for details.
>
> PANA: warning: Loading config.xml from current directory.
> EAP: Server state machine created
> PANA: DEBUG: rtxTimerStop function.
> PANA: DEBUG: There isn't any session associated.
> hostapd_logger: Authentication server 192.168.0.10:1812
> RADIUS local address: 192.168.0.9:48634
> PANA: DEBUG: thread '0' as worker manager.
> PANA: DEBUG: Starting thread '0'.
> PANA: DEBUG: add_task: added task.
> PANA: DEBUG: thread '0' tries to get a task.
> PANA: DEBUG: Trying to get a task..
> PANA: warning: Loading config.xml from current directory.
> *** glibc detected *** ./openpaa: malloc(): memory corruption: 0x093edb28
> ***
> ======= Backtrace: =========
> /lib/i386-linux-gnu/libc.so.6(+0x6ebc2)[0x68abc2]
> /lib/i386-linux-gnu/libc.so.6(+0x7055e)[0x68c55e]
> /lib/i386-linux-gnu/libc.so.6(__libc_malloc+0x68)[0x68e498]
> /usr/lib/libxml2.so.2(xmlGetGlobalState+0x7c)[0x1aa43c]
> /usr/lib/libxml2.so.2(__xmlBufferAllocScheme+0x23)[0x1a9743]
> /usr/lib/libxml2.so.2(xmlBufferCreateSize+0x3f)[0x15916f]
> /usr/lib/libxml2.so.2(xmlNodeGetContent+0x10e)[0x159cee]
> ./openpaa[0x8054a36]
> ./openpaa[0x8054c38]
> ./openpaa[0x8054c38]
> ./openpaa[0x8054c38]
> ./openpaa[0x8055327]
> ./openpaa[0x8049a60]
> ./openpaa[0x8052437]
> ./openpaa[0x8052f50]
> /lib/i386-linux-gnu/libpthread.so.0(+0x6d31)[0x607d31]
> /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x6ee0ce]
> ======= Memory map: ========
> 00110000-00257000 r-xp 00000000 08:01 297593 /usr/lib/libxml2.so.2.7.8
> 00257000-0025b000 r--p 00147000 08:01 297593 /usr/lib/libxml2.so.2.7.8
> 0025b000-0025c000 rw-p 0014b000 08:01 297593 /usr/lib/libxml2.so.2.7.8
> 0025c000-0025d000 rw-p 00000000 00:00 0
> 0025d000-00270000 r-xp 00000000 08:01 134695
> /lib/i386-linux-gnu/libz.so.1.2.3.4
> 00270000-00271000 r--p 00012000 08:01 134695
> /lib/i386-linux-gnu/libz.so.1.2.3.4
> 00271000-00272000 rw-p 00013000 08:01 134695
> /lib/i386-linux-gnu/libz.so.1.2.3.4
> 002b9000-002e1000 r-xp 00000000 08:01 134642 /lib/i386-linux-gnu/
> libm-2.13.so
> 002e1000-002e2000 r--p 00028000 08:01 134642 /lib/i386-linux-gnu/
> libm-2.13.so
> 002e2000-002e3000 rw-p 00029000 08:01 134642 /lib/i386-linux-gnu/
> libm-2.13.so
> 00304000-00322000 r-xp 00000000 08:01 134599 /lib/i386-linux-gnu/
> ld-2.13.so
> 00322000-00323000 r--p 0001d000 08:01 134599 /lib/i386-linux-gnu/
> ld-2.13.so
> 00323000-00324000 rw-p 0001e000 08:01 134599 /lib/i386-linux-gnu/
> ld-2.13.so
> 0035a000-004e7000 r-xp 00000000 08:01 139154
> /lib/i386-linux-gnu/libcrypto.so.1.0.0
> 004e7000-004f5000 r--p 0018d000 08:01 139154
> /lib/i386-linux-gnu/libcrypto.so.1.0.0
> 004f5000-004fb000 rw-p 0019b000 08:01 139154
> /lib/i386-linux-gnu/libcrypto.so.1.0.0
> 004fb000-004fe000 rw-p 00000000 00:00 0
> 00601000-00618000 r-xp 00000000 08:01 134672 /lib/i386-linux-gnu/
> libpthread-2.13.so
> 00618000-00619000 r--p 00016000 08:01 134672 /lib/i386-linux-gnu/
> libpthread-2.13.so
> 00619000-0061a000 rw-p 00017000 08:01 134672 /lib/i386-linux-gnu/
> libpthread-2.13.so
> 0061a000-0061c000 rw-p 00000000 00:00 0
> 0061c000-00792000 r-xp 00000000 08:01 134612 /lib/i386-linux-gnu/
> libc-2.13.so
> 00792000-00794000 r--p 00176000 08:01 134612 /lib/i386-linux-gnu/
> libc-2.13.so
> 00794000-00795000 rw-p 00178000 08:01 134612 /lib/i386-linux-gnu/
> libc-2.13.so
> 00795000-00798000 rw-p 00000000 00:00 0
> 007bc000-007bd000 r-xp 00000000 00:00 0 [vdso]
> 007bf000-007c2000 r-xp 00000000 08:01 134623 /lib/i386-linux-gnu/
> libdl-2.13.so
> 007c2000-007c3000 r--p 00002000 08:01 134623 /lib/i386-linux-gnu/
> libdl-2.13.so
> 007c3000-007c4000 rw-p 00003000 08:01 134623 /lib/i386-linux-gnu/
> libdl-2.13.so
> 00e49000-00e65000 r-xp 00000000 08:01 134633
> /lib/i386-linux-gnu/libgcc_s.so.1
> 00e65000-00e66000 r--p 0001b000 08:01 134633
> /lib/i386-linux-gnu/libgcc_s.so.1
> 00e66000-00e67000 rw-p 0001c000 08:01 134633
> /lib/i386-linux-gnu/libgcc_s.so.1
> 08048000-0809f000 r-xp 00000000 08:01 39668
> /home/anmolm/trunk/src/openpaa
> 0809f000-080a0000 r--p 00056000 08:01 39668
> /home/anmolm/trunk/src/openpaa
> 080a0000-080a1000 rw-p 00057000 08:01 39668
> /home/anmolm/trunk/src/openpaa
> 093de000-093ff000 rw-p 00000000 00:00 0 [heap]
> b6600000-b6621000 rw-p 00000000 00:00 0
> b6621000-b6700000 ---p 00000000 00:00 0
> b67ed000-b67ee000 ---p 00000000 00:00 0
> b67ee000-b6fee000 rw-p 00000000 00:00 0
> b6fee000-b6fef000 ---p 00000000 00:00 0
> b6fef000-b77f2000 rw-p 00000000 00:00 0
> b7802000-b7805000 rw-p 00000000 00:00 0
> bf8af000-bf8d0000 rw-p 00000000 00:00 0 [stack]
> Aborted
>
>
>
> ------------------------------
> *From:* Francisco Vidal Meca <f.v...@um...>
> *To:* anmolmeet singh malhi <anm...@ym...>
> *Cc:* Pedro Moreno Sánchez <p.m...@um...>; "
> ope...@li..." <
> ope...@li...>
> *Sent:* Thursday, 27 June 2013, 8:44
> *Subject:* Re: [Openpana-users] openpana implementation
>
> Hi Anmolmeet Singh Malhi,
>
> With so few details it's difficult to have an idea of what's going on with
> your "config.xml".
>
> Some details about your network set up, where the different entities (PaC,
> PAA, RADIUS server) are located and the config.xml might help in determine
> if there is some error in your config.xml, wrong network setup or bugs in
> the OpenPANA implementation itself. Attaching the config.xml itself might
> also help.
>
> Please take a look at the documentation provided in [1] and compare your
> config.xml file with the one given by default. There car be some parsing
> problems such as introducing the IP with a wrong format.
>
> Best regards,
> Francisco Vidal Meca
>
> [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/
>
>
> 2013/6/27 anmolmeet singh malhi <anm...@ym...>
>
> hello sorry to interupt you
> if i use my auth server ip address in config.xml i got memory error
> somthing like
>
> openpaa malloc() memory corruption
> please help
> On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez
>
> Hi Anmol.
>
> Inside the configuration file (config.xml) you have three different
> sections (PaC, PAA and PRE configuration data). Inside the PAAConfiguration Data section, you have the <
> AUTH_SERVER> subsection, where you can configure the values corresponding
> to the RADIUS server. In particular, you can configure:
> - <IP_VERSION_AUTH> IP version to be used in the communication between
> the PAA and the RADIUS server
> - <AS_IP> IP address in which the RADIUS server will be listening to
> incoming request
> - <AS_PORT> UDP port in which the RADIUS server will be listening to
> incoming request
> - <SHARED_SECRET> Shared secret between the RADIUS server and the RADIUS
> client (note that the former is included inside the PAA functionality).
>
> You can find more info about the configuration file and some other
> questions in the documentation of the OpenPANA's project, under the link:
> http://sourceforge.net/projects/openpana/files/docs/
>
> Hope it helps,
> Pedro.
>
>
> On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...> wrote:
>
> I need help in configuration of config.xml .
> what should be the ip address of radius server is that my ip address of
> PAA ?
> please help i am doing research on pana protocol
> Thankyou
>
> ------------------------------------------------------------------------------
> This SF.net <http://sf.net/> email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Openpana-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openpana-users
>
>
>
>
> --
>
> ----------------------------------------------------------------------------
> Pedro Moreno Sánchez - MSc Computer Engineer
> Networks and Telematics
> Faculty of Computer Science - University of Murcia
> 30100 - Murcia - Spain
> email: p.m...@um...
>
> ----------------------------------------------------------------------------
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Openpana-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openpana-users
>
>
>
>
>
--
----------------------------------------------------------------------------
Pedro Moreno Sánchez - MSc Computer Engineer
Networks and Telematics
Faculty of Computer Science - University of Murcia
30100 - Murcia - Spain
email: p.m...@um...
----------------------------------------------------------------------------
|
|
From: Francisco V. M. <f.v...@um...> - 2013-06-27 08:02:32
|
Hi Anmolmeet Singh Malhi, With so few details it's difficult to have an idea of what's going on with your "config.xml". Some details about your network set up, where the different entities (PaC, PAA, RADIUS server) are located and the config.xml might help in determine if there is some error in your config.xml, wrong network setup or bugs in the OpenPANA implementation itself. Attaching the config.xml itself might also help. Please take a look at the documentation provided in [1] and compare your config.xml file with the one given by default. There car be some parsing problems such as introducing the IP with a wrong format. Best regards, Francisco Vidal Meca [1] http://sourceforge.net/projects/openpana/files/docs/OpenPANA_v0.2.4/ 2013/6/27 anmolmeet singh malhi <anm...@ym...> > hello sorry to interupt you > if i use my auth server ip address in config.xml i got memory error > somthing like > > openpaa malloc() memory corruption > please help > On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez > > Hi Anmol. > > Inside the configuration file (config.xml) you have three different > sections (PaC, PAA and PRE configuration data). Inside the PAAConfiguration Data section, you have the < > AUTH_SERVER> subsection, where you can configure the values corresponding > to the RADIUS server. In particular, you can configure: > - <IP_VERSION_AUTH> IP version to be used in the communication between > the PAA and the RADIUS server > - <AS_IP> IP address in which the RADIUS server will be listening to > incoming request > - <AS_PORT> UDP port in which the RADIUS server will be listening to > incoming request > - <SHARED_SECRET> Shared secret between the RADIUS server and the RADIUS > client (note that the former is included inside the PAA functionality). > > You can find more info about the configuration file and some other > questions in the documentation of the OpenPANA's project, under the link: > http://sourceforge.net/projects/openpana/files/docs/ > > Hope it helps, > Pedro. > > > On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...> wrote: > >> I need help in configuration of config.xml . >> what should be the ip address of radius server is that my ip address of >> PAA ? >> please help i am doing research on pana protocol >> Thankyou >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Openpana-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openpana-users >> > > > > -- > > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > > ---------------------------------------------------------------------------- > > > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Openpana-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openpana-users > > |
|
From: anmolmeet s. m. <anm...@ym...> - 2013-06-27 07:35:37
|
hello sorry to interupt you if i use my auth server ip address in config.xml i got memory error somthing like openpaa malloc() memory corruption please help On 24 Jun 2013, at 13:48, Pedro Moreno Sánchez > Hi Anmol. > > Inside the configuration file (config.xml) you have three different sections (PaC, PAA and PRE configuration data). Inside the PAA Configuration Data section, you have the <AUTH_SERVER> subsection, where you can configure the values corresponding to the RADIUS server. In particular, you can configure: > - <IP_VERSION_AUTH> IP version to be used in the communication between the PAA and the RADIUS server > - <AS_IP> IP address in which the RADIUS server will be listening to incoming request > - <AS_PORT> UDP port in which the RADIUS server will be listening to incoming request > - <SHARED_SECRET> Shared secret between the RADIUS server and the RADIUS client (note that the former is included inside the PAA functionality). > > You can find more info about the configuration file and some other questions in the documentation of the OpenPANA's project, under the link: > http://sourceforge.net/projects/openpana/files/docs/ > > Hope it helps, > Pedro. > > > On 24 June 2013 12:02, anmolmeet singh malhi <anm...@ym...> wrote: > I need help in configuration of config.xml . > what should be the ip address of radius server is that my ip address of PAA ? > please help i am doing research on pana protocol > Thankyou > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Openpana-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openpana-users > > > > -- > ---------------------------------------------------------------------------- > Pedro Moreno Sánchez - MSc Computer Engineer > Networks and Telematics > Faculty of Computer Science - University of Murcia > 30100 - Murcia - Spain > email: p.m...@um... > ---------------------------------------------------------------------------- > > > > > |
2 messages has been excluded from this view by a project administrator.
