Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#45 closed request (wontfix)

Randy and the Wireless

Reported by: randy@… Owned by: joelja@…
Priority: minor Milestone:
Component: wireless Keywords:
Cc: My Current Location: back left of plenary
My MAC Address: 00:1e:52:70:b6:36 My OS: leopard

Description

back left corner of plenary. ietf.1x. got full strength on chan 6, but no dhcp. switched to ietf-a chan 44 and fine.

Change history (9)

comment:1 Changed 10 years ago by Bill Fenner

Reporter: changed from anonymous to randy@…

I think Randy was assocaiated with bssid 00:1a:1e:8e:9b:74 when on .1x and is now on bssid 00:1a:1e:8e:81:f0 (ap 00:1a:1e:c0:e8:1e).

I don't know how to find the ap for a bssid that nobody is associated with, but 9b:74 is far enough away from 81:f0 that I suspect that this reassociation had nothing to do with the different between .1x and -a per se but just a switch of access points.

comment:2 Changed 10 years ago by llynch@…

Bill -

Find the bssid in netdisco, get the IP and match it the Karens
AP deployment spreedsheet -

  • Lucy

comment:3 in reply to:  2 Changed 10 years ago by Bill Fenner

Replying to llynch@civil-tongue.net:

Find the bssid in netdisco, get the IP and match it the Karens
AP deployment spreedsheet -

Karen's deployment spreadsheet has MAC addresses of the APs - but I don't know how to get from the BSSID to the AP MAC address when there are no users. When there are users, I can use the Aruba search page. Maybe there's another Aruba search page that I haven't found yet.

comment:5 Changed 10 years ago by Bill Fenner

That does let me search for and find the BSSID but all it reports back is the BSSID - no AP name, no AP mac address, as far as I can tell. :-(

comment:6 Changed 10 years ago by llynch@…

This is where i took the ip and mapped back to Karens mac add

... sorry it took my old brain so long to re-construct

comment:7 Changed 10 years ago by Bill Fenner

I must be accidentally using a different report. The pieces of info that it gives me are:

Aruba Networks 802.11a 52 ietf.1x 00:1a:1e:8e:9b:74 0 18:42:58 7/30/2008 up

(That's the BSSID, not the IP address or the AP mac).

comment:8 Changed 10 years ago by joelja@…

Resolution: wontfix
Status: newclosed

incosistant behavior with mac osX 10.5 noted.

client thinks it's contect to controller

controller things client is connected

packets do not flow at l2 from wireless side of vlan to wired.

spent some time looking at this behavior this morning.

could be the arubas implementation of re-authatication or the mac's supplicant.

disabling opportunistic key caching on the controller might fix this at the expense of making 802.1x roaming between aps more expensive.

comment:9 Changed 8 years ago by (none)

Milestone: IETF Week ieft 72

Milestone IETF Week ieft 72 deleted

Note: See TracTickets for help on using tickets.