(RADIATOR) Simple conditional Reply item

Hugh Irvine hugh at open.com.au
Wed Mar 7 16:09:28 CST 2007


Hello Peter -

There should be no line between the username and the reply item:


someuser
	Aruba-User-Vlan = 3

DEFAULT
	Aruba-User-Vlan = 6


My testing here with the above gives this:


Radiator-3.16 hugh$ perl radpwtst -noacct -user someuser
sending Access-Request...
Thu Mar  8 09:06:11 2007: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 50054 ....
Code:       Access-Request
Identifier: 191
Authentic:  1234567890123456
Attributes:
         User-Name = "someuser"
         Service-Type = Framed-User
         NAS-IP-Address = 203.63.154.1
         NAS-Identifier = "203.63.154.1"
         NAS-Port = 1234
         Called-Station-Id = "123456789"
         Calling-Station-Id = "987654321"
         NAS-Port-Type = Async
         User-Password = <159><249>:<201><175> 
\<4><246><188>8<9><160><216>}x<153>

Thu Mar  8 09:06:11 2007: DEBUG: Handling request with Handler 'Realm='
Thu Mar  8 09:06:11 2007: DEBUG:  Deleting session for someuser,  
203.63.154.1, 1234
Thu Mar  8 09:06:11 2007: DEBUG: Handling with Radius::AuthFILE:
Thu Mar  8 09:06:11 2007: DEBUG: Reading users file ./users.vlan
Thu Mar  8 09:06:11 2007: DEBUG: Radius::AuthFILE looks for match  
with someuser [someuser]
Thu Mar  8 09:06:11 2007: DEBUG: Radius::AuthFILE ACCEPT: : someuser  
[someuser]
Thu Mar  8 09:06:11 2007: DEBUG: AuthBy FILE result: ACCEPT,
Thu Mar  8 09:06:11 2007: DEBUG: Access accepted for someuser
Thu Mar  8 09:06:11 2007: DEBUG: Packet dump:
*** Sending to 127.0.0.1 port 50054 ....
Code:       Access-Accept
Identifier: 191
Authentic:  1234567890123456
Attributes:
         Aruba-User-Vlan = 3

OK
titi:/Local/src/Radiator/Radiator-3.16 hugh$ perl radpwtst -noacct - 
user some
sending Access-Request...
Thu Mar  8 09:06:19 2007: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 50055 ....
Code:       Access-Request
Identifier: 199
Authentic:  1234567890123456
Attributes:
         User-Name = "some"
         Service-Type = Framed-User
         NAS-IP-Address = 203.63.154.1
         NAS-Identifier = "203.63.154.1"
         NAS-Port = 1234
         Called-Station-Id = "123456789"
         Calling-Station-Id = "987654321"
         NAS-Port-Type = Async
         User-Password = <159><249>:<201><175> 
\<4><246><188>8<9><160><216>}x<153>

Thu Mar  8 09:06:19 2007: DEBUG: Handling request with Handler 'Realm='
Thu Mar  8 09:06:19 2007: DEBUG:  Deleting session for some,  
203.63.154.1, 1234
Thu Mar  8 09:06:19 2007: DEBUG: Handling with Radius::AuthFILE:
Thu Mar  8 09:06:19 2007: DEBUG: Radius::AuthFILE looks for match  
with some [some]
Thu Mar  8 09:06:19 2007: DEBUG: Radius::AuthFILE REJECT: No such  
user: some [some]
Thu Mar  8 09:06:19 2007: DEBUG: Radius::AuthFILE looks for match  
with DEFAULT [some]
Thu Mar  8 09:06:19 2007: DEBUG: Radius::AuthFILE ACCEPT: : DEFAULT  
[some]
Thu Mar  8 09:06:19 2007: DEBUG: AuthBy FILE result: ACCEPT,
Thu Mar  8 09:06:19 2007: DEBUG: Access accepted for some
Thu Mar  8 09:06:19 2007: DEBUG: Packet dump:
*** Sending to 127.0.0.1 port 50055 ....
Code:       Access-Accept
Identifier: 199
Authentic:  1234567890123456
Attributes:
         Aruba-User-Vlan = 6



If you are having a problem I will need to see the configuration file  
you are using and a trace 4 debug showing what is happening.

regards

Hugh


On 7 Mar 2007, at 21:59, Peter Bates wrote:

>
> Hi again...
>
>> On 06/03/07 at 21:29, Hugh Irvine <hugh at open.com.au> wrote:
>> Try this:
>>
>> <Handler TunnelledByPEAP=1>
>>
>> 	RewriteUsername       s/^([^@]+).*/$1/
>> 	RejectHasReason
>>
>> 	AuthByPolicy ContinueWhileAccept
>>
>> 	AuthBy TestUP
>>
>>      <AuthBy FILE>
>>                Filename %D/users.vlans
>>       <AuthBy>
>>
>> </Handler>
>
> Having the following in users.vlans (as you previously mentioned)
>
> username
>                     Aruba-User-Vlan = x
>
> DEFAULT
>                     Aruba-User-Vlan = y
>
> where I presume the line between the username and
> the Reply-item is significant, authentication stops working.
>
> The 'AuthBy TestUP' is a group:
>
> <AuthBy GROUP>
> Identifier TestUP
> AuthBy its2
> AuthBy its1
> </AuthBy>
>
> and then 'its1' and 'its2' are <AuthBy LDAP2> sections,
> using LDAP to authenticate against eDirectory.
>
> Am I missing something obvious?
>
>
> -- 
>
> ---------------------------------------------------------------------- 
> ----------------------------->
> Peter Bates, Systems Support Officer, IT Services.
> London School of Hygiene & Tropical Medicine.
> Telephone:0207-958 8353 / Fax: 0207- 636 9838
>
> --
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.



NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/ 
radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list