Re: failed to receive Accounting Response
Ok! Then I have one a question about moving Accounting packets through my network: When I login to cisco on log server(radius server) I racieve a: tcpdump port 1813 15:48:00.281073 IP 192.168.255.10.radacct > carlogg.radacct: RADIUS, Accounting Request (4), id: 0x67 length: 93 15:48:00.281727 IP carlogg.radacct > 192.168.255.10.radacct: RADIUS, Accounting Response (5), id: 0x67 length: 20 Then mean the ttrouble in my radius setting, but I don't resolve where!
Hi,
Ok! Then I have one a question about moving Accounting packets through my network:
When I login to cisco on log server(radius server) I racieve a:
tcpdump port 1813
15:48:00.281073 IP 192.168.255.10.radacct > carlogg.radacct: RADIUS, Accounting Request (4), id: 0x67 length: 93 15:48:00.281727 IP carlogg.radacct > 192.168.255.10.radacct: RADIUS, Accounting Response (5), id: 0x67 length: 20
do you see anything at the same time with radiusd -X if not, then there are two things 1) iptables or some other firewall ont he host is not allowing UDP 1813 to the applications 2) radiusd isnt listening on port 1813 (check your listen stuff and do 'netstat -anp | grep radiusd' to see what IP and ports radiusd is listening on) alan
Ok! Then I have one a question about moving Accounting packets through my network:
When I login to cisco on log server(radius server) I racieve a:
tcpdump port 1813
15:48:00.281073 IP 192.168.255.10.radacct > carlogg.radacct: RADIUS, Accounting Request (4), id: 0x67 length: 93 15:48:00.281727 IP carlogg.radacct > 192.168.255.10.radacct: RADIUS, Accounting Response (5), id: 0x67 length: 20
Then mean the ttrouble in my radius setting, but I don't resolve where!
So, port 1813 is OK. How about the port on which the packets are recieved. Zou can see that port on radius debug Sending Accounting-Reasopnse to IP:port. Check if firewall is closed for that IP:port. Ivan Kalik
participants (3)
-
"Николай Г. Петров" -
A.L.M.Buxey＠lboro.ac.uk -
tnt＠kalik.net