Louis:

I updated the ArubeSwitch.pm module and re-ran the test after I switched the AP 
to the Aruba Switch type in the config.

I now have a new error ... so thats progress ... right?

Sep 30 17:48:15 httpd.webservices(23257) WARN: [10.11.40.252] Unable to perform 
RADIUS CoA-Request: Can't locate object method "deauth_source_ip" via package 
"pf::Switch::ArubaSwitch" at /usr/local/pf/lib/pf/Switch/ArubaSwitch.pm line 
238. (pf::Switch::ArubaSwitch::__ANON__)


Jake Sallee
Godfather of Bandwidth
System Engineer
University of Mary Hardin-Baylor
WWW.UMHB.EDU

900 College St.
Belton, Texas
76513

Fone: 254-295-4658
Phax: 254-295-4221
________________________________
From: Durand fabrice [fdur...@inverse.ca]
Sent: Wednesday, September 30, 2015 5:07 PM
To: packetfence-devel@lists.sourceforge.net
Subject: Re: [PacketFence-devel] Testing Aruba 205H in PF 5.3.1

Hi Jakes,

can you try with Aruba Switches module ?
https://github.com/inverse-inc/packetfence/blob/devel/lib/pf/Switch/ArubaSwitch.pm

Regards
Fabrice



Le 2015-09-30 17:38, Sallee, Jake a écrit :

Louis:

I did as you suggested and got the latest version of the aruba module, but no 
luck : (

Here is the config:
[10.11.40.252] ## This is the IP of the virtual controller##
type=Aruba
radiusSecret=[REDACTED]
guestVlan=112
defaultRole=default
defaultVlan=111
deauthMethod=RADIUS
AccessListMap=N
gamingRole=gaming
type=Aruba::Controller_200
guestRole=guest
gamingVlan=112

Here is the error:

Sep 30 16:24:29 httpd.webservices(2389) WARN: Until CoA is implemented we will 
bounce the port on VLAN re-assignment traps for MAC-Auth 
(pf::Switch::handleReAssignVlanTrapForWiredMacAuth)

I checked on the method referenced in the error and the comments made it sound 
like RADIUS CoA is not supported for wired Mac-Auth on any switch ...

=================================
=item handleReAssignVlanTrapForWiredMacAuth
Called when a ReAssignVlan trap is received for a switch-port in Wired MAC 
Authentication.
Default behavior is to bounce the port
=cut

sub handleReAssignVlanTrapForWiredMacAuth {
    my ($this, $ifIndex, $mac) = @_;
    my $logger = Log::Log4perl::get_logger(ref($this));

    # TODO extract that behavior in a method call in pf::vlan so it can be 
overridden easily

    $logger->warn("Until CoA is implemented we will bounce the port on VLAN 
re-assignment traps for MAC-Auth");

    # TODO perform CoA instead (when implemented)
    # actually once CoA will be implemented, we should consider offering the 
same option to users
    # as we currently do with port-security and VoIP which is bounce or not 
bounce and suffer consequences
    # this should be a choice exposed in configuration and not hidden in code
    $this->bouncePort($ifIndex);
}
=================================

Am I barking up the wrong tree here?  Should I be looking into the radius 
module?


Jake Sallee

Godfather of Bandwidth

System Engineer

University of Mary Hardin-Baylor

WWW.UMHB.EDU<http://WWW.UMHB.EDU>



900 College St.

Belton, Texas

76513



Fone: 254-295-4658

Phax: 254-295-4221








From: Louis Munro [lmu...@inverse.ca<mailto:lmu...@inverse.ca>]

Sent: Wednesday, September 30, 2015 3:11 PM

To: 
packetfence-devel@lists.sourceforge.net<mailto:packetfence-devel@lists.sourceforge.net>

Subject: Re: [PacketFence-devel] Testing Aruba 205H in PF 5.3.1





Hi Jake,



Could you post both your config for the Aruba in conf/switches.conf and the 
error in the logs?



You may want to avail yourself of the latest version of the Aruba module at :
https://raw.githubusercontent.com/inverse-inc/packetfence/devel/lib/pf/Switch/Aruba.pm






Regards,






--

Louis Munro

lmu...@inverse.ca<mailto:lmu...@inverse.ca>  ::  
www.inverse.ca<http://www.inverse.ca>

+1.514.447.4918 x125  :: +1 (866) 353-6153 x125

Inverse inc. :: Leaders behind SOGo (www.sogo.nu<http://www.sogo.nu>) and 
PacketFence (www.packetfence.org<http://www.packetfence.org>)





On Sep 30, 2015, at 16:07 , Sallee, Jake 
<jake.sal...@umhb.edu><mailto:jake.sal...@umhb.edu>
 wrote:

I
 need to test the Aruba 205H to see if it will work with PF 5.3.1, but the 
RADIUS module is throwing the switch unsupported error.










------------------------------------------------------------------------------
_______________________________________________
PacketFence-devel mailing list
PacketFence-devel@lists.sourceforge.net<mailto:PacketFence-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/packetfence-devel



------------------------------------------------------------------------------
_______________________________________________
PacketFence-devel mailing list
PacketFence-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-devel

Reply via email to