gull-users Mailing List for Seagull

Hi:

I tried to store and restore "Vendor-Id", and "Firmware-Revision" avp
value from the request message in to answer message within the INIT
section of the scenario.  Both the segull's log file and the test log
file suggest that these AVPs are missing in the answer message generated
by the Seagull.

Can anyone let me know if this is a known problem?

Thanks,
Madhava

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

Dear all,
i have found, that radius authenticator calculation code needs in fix,
without it FreeRadius doesn't accept packets from SeaGull RADIUS
client.

This is patched version of function create_algo_MD5_radius
from file library-crypto/CryptExternalMethods.cpp

int create_algo_MD5_radius(char          *  P_msg,
                           int              P_msg_size,
                           char          *  P_shared_secret,
                           unsigned char *  P_result) {
  int        L_ret         = 0 ;
  int        L_size_shared = 0 ;

  MD5_CTX    L_Md5Ctx ;

  if (P_shared_secret != NULL) {
    L_size_shared = strlen(P_shared_secret);
  }

  memset(P_msg + 4, 0, 16);

  MD5_Init(&L_Md5Ctx);
  MD5_Update(&L_Md5Ctx, P_msg, P_msg_size);
  MD5_Update(&L_Md5Ctx, P_shared_secret, L_size_shared);
  MD5_Final(P_result, &L_Md5Ctx);

  return (L_ret);
}

Yours sincerely,
Roman Volkov

Hi Bruno,
Thanks for Reply. I have checked for the same configuration what ever=20
you have suggested, But
Now issue is, neither SCTP connection nor Tcp connection. Could any one=20
help me on this issue??
conf.xml given  below:
<define entity=3D"transport"
    name=3D"trans-1"
    file=3D"libtrans_extsctp.so"
    create_function=3D"create_cipsctpio_instance"
    delete_function=3D"delete_cipsctpio_instance"
    init-args=3D"type=3Dtcp">
  </define>
  <define entity=3D"channel"
    name=3D"channel-1"
    protocol=3D"diameter-v1"
    transport=3D"trans-1"
    open-args=3D"mode=3Dclient;dest=3D127.0.0.1:3868">
  </define>
Thanks and Regards
Shashi


Bruno, Guerin (NonHP : AtosOrigin) wrote:

> Hello
> You need to change the create_function and the delete_function like thi=
s:
>     create_function=3D"create_cipsctpio_instance"
>     delete_function=3D"delete_cipsctpio_instance"
> (as describe on the documentation :=20
> http://gull.sourceforge.net/doc/core.html#Transport+protocols+and+chann=
els )
> =20
> =20
> Regards
> Bruno GUERIN
> -----Message d'origine-----
> *De :* gul...@li...=20
> [mailto:gul...@li...]*De la part de*=20
> shashikant.suman
> *Envoy=C3=A9 :* lundi 13 ao=C3=BBt 2007 17:48
> *=C3=80 :* gul...@li...
> *Objet :* [Seagull-users] Error : SCTP connection with seagull
>
>     Hi Oliver,
>     Shashi here, I am trying to use Seagull with SCTP support.
>     1) I have downloaded the sctplib-1.0.5.tar.gz &
>     socketapi-1.9.0.tar.gz and
>          placed in the external-lib-src folder
>     2) Edited both build-ext-lib.conf & build.conf as per Installation
>     guide
>     3) then run the build-ext-lib.ksh, build.ksh and install.ksh
>     4) All the files along with libtrans_extsctp.so are created fine,
>     mean no compliation and linking error.
>     But problem is when running Seagull client and server mode,  No=20
>     SCTP  connection, Tcp connetion getting established and all message=
s
>     getting exchange on TCP connection.
>
>     WHAT COULD BE THE POSSIBLE CAUSE??
>     *my conf.server.xml file looks like this....
>     <?xml version=3D"1.0" encoding=3D"ISO-8859-1"?>
>     *<configuration name=3D"Simple IP Server Conf">
>       <define entity=3D"transport"
>         name=3D"trans_sctp"
>         file=3D"libtrans_extsctp.so"
>         create_function=3D"create_cipio_instance"
>         delete_function=3D"delete_cipio_instance"
>         init-args=3D"type=3Dtcp">
>       </define>
>       <define entity=3D"channel"
>         name=3D"channel-1"
>         protocol=3D"diameter-v1"
>         transport=3D"trans_sctp"
>         open-args=3D"mode=3Dserver;source=3D127.0.0.1:3868">
>       </define>
>     *my conf.client.xml file looks like this....*
>     ?xml version=3D"1.0" encoding=3D"ISO-8859-1"?>
>     <configuration name=3D"Simple IP Client Conf">
>       <define entity=3D"transport"
>         name=3D"trans_sctp"
>         file=3D"libtrans_extsctp.so"
>         create_function=3D"create_cipio_instance"
>         delete_function=3D"delete_cipio_instance"
>         init-args=3D"type=3Dtcp">
>       </define>
>       <define entity=3D"channel"
>         name=3D"channel-1"
>         protocol=3D"diameter-v1"
>         transport=3D"trans_sctp"
>         open-args=3D"mode=3Dclient;dest=3D127.0.0.1:3868">
>       </define>
>
>     Is my  conf.server.xml/ conf.client.xml  CONFIGURED CORRECTLY?? If
>     yes then what could be the other error?
>
>     Thanks and Regards
>     Shashi
>
>     -------------------------------------------------------------------=
-----
>     EMAIL DISCLAIMER : This email and any files transmitted with it
>     are confidential and intended solely for the use of the individual
>     or entity to whom they are addressed. Any unauthorised
>     distribution or copying is strictly prohibited. If you receive
>     this transmission in error, please notify the sender by reply
>     email and then destroy the message. Opinions, conclusions and
>     other information in this message that do not relate to official
>     business of Mascon shall be understood to be neither given nor
>     endorsed by Mascon. Any information contained in this email, when
>     addressed to Mascon clients is subject to the terms and conditions
>     in governing client contract.
>
>     Whilst Mascon takes steps to prevent the transmission of viruses
>     via e-mail, we can not guarantee that any email or attachment is
>     free from computer viruses and you are strongly advised to
>     undertake your own anti-virus precautions. Mascon grants no
>     warranties regarding performance, use or quality of any e-mail or
>     attachment and undertakes no liability for loss or damage,
>     howsoever caused.
>



EMAIL DISCLAIMER : This email and any files transmitted with it are confi=
dential and intended solely for the use of the individual or entity to wh=
om they are addressed. Any unauthorised distribution or copying is strict=
ly prohibited. If you receive this transmission in error, please notify t=
he sender by reply email and then destroy the message. Opinions, conclusi=
ons and other information in this message that do not relate to official =
business of Mascon shall be understood to be neither given nor endorsed b=
y Mascon. Any information contained in this email, when addressed to Masc=
on clients is subject to the terms and conditions in governing client con=
tract.=0A=0AWhilst Mascon takes steps to prevent the transmission of viru=
ses via e-mail, we can not guarantee that any email or attachment is free=
 from computer viruses and you are strongly advised to undertake your own=
 anti-virus precautions. Mascon grants no warranties regarding performanc=
e, use or quality of any e-mail or attachment and undertakes no liability=
 for loss or damage, howsoever caused. =0A=0A