Just wanted to thank everyone for their help. I've gotten the issue
resolved.
Apparently Freeradius was working 100%, what wasn't working, however, was my
Cisco routing. We had our network worked on several weeks back, and all
seemed to be working ok, but it never dawned on me to check if my
On Mon, Mar 29, 2010 at 2:12 PM, Randall Degges rdeg...@gmail.com wrote:
FreeRADIUS Version 2.1.0, for host x86_64-pc-linux-gnu, built on Sep 17 2009
why?
better use latest stable version.
Listening on authentication address * port 1812
Listening on accounting address * port 1813
Hi,
*PROBLEM*
The problem I'm having is that when I run Freeradius (in production or
debug mode), my Cisco AS5400 is unable to connect to the freeradius
server. When I do a netstat -a on my freeradius server, I see no
connections listening on ports 1812 and 1813 (which freeradius should
be
Hi Stefan,
Ah, I thought that it would have to show in the bottom portion of my netstat
with the port numbers.
Also, when I run tcpdump (tcpdump port 1812) (tcpdump port 1813) I see no
packets at all. I've submitted a ticket with rackspace, although I'm like
99% sure there is no firewall there.
Stefan Everyone,
I just confirmed that my server does have no firewall. The way I tested this
is:
*ON THE SERVER*
tcpdump udp port 1812
*ON THE CLIENT*
nc -u xx.xx.xx.xx 1812
mash the keyboard repeatedly to send fake packets
When I do this I send some raw packets to my radius server on
Randall Degges wrote:
I just confirmed that my server does have no firewall. The way I tested
this is:
...
When I do this I send some raw packets to my radius server on port 1812
for testing, and my tcpdump output shows each packet being received just
fine. So I don't think this is a firewall
I just confirmed that my server does have no firewall. The way I tested this
is:
ON THE SERVER
tcpdump udp port 1812
ON THE CLIENT
nc -u xx.xx.xx.xx 1812
mash the keyboard repeatedly to send fake packets
When I do this I send some raw packets to my radius server on port
7 matches
Mail list logo
