Sending attribute with sub-attributes
David Peterson
davidp at wirelessconnections.net
Wed Mar 16 19:59:12 CET 2011
After some excellent tutelage from Mr. Wiechman, I am getting different
access-accept. However, it's showing Breezecom attributes which seem out of
place.
Access-Accept Id 86 172.16.4.14:1812 -> 172.16.4.2:1812 +26.680
Breezecom-Attr1 = "vpws"
Breezecom-Attr1 = "\000\000\000{"
Breezecom-Attr1 = "\000\001"
WiMAX-Packet-Data-Flow-Id = 1
WiMAX-Direction = Bi-Directional
WiMAX-Transport-Type = Ethernet
WiMAX-Uplink-QOS-Id = 1
WiMAX-Downlink-QOS-Id = 1
Breezecom-Attr11 = "\000\000\000\002"
Breezecom-Attr11 = "\000\000\000\001"
Breezecom-Attr11 = "\003"
Breezecom-Attr8 = "\000\000\000\310"
WiMAX-QoS-Id = 1
WiMAX-Schedule-Type = Best-Effort
WiMAX-Traffic-Priority = 4
WiMAX-Maximum-Sustained-Traffic-Rate = 524288
EAP-Message = 0x03080004
Message-Authenticator = 0x8f55919c4b4c60477f2db19bb718991e
User-Name = "{sm=1}002C4FF731202A48C2F17C5DB5C47019"
WiMAX-MSK =
0x9981c3c5526316c7187b884c6877162d8158025a98d212500cfe1a9809fc011a7f12796947
7a38a93b493304783d6cbb4b581f3a50a011fd04b78cba8b3f20caed618b15c1a23af3d1bb03
4c6812d5ad822b
Is there another dictionary that is driving the Breezecom-Attr or does
Freeradius just figure out its Alvarion and assign that internally?
David
-----Original Message-----
From:
freeradius-users-bounces+david.peterson=acc-corp.net at lists.freeradius.org
[mailto:freeradius-users-bounces+david.peterson=acc-corp.net at lists.freeradiu
s.org] On Behalf Of David Peterson
Sent: Wednesday, March 16, 2011 1:42 PM
To: FreeRadius users mailing list
Subject: RE: Sending attribute with sub-attributes
OK set up radsniff and am seeing the following access-accept:
Access-Request Id 34 172.16.4.2:1812 -> 172.16.4.14:1812 +28.495
User-Name = "{sm=1}FA9855191E4832141998A03A7F827633 at WiMax.com"
EAP-Message =
0x020600d01580000000c616030100861000008200804b0afe388db371ab697ea9a00c4f4e8b
57cf5def239b801972d3bb8131d327e0a4f84a78b4e1084e4b27439fb7b025013b1950689de6
c28997f09b34694141e0f81def057e61e6a4c069def68c0160419fc68d332f001ad29adcb7fa
462ee8b9ad2bb4b99edd890f51c8bea74d42d0b8b5a860e83aa02ee4397fdff5948166601403
01000101160301003033b07664e55c63d8c752131c02235aaf88bda8e166ba71080c17335e52
01d3aecccae5019bbde607b9dcb08d05733047
Message-Authenticator = 0xdf908effc4e4f5d3f7dfa19d28a9cca3
NAS-Identifier = "4motion"
NAS-IP-Address = 172.16.4.2
Calling-Station-Id = "00-26-82-CA-6D-B0"
WiMAX-BS-Id = 0xfff329000001
NAS-Port-Type = 27
Framed-MTU = 2000
Service-Type = Framed-User
WiMAX-GMT-Timezone-offset = 0
WiMAX-Release = "1.0"
WiMAX-Accounting-Capabilities = IP-Session-Based
WiMAX-Hotlining-Capabilities = Hotline-Profile-Id
WiMAX-Attr-1793 = 0x0000028a
State = 0x71bea04575b8b51c6b3e400a0b7eaac2
Access-Challenge Id 34 172.16.4.14:1812 -> 172.16.4.2:1812 +28.500
EAP-Message =
0x0107004515800000003b1403010001011603010030e524056fa3a81b105c96239b9e88d105
06e63b5a0b71257d6c3ddef0a93e0b1234af032a18ef2f0eff217596a2ec63a9
Message-Authenticator = 0xdd2059b4ee01295ee23b010784ad8e82
State = 0x71bea04574b9b51c6b3e400a0b7eaac2
Access-Request Id 35 172.16.4.2:1812 -> 172.16.4.14:1812 +28.625
User-Name = "{sm=1}FA9855191E4832141998A03A7F827633 at WiMax.com"
EAP-Message =
0x020700c015001703010020af88796d54ff518c6fc9c4cbd7c870e75d4a301b57a650afc8f9
564a6472ed0f1703010090e532047e4b7e0af770e6aef6dba034560c7e3980c204d866559d96
aebe29311030c0e58ee6356857be034b68a6ca8ed2a80fc02273152f1cb692ba6b3da1335d4e
5dd60e726f8d522321d3af5afc7e0dece805e70aeb1d1f20ae5f05bd9a0df4280abc9769311b
b0d64f7653367fb4f9e75ac99b1faf8da602b174f4a4bc7d3eabe8692c6dc71301c44fdfad2c
854c48
Message-Authenticator = 0xb1ceae83822d784a23d3e8614aca1367
NAS-Identifier = "4motion"
NAS-IP-Address = 172.16.4.2
Calling-Station-Id = "00-26-82-CA-6D-B0"
WiMAX-BS-Id = 0xfff329000001
NAS-Port-Type = 27
Framed-MTU = 2000
Service-Type = Framed-User
WiMAX-GMT-Timezone-offset = 0
WiMAX-Release = "1.0"
WiMAX-Accounting-Capabilities = IP-Session-Based
WiMAX-Hotlining-Capabilities = Hotline-Profile-Id
WiMAX-Attr-1793 = 0x0000028a
State = 0x71bea04574b9b51c6b3e400a0b7eaac2
Access-Challenge Id 35 172.16.4.14:1812 -> 172.16.4.2:1812 +28.626
EAP-Message =
0x0108005f158000000055170301005062cea2e66a8eec902121e911deb72b6464b8ab4861b9
4730d4f9ccb21af518afe16c18f12f305041b2c6df60e6fdc02bad7849141eca3b6c3e27f9a1
2790af090615185f8270e3be4de91ec9343699c2
Message-Authenticator = 0xebe75e60f6789cde3b7dce50e64516ad
State = 0x71bea04577b6b51c6b3e400a0b7eaac2
Access-Request Id 36 172.16.4.2:1812 -> 172.16.4.14:1812 +28.689
User-Name = "{sm=1}FA9855191E4832141998A03A7F827633 at WiMax.com"
EAP-Message = 0x020800061500
Message-Authenticator = 0x5683416041e6648a72b51ef5d0d92c8e
NAS-Identifier = "4motion"
NAS-IP-Address = 172.16.4.2
Calling-Station-Id = "00-26-82-CA-6D-B0"
WiMAX-BS-Id = 0xfff329000001
NAS-Port-Type = 27
Framed-MTU = 2000
Service-Type = Framed-User
WiMAX-GMT-Timezone-offset = 0
WiMAX-Release = "1.0"
WiMAX-Accounting-Capabilities = IP-Session-Based
WiMAX-Hotlining-Capabilities = Hotline-Profile-Id
WiMAX-Attr-1793 = 0x0000028a
State = 0x71bea04577b6b51c6b3e400a0b7eaac2
Access-Accept Id 36 172.16.4.14:1812 -> 172.16.4.2:1812 +28.690
WiMAX-Attr-4381 = 0x010676707773020531323303040001
WiMAX-Packet-Data-Flow-Id = 1
WiMAX-Direction = Bi-Directional
WiMAX-Transport-Type = Ethernet
WiMAX-Uplink-QOS-Id = 1
WiMAX-Downlink-QOS-Id = 1
WiMAX-Attr-2844 = 0x0103020206000000010403030806000000c8
WiMAX-QoS-Id = 1
WiMAX-Schedule-Type = Best-Effort
WiMAX-Traffic-Priority = 4
WiMAX-Maximum-Sustained-Traffic-Rate = 524288
EAP-Message = 0x03080004
Message-Authenticator = 0xd3e1212d3ef4d04b512b7212c58858f3
User-Name = "{sm=1}FA9855191E4832141998A03A7F827633"
WiMAX-MSK =
0x9dec7a253fe31755903407d2fac5130fa96e8fe4469dbb6d825fa7bc7f23a2a74fdba9a5d8
d2e0dbe34f89d54495895ce557134c92fe4fd2e9c8b9fb1bc90261f7865036ed45c03b5a4c61
73ac3d58afaff4
Is there more detail we can get from radsniff?
David
-----Original Message-----
From:
freeradius-users-bounces+david.peterson=acc-corp.net at lists.freeradius.or
freeradius-users-bounces+g
[mailto:freeradius-users-bounces+david.peterson=acc-corp.net at lists.freeradiu
s.org] On Behalf Of Alan DeKok
Sent: Tuesday, March 15, 2011 10:30 AM
To: David Peterson-WirelessConnections; FreeRadius users mailing list
Subject: Re: Sending attribute with sub-attributes
David Peterson wrote:
> ... 1a 12 >.zi.... .M%.6...
> 0040 00 00 60 b5 1a 0c 00 01 06 76 70 77 73 03 03 01 ..`..... .vpws...
> 0050 1a 29 00 00 60 b5 1c 23 00 04 03 03 06 03 03 07 .)..`..# ........
> Not sure if this helps or not....
> VSA: l=12 t=WiMAX-PDFID(26) C=0x00: [unhandled integer length(9)]
Well, wireshark isn't using the same dictionaries you're using.
Wireshark is using the standard WiMAX dictionaries (it seems), and you're
using the broken Alvarion version of the WiMAX dictionaries.
If you want wireshark to print out the same things as sent by FreeRADIUS,
make Wireshark use the FreeRADIUS dictionaries.
Or, use "radsniff", which *automatically* uses the FreeRADIUS
dictionaries.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
More information about the Freeradius-Users
mailing list