PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001618PacketFencedocpublic2012-12-17 06:092015-02-18 10:59
Reporterxinity 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version3.5.1 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001618: Aruba IAP-93 Packetfence integration how to
DescriptionThis little documentation describe how to use Aruba/DELL IAP-93 with Packetfence.
Steps To Reproduce
Additional Information================================================================================

0°) We define :
VLANID 1: Production
VLANID 4: Registration

1°) add your packetfence instance to your configuration:
-----
wlan auth-server packetfence
 ip [IP of your packetfence]
 port 1812
 acctport 1813
 timeout 10
 retry-count 5
 key [your radius key]
 nas-ip [IP of your Aruba Virtual Controller]
 rfc3576
-----

2°) add dynamic vlan rules and mac auth to your ssid profile
-----
wlan ssid-profile [my SSID Name]
 index 0
 type employee
 essid [my ESSID Name]
 wpa-passphrase [your wpa-passphrase]
 opmode wpa2-psk-aes
 max-authentication-failures 0
 vlan 1
 auth-server packetfence
 set-vlan Tunnel-Private-Group-Id contains 1 1
 set-vlan Tunnel-Private-Group-Id contains 4 4
 rf-band all
 captive-portal disable
 mac-authentication
 dtim-period 1
 inactivity-timeout 1000
 broadcast-filter none
 radius-reauth-interval 5
 dmo-channel-utilization-threshold 90
-----

note: this is working as well with IAP-105.
note2: Cli changes in configuration is not supported by aruba.
note3: CoA doesn't seem to be working as of the latest Aruba Firmware, even if rfc3576 support is activated.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-12-17 06:09xinityNew Issue
2012-12-17 15:54dwuelfrathNote Added: 0003285
2012-12-18 04:49xinityNote Added: 0003286
2012-12-19 07:27deneme2Note Added: 0003287
2012-12-19 07:28deneme2Note Added: 0003288
2012-12-19 08:42xinityNote Edited: 0003286
2015-02-18 10:59lmunroNote Added: 0003931
2015-02-18 10:59lmunroStatusnew => closed

Notes
(0003285)
dwuelfrath   
2012-12-17 15:54   
We usually ask, if possible, to fork the project on GitHub (https://github.com/inverse-inc/packetfence [^]) and do the modifications. Once done, open up a pull-request.
It is way easier to keep track of code change ;)

Cheers!
(0003286)
xinity   
2012-12-18 04:49   
(edited on: 2012-12-19 08:42)
i though it was only for code changes :)
anyway i'll do as advised and open a pull-request for the doc changes.
Cheers!

Pull Request done
(0003287)
deneme2   
2012-12-19 07:27   
sfds
(0003288)
deneme2   
2012-12-19 07:28   
yapsana olumm
(0003931)
lmunro   
2015-02-18 10:59   
Obsolete bug tracker entries.
PF 4 introduced changes that either make these irrelevant or impossible to reproduce.

New issues are moving to github issues.