Frédéric EVRARD wrote:

Hi,

Running freeradius -x, we get the following:
...
Listening on authentication x.x.x.x:1812
Listening on accounting x.x.x.x:1813
Ready to process requests.
rad_recv: Accounting-Request packet from host y.y.y.y:1646, id=84,
length=461
...
Sending Accounting-Response of id 84 to y.y.y.y:1646


In radiusd.conf: port = 1812

In /etc/services:
datametrics     1645/tcp        old-radius
datametrics     1645/udp        old-radius
sa-msg-port     1646/tcp        old-radacct
sa-msg-port     1646/udp        old-radacct

radius          1812/tcp
radius          1812/udp
radius-acct     1813/tcp        radacct         # Radius Accounting
radius-acct     1813/udp        radacct


What's wrong, our config or is it just the output?



Regards, Pascal


If I have understand doc about radiusd.conf, if you write port=1812,
freeradius doens't use /etc/services, try to let default value "port=0",
then Freeradius will read /etc/services. Maybe that could help you.

Fred


I add something to my answer, your NAS uses old port to talk to radius(1645), and your radius use new one(1812). Configure your radius and your NAS to talk on the same port.

Sorry, I didn't mention that everything is working fine! We want to use the ports 1812/1813 and the NAS are sending on port 1813.
If the NAS were not sending on the same port FreeRADIUS is listening on it should not work, right?


So that seems very strange to me :-/



- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to