Thanks Alan, That's what I thought. I'll trace this back to our original source and have them check what's going on. Thanks for the confirmation :-) Stefan Paetow Federated Roaming Technical Specialist t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: stefanp@jabber.dev.ja.net skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800. On 12/02/2020, 13:39, "Freeradius-Users on behalf of Alan DeKok" <freeradius-users-bounces+stefan.paetow=jisc.ac.uk@lists.freeradius.org on behalf of aland@deployingradius.com> wrote: On Feb 12, 2020, at 7:19 AM, Stefan Paetow <Stefan.Paetow@jisc.ac.uk> wrote: > > Just a quick question... has anyone ever seen a RADIUS request/response containing a vendor-specific attribute with vendor 0, attribute 0? That's not an IANA packet, is it? I mean... IANA would just be non-VSA. Nope. I haven't seen it, and it's not in any standard. > Is this a possible misconfiguration somewhere? Only if you go out of your way to create a vendor dictionary with vendor ID 0, and then an attribute 0, and then manually add it to the configuration. If that attribute is coming from a NAS, then the NAS is broken. FreeRADIUS may make mistakes internally, it doesn't create bad RADIUS packets. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html