Menu
▾
▴
Re: [Openpana-users] openpana implementation
|
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...
----------------------------------------------------------------------------
|
