On Wed, 2005-07-20 at 21:29 +0200, freeradius-users- request@lists.freeradius.org wrote:
sean <sean@topup.ie> wrote:
The problem is that Chilli can't communicate with my Radius server. Ethereal tells me that the destination is unreachable when replying to the Chilli box.
It looks like the port isn't open.
No. Time Source Destination Protocol Info 540 142.622909 192.168.1.6 82.141.232.132 RADIUS Access Request(1) (id=0, l=195)
Ok...
The Radius server and the Chilli AP get their IP's from DHCP on a Caymen DSL modem with static IP. The Modem is 82.141.232.132. The Radius server is 192.168.1.2
What's the problem? The Ethereal output you showed above disagrees with your statement about the IP address of the RADIUS server.
You have the Chilli AP configured to send RADIUS packets to the DSL modem. The Ethereal output is telling you this.
Alan DeKok.
I have UDP and TCP Pinholes open in the modem for ports 1812, 1813 and 1814 pointing to 192.168.1.2 This should be directing trafic to 82.141.232.132:1812 etc to 192.168.1.2:1812. That is what I had to do for Apache, Jabber and other services. Does Radius use any other ports and should I have any ports opened to 192.168.1.6 Thanks for your help. Regards Sean
sean <sean@topup.ie> wrote:
I have UDP and TCP Pinholes open in the modem for ports 1812, 1813 and 1814 pointing to 192.168.1.2 This should be directing trafic to 82.141.232.132:1812 etc to 192.168.1.2:1812.
The "destination unreachable" message says that isn't happening. Have you tried looking at the packets coming *out* of 82.141.232.132 to 192.168.1.2, to see if the forwarding is happening?
Does Radius use any other ports and should I have any ports opened to 192.168.1.6
Talk of other ports is a waste of time. You say you've set it up to forward packets sent to 82.141.232.132:1812, yet the logs you posted shows that packets sent to 82.141.232.132:1812 get "destination unreachable". Alan DeKok.
participants (2)
-
Alan DeKok -
sean