[strongSwan] Strongswan charon 4.6.4 not responding with more that one INTERNAL_IPV4_ADDRESS

[Avishek Ganguly]

Hi,

I am developing a testing tool for ikev2 conforming rfc 5996.

In IKE_AUTH request sending Configuration payload with two
INTERNAL_IPV4_ADDRESS attributes which value's are null.

Is there anything wrong with the packet structure or some thing from
strongswan's side need to be modified?

In charon log it is showing that two INTERNAL_IPV4_ADDRESS attributes are
being parsed but in reply it is returning only one IPV4 address.

According to the spec -----------
"

Multiple internal addresses
      MAY be requested by requesting multiple internal address
      attributes.  The responder MAY only send up to the number of
      addresses requested.

"
My packet structure is like sending on CP and the CFG attributes are listed
in that payload only.
Is there any need to send Multiple different CP's for each CFG attributes,
though it is not mentioned anywhere in the spec?

Below is the strong swan log for CFG attribute parsing -----

Jun 14 16:11:04 05[ENC]   parsing rule 14 CONFIGURATION_ATTRIBUTES
Jun 14 16:11:04 05[ENC]   8 bytes left, parsing recursively
CONFIGURATION_ATTRIBUTE
Jun 14 16:11:04 05[ENC] parsing CONFIGURATION_ATTRIBUTE payload, 96 bytes
left
Jun 14 16:11:04 05[ENC] parsing payload from => 96 bytes @ 0x8f00bb4
Jun 14 16:11:04 05[ENC]    0: 00 01 00 00 00 01 00 00 2C 00 00 28 00 00 00
24  ........,..(...$
Jun 14 16:11:04 05[ENC]   16: 01 03 04 03 00 00 3E 9D 03 00 00 08 01 00 00
03  ......>.........
Jun 14 16:11:04 05[ENC]   32: 03 00 00 08 03 00 00 01 00 00 00 08 05 00 00
00  ................
Jun 14 16:11:04 05[ENC]   48: 2D 00 00 18 01 00 00 00 07 00 00 10 00 00 FF
FF  -...............
Jun 14 16:11:04 05[ENC]   64: 1E 00 00 00 1E 00 00 FF 00 00 00 18 01 00 00
00  ................
Jun 14 16:11:04 05[ENC]   80: 07 00 00 10 00 00 FF FF 78 78 78 00 78 78 78
FF  ........xxx.xxx.
Jun 14 16:11:04 05[ENC]   parsing rule 0 RESERVED_BIT
Jun 14 16:11:04 05[ENC]    => 0
Jun 14 16:11:04 05[ENC]   parsing rule 1 ATTRIBUTE_TYPE
Jun 14 16:11:04 05[ENC]    => 1
Jun 14 16:11:04 05[ENC]   parsing rule 2 CONFIGURATION_ATTRIBUTE_LENGTH
Jun 14 16:11:04 05[ENC]    => 0
Jun 14 16:11:04 05[ENC]   parsing rule 3 CONFIGURATION_ATTRIBUTE_VALUE
Jun 14 16:11:04 05[ENC]    => => 0 bytes @ (nil)
Jun 14 16:11:04 05[ENC] parsing CONFIGURATION_ATTRIBUTE payload finished
Jun 14 16:11:04 05[ENC]   4 bytes left, parsing recursively
CONFIGURATION_ATTRIBUTE
Jun 14 16:11:04 05[ENC] parsing CONFIGURATION_ATTRIBUTE payload, 92 bytes
left
Jun 14 16:11:04 05[ENC] parsing payload from => 92 bytes @ 0x8f00bb8
Jun 14 16:11:04 05[ENC]    0: 00 01 00 00 2C 00 00 28 00 00 00 24 01 03 04
03  ....,..(...$....
Jun 14 16:11:04 05[ENC]   16: 00 00 3E 9D 03 00 00 08 01 00 00 03 03 00 00
08  ..>.............
Jun 14 16:11:04 05[ENC]   32: 03 00 00 01 00 00 00 08 05 00 00 00 2D 00 00
18  ............-...
Jun 14 16:11:04 05[ENC]   48: 01 00 00 00 07 00 00 10 00 00 FF FF 1E 00 00
00  ................
Jun 14 16:11:04 05[ENC]   64: 1E 00 00 FF 00 00 00 18 01 00 00 00 07 00 00
10  ................
Jun 14 16:11:04 05[ENC]   80: 00 00 FF FF 78 78 78 00 78 78 78
FF              ....xxx.xxx.
Jun 14 16:11:04 05[ENC]   parsing rule 0 RESERVED_BIT
Jun 14 16:11:04 05[ENC]    => 0
Jun 14 16:11:04 05[ENC]   parsing rule 1 ATTRIBUTE_TYPE
Jun 14 16:11:04 05[ENC]    => 1
Jun 14 16:11:04 05[ENC]   parsing rule 2 CONFIGURATION_ATTRIBUTE_LENGTH
Jun 14 16:11:04 05[ENC]    => 0
Jun 14 16:11:04 05[ENC]   parsing rule 3 CONFIGURATION_ATTRIBUTE_VALUE
Jun 14 16:11:04 05[ENC]    => => 0 bytes @ (nil)
Jun 14 16:11:04 05[ENC] parsing CONFIGURATION_ATTRIBUTE payload finished
Jun 14 16:11:04 05[ENC] parsing CONFIGURATION payload finished

Can some one please clarify?

Thanks in Advance.

Regards,
aganguly
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/users/attachments/20130614/a1a928f0/attachment.html>