Switch authorization on Radius?

Question

Computer networks

Good afternoon, Habr!
I want to test (but fail) the ability to authenticate and account switches (D-link 3526, firmware 6.10.023) on a Radius server (Freeradius 2.1.0 on Ubuntu 11.04).
read more
As planned, the following scheme should work:
1. The subscriber sends an IGMP-Join.
2.switch sees this and sends a message with authentication to the Radius server (as a username and password, the poppy address of the subscriber).
3.Radius-server replies to the switch that authentication was successful and the switch starts pouring a multicast stream on the subscriber's port.
4. Periodically and when switching the channel, the switch sends messages to the Radius server containing information for accounting.
The goal is to record the use of channels by subscribers. In fact, only accounting is needed.
BUT! The annoyance is that authentication does not pass and, accordingly, accounting does not occur.
Error text in radius logs ():

Wed Jun 22 16:21:23 2011 : Auth: Login incorrect: [001617122639/001617122639] (from client D-link port 20) <br/>

So, the login is not correct)))
However, in the Users file, I created this login:

001617122639 Cleartext-Password := "001617122639", NAS-Port == 20, Framed-IP-Address == "239.0.0.1", NAS-IP-Address == "10.10.0.1"

also the output of sudo freeradius -X gives the following (such garbage is sent by the switch, which I expected ...):

..............<br/>
User-Name = &quot;001617122639&quot;<br/>
User-Password = &quot;001617122639&quot;<br/>
NAS-IP-Address = 10.10.0.1<br/>
NAS-Identifier = &quot;D-Link&quot;<br/>
NAS-Port-Type = Virtual<br/>
Service-Type = Framed-User<br/>
Framed-Protocol = PPP<br/>
NAS-Port = 20<br/>
Framed-IP-Address = 239.0.0.1<br/>
..............

My thoughts and additions are as follows:
1. Judging by the logs and by the fact that the login and password are transmitted correctly, I sin on the type of entry in the Users file. However, I tried to enclose in quotes, I tried to write in a column - the same thing.
2. Accordingly, every time after changing the settings, I restart the service.
3. With a non-digital login, authentication passes.
4. I tried to test using the radtest utility with this login and password - the same error.
5. I tried, although a little, to do the same with the radl utility, and authentication does not work either.
6. Yes, and looking at the traffic dump, I also see what comes to the server, everything seems to be correct (as in the output of freeradius -X).
Lord, please help! Thank you.

Answer 1

check that files is in:
authorize {
...
files
...
}
accounting {
...
files
...
attr_filter.accounting_response # worth checking, mb. something needs to be tweaked.
}
In general, it would be nice to see the full output of the freeradius -X command along with 1 authorization attempt.