Alan DeKok wrote:
Geoff Silver <[EMAIL PROTECTED]> wrote:
rad_recv: Access-Reject packet from host 127.0.0.1:1645, id=121, length=2
You're getting a *reject* and not any other issue? Oh...
Am I? I'm not entirely sure. Usually I see the client send me an
Access-Request message. I then see *me* send an Access-Request to the backend
server, and finally see an Access-Accept or Access-Reject message (not sure if
this last one comes from the backend to me or from me to the requesting client).
In the failure case, I'm seeing only one Access-Request, and then eventually
an Access-Reject that appears to be generated by me. I can't tell if I've
actually sent the second request to the backend server and not logged it, or
not even sent it.
That sounds to me like the home server is simply not responding to
the proxy server. This *should* be mentioned in the log file.
I don't see anything in the logs about it, unfortunately. I'll fire up
radiusd -AX and see if I can't get our VPN group to send some traffic to
recreate the problem again.
Alan DeKok.
--
http://deployingradius.com - The web site of the book
http://deployingradius.com/blog/ - The blog
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html