radius_put_vendor_string

(PECL radius >= 1.1.0)

radius_put_vendor_string — Attaches a vendor specific string attribute

说明

bool radius_put_vendor_string ( resource $radius_handle , int $vendor , int $type , string $value [, int $options = 0 [, int $tag ]] )

Attaches a vendor specific string attribute to the current RADIUS request. In general, radius_put_vendor_attr() is a more useful function for attaching string attributes, as it is binary safe.

Note:
A request must be created via radius_create_request() before this function can be called.

参数

radius_handle: The RADIUS resource.
vendor: The vendor ID.
type: The attribute type.
value: The attribute value. This value is expected by the underlying library to be null terminated, therefore this parameter is not binary safe.
options: A bitmask of the attribute options. The available options include RADIUS_OPTION_TAGGED and RADIUS_OPTION_SALT.
tag: The attribute tag. This parameter is ignored unless the RADIUS_OPTION_TAGGED option is set.

返回值

成功时返回 TRUE，或者在失败时返回 FALSE。

更新日志

版本	说明
PECL radius 1.3.0	The `options` and `tag` parameters were added.

参见

radius_put_vendor_int() - Attaches a vendor specific integer attribute

User Contributed Notes

sebastian at sebsoft dot nl 30-Oct-2008 05:04


In the PECL sources, a certain vendor specific string is included for Microsoft systems.

However, if you just want to pass something entirely different, like Cisco specifics, that's possible.

The fact that this isn't included in the sources of the PECL doesn't mean you can't use them.



Better said, everything there is in the dictionary of your Radius server can be put in as string.



Like the following example to write a h323-gw-id:

<?php

$res = radius_acct_open ();

radius_add_server($res,'127.0.0.1', 1813, 'mysecret', 10, 2);

radius_create_request($res, RADIUS_ACCOUNTING_REQUEST);

radius_put_vendor_string($res,9,33 ,"h323-gw-id=123456");



$result = radius_send_request($res);

?>