Invalid vendor name in attribute name error after migration from 2.2.6 to 3.0.13

[Alan DeKok]

On Aug 19, 2019, at 9:47 AM, Лев Валуев <2309005m03 at gmail.com> wrote:
> 
> I am not sure, I have got this configuration as a legacy. Initial
> radius configuration was done before me.
> I don't have access to NAS so I can't check how it uses this
> attribute, but without it, the user is unable to authorize on NAS.

  You can read the NAS documentation to see what attributes it accepts, and what they do.

> So, there is no way to use it and I need to get rid of this attribute?

  Find the attribute in the dictionaries in v2.  Then, add the attribute to v3.

  Odds are that it's something that was added locally, and therefore isn't in the standard distribution.

  After that, my suggestion is to change your configuration to use a standard attribute.  Which very likely already exists.

  Alan DeKok.