Is that the name of the VLAN as defined on that particular controller?
radius and/or dot1x traces on the controller itself should help you
determine exactly what's going on too.
An AuthBy FILE containing your usernames with the proper VLAN reply
attribute might be an easier way to go than a hook, but there's more than
one way to do it.
Andrew Clark
On Mon, Jun 20, 2011 at 7:13 PM, Zod Mansour <z...@reachlocal.com> wrote:
> Hi,
> Trying to get Trapeze MX8 working with radiator. Juniper says they
> need to receive 'vlan' and the radiator is not sending them that.
> They are requesting a vendor specific attribute att: 26 vendor code
> 14525. I was looking in the dictionary and saw:
>
> # Trapeze Networks dictionary
> #
> VENDOR Trapeze 14525
> VENDORATTR 14525 TRPZ-VLAN-Name 1 string
> VENDORATTR 14525 Trapeze-VLAN-Name 1 string
>
>
> I have a script that adds attribute:
>
> PostSearchHook file:"/etc/radiator/override_default_vlan.pl"
>
>
> sub {
> open(FILE,"/etc/radiator/priv-users");
> my @privUsers = <FILE>;
> close FILE;
> my @userName = $_[4]->get('uid');
> my $userName = @userName[0];
> my $privUser;
>
> foreach $privUser (@privUsers) {
> chomp($privUser);
> if ($userName eq $privUser) {
>
> $_[3]->get_reply->add_attr('Trapeze-VLAN-Name','Techops');
> return;
> };
> };
> $_[3]->get_reply->add_attr('TRPZ-VLAN-Name', 'Corp');
> }
>
>
> I have tried the 2 versions of vlan-name but the Trapeze does not
> receive the vlan.
> Any suggestions?
>
>
> thx,
> Zod
>
> _______________________________________________
> radiator mailing list
> radiator@open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
>
_______________________________________________
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
