HI,
I am using seagull testing tool to send messages to free
radius. I am running seagull with radius protocol .
When i send messages from seagull to freeradius , the
password is not getting decrypted properly on radius side.
Can you please tell
Hi,
I am using seagull testing tool to send messages to free
radius. I am running seagull with radius protocol .
When i send messages from seagull to freeradius , the
password is not getting decrypted properly on radius side.
Hi alan,
Every time I am sending a message from seagull to freeradius ,it is decode the
password differently. I am also getting the following error in Radius debug
mode .
rad_recv: Access-Request packet from host 172.22.55.232 port 65535, id=6,
length=56
Acct-Session-Id = 6
Yashaswini Sathyanarayana wrote:
Every time I am sending a message from seagull to freeradius ,it is decode
the password differently. I am also getting the following error in Radius
debug mode .
...
WARNING: Unprintable characters in the password. Double-check the shared
secret on the
Hi ,
User-Password = \311~B]\021\267\332i\217
This part of message is not right.
The shared secret is same in both system.
Thanks Regards,
Yashaswini | Prod Engg | Tech Mahindra Ltd.
9 / 7 Hosur Road, Bangalore - 560029, India.
(Office: +91 80 40243000, Extn:
Yashaswini Sathyanarayana wrote:
User-Password = \311~B]\021\267\332i\217
This part of message is not right.
The shared secret is same in both system.
Either (a) it's not the same, or (b) the client has a bug.
And don't argue over this. I've been doing RADIUS for ~15
On 20/12/12 11:50, Yashaswini Sathyanarayana wrote:
WARNING: Unprintable characters in the password. Double-check the shared
secret on the server and the NAS!
This message is accurate. You have a typo, or the NAS is buggy.
Re-set the shared secret to something VERY SIMPLE e.g. abc123 - no
Hello,
I am running version 3.0.0 and have a question about sub-tlvs:
I am looking at:
WiMAX-QoS-Descriptor
as it is defined in dictionary.wimax.alvarion
(the standard dictionary.wimax does not get included/is commented out)
This is the situation:
My reply has to contain two QoS profiles.
You follow the dictionary in the order set inside of it. Once you hit the
end of your list of attributes the QoS profile is complete. Keep in mind
that each service flow starts with:
Alvarion-R3-IF-Name+=cpe_mgnt_sg,
Alvarion-PDFID+=1,
WiMAX-Packet-Data-Flow-Id+=1,
If you want
It is noticed that some VSAs are sent with Access-Challenge but not with
Access-Accept when PEAP is used.
Is there a way to configure the server such that those attributes are sent with
Access-Accept?
Thank you.-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
rosect...@yahoo.com wrote:
It is noticed that some VSAs are sent with Access-Challenge but not with
Access-Accept when PEAP is used.
Is there a way to configure the server such that those attributes are
sent with Access-Accept?
Configure the server to send them in the Access-Accept.
If
On 12/20/2012 05:14 PM, rosect...@yahoo.com wrote:
It is noticed that some VSAs are sent with Access-Challenge but not with
Access-Accept when PEAP is used.
Is there a way to configure the server such that those attributes are
sent with Access-Accept?
use_tunneled_reply = yes under the peap
Hi David,
thanks for your quick reply.
On 12/20/2012 03:35 PM, David Peterson wrote:
You follow the dictionary in the order set inside of it.
The dictionary:
ATTRIBUTE WiMAX-QoS-Descriptor29 tlv
ATTRIBUTE WiMAX-QoS-Id29.1
Sven Tantau wrote:
The dictionary:
Yes... there's no need to re-post it here. We all have access to it.
Since I get good results if I use only one QOS profile, I assume that I
can skip attributes and that I'm not required to use them all.
(Please correct me if I'm wrong.)
You don't
Here is an example of two flows, one for management of the CPE and one for
data:
Alvarion-R3-IF-Name += MGMT_PrivateIP
Alvarion-PDFID += 1
WiMAX-Packet-Data-Flow-Id += 1
WiMAX-Service-Data-Flow-Id += 1
WiMAX-Direction += 3
WiMAX-Transport-Type+=
Yeah he is trying to use VPLS with an Alvarion ASN. He is going to have to
use the master branch.
David
-Original Message-
From:
freeradius-users-bounces+davidp=wirelessconnections@lists.freeradius.org
[mailto:freeradius-users-bounces+davidp=wirelessconnections.net@lists.freera
Hi,
In addition, if you're seeing the VSAs in Access-Challenge, it's
most likely because you're returning them in the authorize second.
Instead, consider returning them in the post-auth section of the
inner-tunnel server, combined with the config above.
dont forget RFC 2865
I am using seagull to send messages to freeradius. seagull and freeradius are
in same machine.
I am not clear about how to set password in nas?? Please help.
Thanks Regards,
Yashaswini | Prod Engg | Tech Mahindra Ltd.
9 / 7 Hosur Road, Bangalore - 560029, India.
(Office: +91 80 40243000, Extn:
I am using seagull to send messages to freeradius . Is there any place I need
to set shared secret in seagull also .
I have installed seagull in the same machine as freeradius.
Thanks Regards,
Yashaswini | Prod Engg | Tech Mahindra Ltd.
9 / 7 Hosur Road, Bangalore - 560029, India.
(Office: +91
On 12/20/2012 08:14 PM, Alan DeKok wrote:
I expected freeradius to see that WiMAX-QoS-Id is an element of a new
tlv. And then create a new WiMAX-QoS-Descriptor for it. (Instead of
combining the data for the two QoS profiles into one WiMAX-QoS-Descriptor.)
IIRC, it should create two
20 matches
Mail list logo
