Opened 4 weeks ago

Closed 4 weeks ago

#1336 closed request (fixed)

WiFi not working in swissotel room 2050

Reported by: job@… Owned by: Sean Croghan
Priority: tbd Milestone: ietf-106
Component: hotel Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Heya noc,

It appears the internet access in room 2050 isn’t working at all. I get
DHCP, but no replies to ARP requests from the default gateway.

Is there a known issue at the moment?

Kind regards,

Job

Change history (4)

comment:1 in reply to:  1 ; Changed 4 weeks ago by job@…

Update: I can ping the default gateway, but packets don’t seem to make it
past 31.133.144.1

On Sun, Nov 17, 2019 at 21:29 IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1336: WiFi not working in swissotel room 2050
> ---------------------------+-----------------------------------
>       Reporter:  job@…     |                Owner:  < default >
>           Type:  request   |               Status:  new
>       Priority:  tbd       |            Milestone:  ietf-106
>      Component:  incoming  |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+-----------------------------------
>  {{{
>  Heya noc,
>
>  It appears the internet access in room 2050 isn’t working at all. I get
>  DHCP, but no replies to ARP requests from the default gateway.
>
>  Is there a known issue at the moment?
>
>  Kind regards,
>
>  Job
>  }}}
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1336>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:2 Changed 4 weeks ago by Sean Croghan

Component: incominghotel
Owner: changed from < default > to Sean Croghan
Status: newassigned

Job

Tonight at 21:10 the MDF lost power; our systems notified us of this failure. We verified the outage and had hotel engineering alerted by 21:18. We worked with engineering to restore power to the rack —services were restored just before 22:00.

Our apologies on behalf of the hotel for the disruption in service, and thanks for the patience.

If you are still having issues please respond to this ticket and we will investigate.

Sean

comment:3 in reply to:  3 ; Changed 4 weeks ago by job@…

ouch, that sounds suboptimal :-)

things seem to work now!

thanks for getting back to me - have a good night


On Sun, Nov 17, 2019 at 2:47 PM IETF Tickets/NOC
<tickets@meeting.ietf.org> wrote:
>
> #1336: WiFi not working in swissotel room 2050
> --------------------------+------------------------------------
>       Reporter:  job@…    |                Owner:  Sean Croghan
>           Type:  request  |               Status:  assigned
>       Priority:  tbd      |            Milestone:  ietf-106
>      Component:  hotel    |           Resolution:
>       Keywords:           |  My Current Location:
> My MAC  Address:          |                My OS:
> --------------------------+------------------------------------
> Changes (by Sean Croghan):
>
>  * owner:  < default > => Sean Croghan
>  * status:  new => assigned
>  * component:  incoming => hotel
>
>
> Comment:
>
>  Job
>
>  Tonight at 21:10 the MDF lost power; our systems notified us of this
>  failure. We verified the outage and had hotel engineering alerted by
>  21:18. We worked with engineering to restore power to the rack —services
>  were restored just before 22:00.
>
>  Our apologies on behalf of the hotel for the disruption in service, and
>  thanks for the patience.
>
>  If you are still having issues please respond to this ticket and we will
>  investigate.
>
>  Sean
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1336#comment:2>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:4 Changed 4 weeks ago by odonoghue@…

Resolution: fixed
Status: assignedclosed

As you may be aware from Sean’s email to the 106all mailing list, we have had a number of issues with the hotel network. Changes have been implemented, and we believe the network is now stable (unfortunately without IPv6 service). So, I am going to close this ticket at this point. If you have additional issues you encounter, please feel free to reopen this ticket or create a new one (if the issues is sufficiently different). Thanks!

Note: See TracTickets for help on using tickets.