Works here just fine. Once you've created the correctly formatted value for the
radius attribute FR displays it as an integer but whatever happens in the
background the HP switch just does its stuff
Rgds
A
Sent from my iPhone
On 6 Aug 2013, at 00:39, Andy a...@brandwatch.com wrote:
Hello,
On 7 Aug 2013, at 10:56, Alex Sharaz alex.sha...@york.ac.uk wrote:
Works here just fine. Once you've created the correctly formatted value for
the radius attribute FR displays it as an integer but whatever happens in the
background the HP switch just does its stuff
Yes the HP switch
Arran Cudbard-Bell wrote:
I'm honestly not entirely sure why the freeradius dictionary has the
attribute as an unsigned int
That's what the RFCs say. And the server doesn't really have a way of
packing arbitrary structures from attributes.
Alan DeKok.
-
List info/subscribe/unsubscribe?
On 7 Aug 2013, at 13:46, Alan DeKok al...@deployingradius.com wrote:
Arran Cudbard-Bell wrote:
I'm honestly not entirely sure why the freeradius dictionary has the
attribute as an unsigned int
That's what the RFCs say. And the server doesn't really have a way of
packing arbitrary
Thank you everyone so much :)
Wow, what a great list :D
OK. First, you're not doing PPP, remove the default entries in the
users file for Framed-Protocol and Framed-Compression.
I have commented this out now.
And again thank you for your wireshark capture, and perfect
explanations of the
Hi, yes thank you, that is the guide I have been following..
And as that guide highlights the switch needs a 'bit string', not a
decimal number;
The value of Egress-VLANID is a bit string, the first 8 bits specify
whether the VLAN is tagged or untagged and must be either 0x31 (tagged)
or 0x32
Ahh,
No. The HP switch does not care that FreeRADIUS displayed (but later
encoded correctly) your hex string as an integer.
It does care that you don't seem to understand how to convert decimal
numbers to hex and are actually specifying VLAN 18 tagged, which
probably doesn't exist if you're
It still doesn't work :(
Sorry but I have been working on RFC 4675 for a long time before I
emailed this list, which is why I was a bit short in my first reply
(sorry) and jumped the gun before reading all of your email. I /really/
have trawled every page I can find..
I have changed
On 6 Aug 2013, at 10:50, Andy a...@brandwatch.com wrote:
Hi, yes thank you, that is the guide I have been following..
And as that guide highlights the switch needs a 'bit string', not a decimal
number;
The value of Egress-VLANID is a bit string, the first 8 bits specify whether
the VLAN
HPO switch debug;
0049:03:34:00.18 MAC mWebAuth:Port: 29 MAC: 080027-e4b2cd new client
detected on vid: 11.
0049:03:34:00.18 MAC mWebAuth:Port: 29 MAC: 080027-e4b2cd RADIUS CHAP
authentication started, session: 2985.
0049:03:34:00.20 MAC mWebAuth:Port: 29 MAC: 080027-e4b2cd vid
Hello,
This is my first post here so please excuse any missed etiquette.
I have read through the wiki's and googled a lot and not found anything.
I have been trying configure our switch ports (HP 2910al) with Tagged
VLANs via Egress-VLANID and Egress-VLAN-Name.
The Radius backend is
On 5 Aug 2013, at 23:39, Andy a...@brandwatch.com wrote:
Hello,
This is my first post here so please excuse any missed etiquette.
I have read through the wiki's and googled a lot and not found anything.
12 matches
Mail list logo