ArubaOS and Controllers

Reply
Frequent Contributor I
Posts: 97
Registered: ‎08-19-2008

WPA/DHCP issue

We are still having IP address issues with PioneerNet, our WPA network, using Radius and an external DHCP server. Some users get self-assigned IPs even after authentication. Please look at the logs below from our Radius server and see if you have any ideas. Do you guys think this might be related to roaming somehow?, where Aruba is trying to maintain the user's IP address (if you look at the last log, that same user an hour later gets the same IP address in the UTS Bldg as when connected in DCB, though this buildings (APs) belong to different groups, with different VAPs that have different vlans attached, so the user should have gotten a different IP)
Not sure if this is relevant information, but I have Fast Roaming, VLAN Mobility, and Mobile IP enabled in the VAPs.
Here are the logs from the Radius server for the same user.
There is something strange with some of them. The following log entries show one system authenticating from 3 different IP addresses within seconds of each other:
Wed Aug 20 15:05:12 2008
NAS-IP-Address = 130.253.21.26
Acct-Status-Type = Start
User-Name = "870200998"
NAS-Port = 4431
NAS-Port-Type = Wireless-IEEE-802-11
Framed-IP-Address = 169.254.208.185
Calling-Station-Id = "0021E943F2C8"
Called-Station-Id = "000B860A1D80"
Acct-Session-Id = "870200990021E943F2C8-4232"
Acct-Authentic = 0
Acct-Delay-Time = 0
Aruba-Essid-Name = "PioneerNet"
Aruba-Location-Id = "AP7-DCB"
Aruba-User-Role = "authenticated"
Aruba-User-Vlan = 0
Timestamp = 1219266312
Wed Aug 20 15:05:13 2008
NAS-IP-Address = 130.253.21.26
Acct-Status-Type = Start
User-Name = "870200998"
NAS-Port = 4431
NAS-Port-Type = Wireless-IEEE-802-11
Framed-IP-Address = 10.139.66.72
Calling-Station-Id = "0021E943F2C8"
Called-Station-Id = "000B860A1D80"
Acct-Session-Id = "870200990021E943F2C8-4233"
Acct-Authentic = 0
Acct-Delay-Time = 0
Aruba-Essid-Name = "PioneerNet"
Aruba-Location-Id = "AP7-DCB"
Aruba-User-Role = "authenticated"
Aruba-User-Vlan = 0
Timestamp = 1219266313
Wed Aug 20 15:05:13 2008
NAS-IP-Address = 130.253.21.26
Acct-Status-Type = Start
User-Name = "870200998"
NAS-Port = 4431
NAS-Port-Type = Wireless-IEEE-802-11
Framed-IP-Address = 130.253.56.86
Calling-Station-Id = "0021E943F2C8"
Called-Station-Id = "000B860A1D80"
Acct-Session-Id = "870200990021E943F2C8-4234"
Acct-Authentic = 0
Acct-Delay-Time = 0
Aruba-Essid-Name = "PioneerNet"
Aruba-Location-Id = "AP7-DCB"
Aruba-User-Role = "authenticated"
Aruba-User-Vlan = 0
Timestamp = 1219266313
The logs show similar gyrations as long as the system is in DCB.
However later it connects, apparently with out problem, in UTS, yet this should have been a different IP address because AP7-UTS belongs to a different group with a different VAP (and different vlan).
Wed Aug 20 16:50:31 2008
NAS-IP-Address = 130.253.21.26
Acct-Status-Type = Start
User-Name = "870200998"
NAS-Port = 4301
NAS-Port-Type = Wireless-IEEE-802-11
Framed-IP-Address = 130.253.56.86
Calling-Station-Id = "0021E943F2C8"
Called-Station-Id = "000B860A1D80"
Acct-Session-Id = "870200990021E943F2C8-43F6"
Acct-Authentic = 0
Acct-Delay-Time = 0
Aruba-Essid-Name = "PioneerNet"
Aruba-Location-Id = "AP7-UTS"
Aruba-User-Role = "authenticated"
Aruba-User-Vlan = 0
Timestamp = 1219272631
Thanks!
Marcelo
Marcelo Lew
Wireless Network Architect-Engineer
University of Denver
Search Airheads
Showing results for 
Search instead for 
Did you mean: