Problem in connecting to freeradius on Amazon EC2.

The professional way to manage your WiFi network using FreeRADIUS

Brought to you by: dvdwalt

Problem in connecting to freeradius on Amazon EC2.

Forum: Help

Creator: Karthik Kumar Balasubramani

Created: 2014-01-29

Updated: 2014-09-22

Karthik Kumar Balasubramani - 2014-01-29

Hello,

I tried installing Radiusdesk from source on a EC2 instance.
My requirements are to install
Nginx, FreeRadius and Node.js.

I followed the article http://www.radiusdesk.com/getting_started/install

After complete installation the clients cannot reach radius server. Debug says "ready to process request" and listening on ports. The netstat output shows ports 1812, 1813 open.
Radtest failed with "radclient: no response from server for id 122 socket 3"

Full debugoutput : http://pastebin.com/3N7Y6PXh
Radtest result: http://postimg.org/image/ss2n7gzll
Netstat output: http://postimg.org/image/9yguah1dl

The EC2 firewall is set to allow incoming 1812, 1813 and 1814. But still cannot see the ports open on the public IP.

Please help.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dirk van der Walt - 2014-01-29

Hi,

That does not make sense especially trying to connect from the local machine to itself with radclient.

You did all the tests I would also have done. What if you restart the machine as a last resort?

Regards

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Karthik Kumar Balasubramani - 2014-01-29
  
  Hi Dirk,
  
  I tried restarting and didn't make any difference. Do you think its something to do with Amazon EC2?
  
  Regards,
  Karthik.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dirk van der Walt - 2014-01-29

Hi Karthik,

If you want I can log into the server to do a quick check if there is something you may have overlooked. Sometimes two heads are better than one :-)

You can mail me: dirkvanderwalt at gmail

Regards

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Karthik Kumar Balasubramani - 2014-01-30

Hi Dirk,

Thanks a lot for your help. I will email you the login details shortly.

Cheers.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Karthik Kumar Balasubramani - 2014-02-04

Hi Dirk,

Thanks for sorting the problem for me. My RadiusDesk on EC2 receives packet now.

Cheers,
Karthik.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- krunal vaghasiya - 2017-01-26
  
  @Karthik
  
  Can you share what settings work for your freeradius at EC2 AWS, currentyl i am also facing same issue.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

alexandre - 2014-08-26

Hi,

I'm the one who using Amazon EC2 too. Could you please suggest me how to fix that problem.

Thanks

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Mfawa Alfred Onen - 2014-08-26
  
  Makes sure you open FreeRADIUS ports in your security groups for EC2
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - alexandre - 2014-08-26
    
    This is a list of ports I have opened: 22, 80, 8000 for tcp and 1812, 1813 for udp.
    
    Is there another port number need to be open?
    
    Thanks
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jon Webb - 2014-09-18

Was this just a port opening problem?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- alexandre - 2014-09-22
  
  Hi Jon Webb,
  
  For Amazon EC2 you have to open ICMP in Security Groups.
  
  Cheers.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dirk van der Walt - 2014-09-22

Hi guys,

It seems to be a common struggle on the Amazon EC2 to get the traffic going. Someone I helped with a few weeks back also had to open ICMP (although this I thought was more related to the MESHdesk since the MESHdesk firmware sends a ping to the back-end)

Unfortunately I don't have access to the EC2 control panel, so if one you you got it working, perhaps you can forward me a short 'howto' which we can add to the Wiki to ease things in the future.

Cheers

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- fridaystreet - 2014-09-22
  
  Sorry double post
  
  Last edit: fridaystreet 2014-09-22
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

fridaystreet - 2014-09-22

Hi Guys,

I can confirm you don't need ICMP to run pure radiusdesk on EC2. We've been running it for over a year on EC2 with an RDS DB and only have the following inbound rules. Server talks to the db server over the VPC.

1812 UDP
1813 UDP
8888 TCP
22 TCP
80 TCP
443 TCP

The only reason I could think you would need ICMP is for ping based monitoring, but that shouldn't be affecting freeradius. Sorry if it sounds silly, but you are modifying the right group? EC2 wizard tends to create a lot of generically named groups (eg launch wizard-1 launchwizard-2 etc), just double check the group the instance is using and make sure that's the group you're editing.

Cheers
Paul

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.