Issues with vendor 3375 (F5) and FreeRADIUS

[Gerd Magerhans]

Hi Coy,

Am 21.11.2023 um 16:52 schrieb Coy Hile (BLOOMBERG/ 919 3RD A):
[...]
> radcas-rr-641 /root # tcpdump -i bond0 -n -vvv host 10.91.250.120
> tcpdump: listening on bond0, link-type EN10MB (Ethernet), capture size 262144 bytes
[...]
> Vendor-Specific Attribute (26), length: 12, Value: Vendor: Unknown (3375)
> Vendor Attribute: 1, Length: 4, Value: ....
> 0x0000: 0000 0d2f 0106 0000 0000
> Vendor-Specific Attribute (26), length: 12, Value: Vendor: Unknown (3375)
> Vendor Attribute: 22, Length: 4, Value: ..#(
> 0x0000: 0000 0d2f 1606 0000 2328
> Vendor-Specific Attribute (26), length: 12, Value: Vendor: Unknown (3375)
> Vendor Attribute: 21, Length: 4, Value: ....
> 0x0000: 0000 0d2f 1506 0000 03e9
> 
> Why is the vendor showing up as "unknown (3375)" when 3375 is the vendor ID for F5? The attributes that FreeRADIUS says it's sending back actually match the vendor attributes, but they're all jumbled.

"Vendor: Unknown (3375)" is what tcpdump interpretes the attributes as. 
tcpdump does not know about the vendor dictionary You have included into 
the freeradius configuration. Hence tcpdump list those VSAs as "unknown" 
and can not translate the values. This is not a malfunction of radiusd.

You may want to use radclient to send and receive test requests to/from 
radiusd.

./regards gerd