Server dosn't detect any requests except from localhost
Hello, I have a student project that I need a RADIUS server in it. I have access to two servers that I have to remotely connect to them (VPN required, of course two servers are on the same network and can see each other always), one is having windows server on it and another one has CentOS 64bit on it. Both are virtual in a company using VMWare tools I believe. I installed freeRadius on CentOS and I performed first tests from the server itself and it's working allright. I added the clients and users that I needed to the configuration files. Here is the problem: Whenever I send a request from a radius client (I tried some testers, and even radtest) to my freeRadius server I get time out, freeRadius is running in dubuging mode and I can see that it doesn't receive any request whether to accept or reject. I tried the windows server on that LAN and my computer which is connected to VPN and can see the freeRadius server. (successful pinging) I used -netstat to see what IPs and ports are listening, the result was 0.0.0.0:1812(udp) so I assume that it is listening to all IPs on 1812. whenever I try to start the server with -i and -p I get the message that server cannot bind on the address that I want because it is already listening to them on another thing. I can start the server with -i 172.16.150.*** which is its own address and -p 1812. I am stocked on this problem for two days, I read all the config files of freeRadius and I tried to make some changes (I revert them later) but none helped cause I think the problem is not there. I assume that server should see all the requests and then decide what to do with them. Any ideas where the problem is? Thank you Saeed Zanderahimi
On 04/09/2013 05:21 AM, Saeed Zanderahimi wrote:
Hello, I have a student project that I need a RADIUS server in it. I have access to two servers that I have to remotely connect to them (VPN required, of course two servers are on the same network and can see each other always), one is having windows server on it and another one has CentOS 64bit on it. Both are virtual in a company using VMWare tools I believe. I installed freeRadius on CentOS and I performed first tests from the server itself and it's working allright. I added the clients and users that I needed to the configuration files. Here is the problem: Whenever I send a request from a radius client (I tried some testers, and even radtest) to my freeRadius server I get time out, freeRadius is running in dubuging mode and I can see that it doesn't receive any request whether to accept or reject. I tried the windows server on that LAN and my computer which is connected to VPN and can see the freeRadius server. (successful pinging) I used -netstat to see what IPs and ports are listening, the result was 0.0.0.0:1812(udp) so I assume that it is listening to all IPs on 1812. whenever I try to start the server with -i and -p I get the message that server cannot bind on the address that I want because it is already listening to them on another thing. I can start the server with -i 172.16.150.*** which is its own address and -p 1812. I am stocked on this problem for two days, I read all the config files of freeRadius and I tried to make some changes (I revert them later) but none helped cause I think the problem is not there. I assume that server should see all the requests and then decide what to do with them. Any ideas where the problem is?
I suspect a firewall is blocking your port. FWIW listening on a port is completely independent of whether the port is blocked, you have to check both. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
Saeed Zanderahimi wrote:
Here is the problem: Whenever I send a request from a radius client (I tried some testers, and even radtest) to my freeRadius server I get time out, freeRadius is running in dubuging mode and I can see that it doesn't receive any request whether to accept or reject. I tried the windows server on that LAN and my computer which is connected to VPN and can see the freeRadius server. (successful pinging)
So the network is up, but you can't reach the RADIUS port. This usually means a firewall is blocking traffic. Go check that.
I used -netstat to see what IPs and ports are listening, the result was 0.0.0.0:1812(udp) so I assume that it is listening to all IPs on 1812. whenever I try to start the server with -i and -p I get the message that server cannot bind on the address that I want because it is already listening to them on another thing. I can start the server with -i 172.16.150.*** which is its own address and -p 1812.
When you start the server in debugging mode, you need to shut down any server already running. You haven't done that. That's why it's saying "address already in use". 1) check that the firewall allows traffic to port 1812 2) stop all servers currently running 3) then run it in debug mode 4) it should work Alan DeKok.
Thank you for your answers, I added my client IP address and 1812:1814 ports to the iptables config file and after saving and rebooting it works now :) Regards Saeed ________________________________ From: Alan DeKok <aland@deployingradius.com> To: Saeed Zanderahimi <saeed_zr@yahoo.com>; FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Sent: Tuesday, April 9, 2013 2:21 PM Subject: Re: Server dosn't detect any requests except from localhost Saeed Zanderahimi wrote:
Here is the problem: Whenever I send a request from a radius client (I tried some testers, and even radtest) to my freeRadius server I get time out, freeRadius is running in dubuging mode and I can see that it doesn't receive any request whether to accept or reject. I tried the windows server on that LAN and my computer which is connected to VPN and can see the freeRadius server. (successful pinging)
So the network is up, but you can't reach the RADIUS port. This usually means a firewall is blocking traffic. Go check that.
I used -netstat to see what IPs and ports are listening, the result was 0.0.0.0:1812(udp) so I assume that it is listening to all IPs on 1812. whenever I try to start the server with -i and -p I get the message that server cannot bind on the address that I want because it is already listening to them on another thing. I can start the server with -i 172.16.150.*** which is its own address and -p 1812.
When you start the server in debugging mode, you need to shut down any server already running. You haven't done that. That's why it's saying "address already in use". 1) check that the firewall allows traffic to port 1812 2) stop all servers currently running 3) then run it in debug mode 4) it should work Alan DeKok.
Hi there , For some reason am not getting the callingstation-ID for my users who are using 3gpp, could be missing something in the config, i have done some reading and all my settings seem fine. This is how my accounting looks and am missing a key feature which is the calling station ID Wed Apr 10 12:39:06 2013 Acct-Multi-Session-Id = "53bf18f2" Acct-Link-Count = 1 Event-Timestamp = "Apr 10 2013 12:38:50 EAT" Framed-IP-Address = y.y.y.y Acct-Session-Id = "c400008653bf18f2" NAS-IP-Address = 196.0.0.133 Framed-Protocol = GPRS-PDP-Context Acct-Authentic = RADIUS Called-Station-Id = "broadband" NAS-Identifier = "GGSN9811" Acct-Delay-Time = 0 User-Name = "eric@3g" NAS-Port-Type = Virtual Service-Type = Framed-User Acct-Status-Type = Start 3GPP-IMSI = "6411101051238450" 3GPP-Charging-ID = 1405032690 3GPP-PDP-Type = 0 3GPP-Charging-Gateway-Address = x.x.x.x 3GPP-GPRS-Negotiated-QoS-profile = "99-23421f9196404074f74040" 3GPP-SGSN-Address = 196.0.0.129 3GPP-GGSN-Address = 196.0.0.134 3GPP-IMSI-MCC-MNC = "64111" 3GPP-GGSN-MCC-MNC = "64111" 3GPP-NSAPI = "5" 3GPP-Selection-Mode = "0" 3GPP-Charging-Characteristics = "0800" 3GPP-SGSN-MCC-MNC = "64111" 3GPP-Attr-26 = 0x00 Acct-Unique-Session-Id = "ae61f0992e7b5eaa" Timestamp = 1365586746 Request-Authenticator = Verified
Mulindwa wrote:
Hi there ,
For some reason am not getting the callingstation-ID for my users who are using 3gpp, could be missing something in the config, i have done some reading and all my settings seem fine.
This is how my accounting looks and am missing a key feature which is the calling station ID
This is in the FAQ. The NAS isn't sending it. Go fix the NAS. There is nothing you can do to FreeRADIUS to magically invent a Calling-Station-Id. Alan DeKok.
participants (4)
-
Alan DeKok -
John Dennis -
Mulindwa -
Saeed Zanderahimi