Ethereal-dev: SV: [Ethereal-dev] RADIUS / Implementation of additional VendorSpecific Attribut
Hi,
Vendor id 3414 belongs to:
3414
VoiceStream Wireless, Inc.
Trey Valenta
trey.valenta@xxxxxxxxxxxxxxx
For the vendor attributes of of T-Systems Nova International GmbH could you
provide the information in the format:
static const radius_attr_info radius_vendor_t_systems_nova_attrib[] =
{
{1, RADIUS_STRING, "Location-ID ", NULL, NULL},
{2, RADIUS_STRING, "Location-Name ", NULL, NULL},
With RADIUS_STRING replaces by RADIUS_INTEGER4 where appropriate(
Avalable attributes are:
RADIUS_STRING,
RADIUS_BINSTRING,
RADIUS_USERPASSWORD,
RADIUS_INTEGER2,
RADIUS_INTEGER4,
RADIUS_INTEGER8,
RADIUS_IP_ADDRESS,
RADIUS_IP6_ADDRESS,
RADIUS_IP6_PREFIX,
RADIUS_IP6_INTF_ID,
RADIUS_UNKNOWN,
RADIUS_IPX_ADDRESS,
RADIUS_STRING_TAGGED,
RADIUS_VENDOR_SPECIFIC,
RADIUS_TIMESTAMP,
RADIUS_INTEGER4_TAGGED,
RADIUS_EAP_MESSAGE,
Best regards
Anders
-----Ursprungligt meddelande-----
Från: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] För Biewald, Manuel
Skickat: den 14 juni 2005 15:34
Till: 'ethereal-dev@xxxxxxxxxxxx'
Ämne: [Ethereal-dev] RADIUS / Implementation of additional VendorSpecific
Attributes
Dear RADIUS experts,
Would you be so kind to implement the decoding of some more Vendor Specific
Attributes for the convenience of the WLAN RADIUS Roaming community.
The Attributes / Vendors are:
the T-Mobile Vendor ID 3414 for T-Mobile-originated VSAs
Attribute Name # Type Comments
Venue-UTC-Offset 41 Integer UTC offset at venue location
Venue-DST-Flag 42 Integer Daylight Savings Time 0 = No, 1 = Yes
Venue-EOD 43 Integer End of day time (24 hour clock) at
venue
The vendor ID (IANA number) 16787 of T-Systems Nova International GmbH
# Attribute Comments
1 Location-ID Unique ID of the Location (Hotspot)
where the End User is using the service. E.g. Berlin_TegelAirport_100
2 Location-Name Name of the Location (Hotspot) where
the end-customer is using the service. "Tegel_Airport_Gate_A"
3 Logoff-URL URL for the end-customer to
perform explicit logoff. E.g. HTTP://www.berlinwisp.de/logout.html
4 Redirection URL After Login at a WISP
hotspot, end-customer SHOULD be redirected to the given URL
5 Bandwidth-Min-Up Minimal upstream bandwidth
which should be reserved to the end-customer (b/s)
6 Bandwidth-Min-Down Minimal downstream bandwidth which
should be reserved to the end-customer (b/s)
7 Bandwidth-Max-Up Maximal upstream bandwidth
the end-customer is allowed to use (b/s)
8 Bandwidth-Max-Down Maximal downstream bandwidth the
end-customer is allowed to use (b/s)
9 Session-Terminate-Time Absolute time for terminating the
end-customers session
10 Session-Terminate-End-Of-Day If flag is set to one, end-customers
session MUST be terminated at the end of the billing day
11 Billing-Class-Of-Service Describes the service(s) the
end-customer demands to use (authorization). Example:
wireless_internet_sunrise
12 Service-Name The service the end-customer is
using in this accounting session. Service-Name has to be the same as defined
in Billing-Class-of-Service. Example: wireless_internet_sunrise
13 Price-Of-Service (Accepted) Price for an
offered service per unit
14 Visiting-Provider-Code The carrier code of the WISP. A
unique carrier code is assigned to each WISP/provider by T-Systems.
Hopefully, the provided information's are helpful.
If you have questions, do not hesitate to contact me.
Thanks in advanced & regards,
Manuel Biewald
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev