David Middleton <[EMAIL PROTECTED]> wrote:
> FYI update, I ran tcpdump on the server and found that the radius
> server was responding with a different address, even though I used the
> -i xxx.xxx.xxx.xxx address switch. I changed the radius address on the
> AP and it's working fine now.
Or, edi
FYI update, I ran tcpdump on the server and found that the radius
server was responding with a different address, even though I used the
-i xxx.xxx.xxx.xxx address switch. I changed the radius address on the
AP and it's working fine now.
David
--- Artur Hecker <[EMAIL PROTECTED]> wrote:
> you co
you could log in into the AP and see what happens in there if this is
supported.
you mean the AP sends the Request, gets the challenge but never answers?
ciao
artur
David Middleton wrote:
Yes I can. I also traced it and it is getting there. It's almost like
the AP is ignoring the packets being
Yes I can. I also traced it and it is getting there. It's almost like
the AP is ignoring the packets being sent to it.
David
--- Ulrich Walcher <[EMAIL PROTECTED]> wrote:
> Sounds like a routing problem.
> Can you ping the ap?
> Am Fre, 2003-09-05 um 17.30 schrieb David Middleton:
> ---SNIP ---
Sounds like a routing problem.
Can you ping the ap?
Am Fre, 2003-09-05 um 17.30 schrieb David Middleton:
---SNIP ---
> The radius server and the ap are on
> different networks, but there is no firewall between them.
>
> Any assistance would be appreciated,
> David
-
List info/subscribe/unsub
I am having trouble getting FreeRadius and an AP-2000 to work.
I installed FreeRadius 0.9.0 on a slackware linux server and everything
there went fine. I then configured the AP-2000 and everything looked
ok, I can even see requests being sent to the radius server and the
radius server sending a re