Opened 4 years ago

Closed 4 years ago

Last modified 5 weeks ago

#655 closed defect (fixed)

Problem on ietf-a.1x

Reported by: bob.hinden@… Owned by: cdoyle@…
Priority: minor Milestone: ietf-088
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

I am in my room on 32nd floor, and am connect to ietf-a.1x.  While I get addresses, the connection doesn't pass traffic.  Info on the connection below.

I switched to Hyatt-Vancouver ssid and then back to ietf-a.1x, it started working :-(

Bob


  Current Network Information:
  ietf-a.1x:
  PHY Mode:	802.11n
  BSSID:	00:17:df:a2:aa:d3
  Channel:	36
  Country Code:	CA
  Network Type:	Infrastructure
  Security:	WPA2 Enterprise
  Signal / Noise:	-78 dBm / -91 dBm
  Transmit Rate:	78
  MCS Index:	12

Attachments (1)

signature.asc (496 bytes) - added by bob.hinden@… 4 years ago.
Added by email2trac

Download all attachments as: .zip

Change history (6)

comment:1 Changed 4 years ago by llynch@…

Owner: changed from llynch@… to cdoyle@…
Status: newassigned

comment:2 Changed 4 years ago by cdoyle@…

Component: incomingwireless
Priority: tbdminor
Resolution: not broken
Status: assignedclosed
Type: requestdefect

Bob,

The WAP's you are connecting to are 2 floors above you. Please connect to the Hyatt_Vancouver SSID from your room. I'm guessing you are experiencing wifi connection issues created by the materials between you and the WAP's 2 floors up and that these issues are preventing the certificate authentication required for 802.1x and/or other oddness. There's not really anything we can do as we are only beaconing the IETF SSID's from our hardware in the meeting space. The Hyatt_Vancouver wifi is being serviced by our uplink on the backend, so you should be sacrificing on speed by switching over. And I know, no encryption, which is a bummer, but it's the best we can do with the hotel's WAP's.

C

comment:3 Changed 4 years ago by bob.hinden@…

Resolution: not broken
Status: closedreopened
Thanks, that all makes sense.

Bob

On Nov 6, 2013, at 4:24 PM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:

> #655: Problem on ietf-a.1x
> -------------------------------+----------------------------------
>      Reporter:  bob.hinden@…  |                Owner:  cdoyle@…
>          Type:  defect        |               Status:  closed
>      Priority:  minor         |            Milestone:  ietf-88
>     Component:  wireless      |           Resolution:  not broken
>      Keywords:                |  My Current Location:
> My MAC  Address:               |                My OS:
> -------------------------------+----------------------------------
> Changes (by cdoyle@…):
> 
> * priority:  tbd => minor
> * resolution:   => not broken
> * status:  assigned => closed
> * component:  incoming => wireless
> * type:  request => defect
> 
> 
> Comment:
> 
> Bob,
> 
> The WAP's you are connecting to are 2 floors above you. Please connect to
> the Hyatt_Vancouver SSID from your room. I'm guessing you are experiencing
> wifi connection issues created by the materials between you and the WAP's
> 2 floors up and that these issues are preventing the certificate
> authentication required for 802.1x and/or other oddness. There's not
> really anything we can do as we are only beaconing the IETF SSID's from
> our hardware in the meeting space. The Hyatt_Vancouver wifi is being
> serviced by our uplink on the backend, so you should be sacrificing on
> speed by switching over. And I know, no encryption, which is a bummer, but
> it's the best we can do with the hotel's WAP's.
> 
> C
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/655#comment:2>
> IETF Meeting/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting - NOC pages

signature.asc

Changed 4 years ago by bob.hinden@…

Attachment: signature.asc added

Added by email2trac

comment:4 Changed 4 years ago by cdoyle@…

Resolution: fixed
Status: reopenedclosed

comment:5 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-88ietf-088

Milestone renamed

Note: See TracTickets for help on using tickets.