Opened 4 weeks ago

Closed 4 weeks ago

#1337 closed request (fixed)

DHCP on ietf-hotel swisshotel

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

Description

I was not receiving addresses from DHCP on ietf-hotel in swisshotel room
3561.  I do not know if you're using SLAAC or DHCPv6, but also not rx'g
a v6 address.

It worked earlier today, though it was slow.  And began working again as
I was writing to open a ticket.  I'm not sure how long it was unresponsive;
perhaps 15 minutes.

Change history (4)

comment:1 Changed 4 weeks ago by Sean Croghan

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

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.

Based roughly on the times this was during the boot up process of the systems and possibly would explain your experience.

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

We are using SLAAC.

Sean

comment:2 in reply to:  2 ; Changed 4 weeks ago by heas@…

Sun, Nov 17, 2019 at 01:51:49PM +0000, john heasley:
> I was not receiving addresses from DHCP on ietf-hotel in swisshotel room
> 3561.  I do not know if you're using SLAAC or DHCPv6, but also not rx'g
> a v6 address.
> 
> It worked earlier today, though it was slow.  And began working again as
> I was writing to open a ticket.  I'm not sure how long it was unresponsive;
> perhaps 15 minutes.

To add to this, from the breakfast discussion, the swisshotel SSID also has
trouble returning an address for me, while Warren said that it worked
immediately for him when ietf-hotel did not.

Just 2 minutes ago, I was not receiving a v4 address from either.  I did
have a v6 address - actually 2:

2001:67c:1232:144:c2b:37a1:b7ee:3e38
2001:67c:1232:144:20a0:7ed6:6b70:91af

when I did receive a v4 address, 31.133.149.168, the default router .1
was NOT pingable, but .4 was.  eventually .1 became pingable.

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

Mon, Nov 18, 2019 at 12:26:53AM +0000, john heasley:
> Sun, Nov 17, 2019 at 01:51:49PM +0000, john heasley:
> > I was not receiving addresses from DHCP on ietf-hotel in swisshotel room
> > 3561.  I do not know if you're using SLAAC or DHCPv6, but also not rx'g
> > a v6 address.
> > 
> > It worked earlier today, though it was slow.  And began working again as
> > I was writing to open a ticket.  I'm not sure how long it was unresponsive;
> > perhaps 15 minutes.
> 
> To add to this, from the breakfast discussion, the swisshotel SSID also has
> trouble returning an address for me, while Warren said that it worked
> immediately for him when ietf-hotel did not.
> 
> Just 2 minutes ago, I was not receiving a v4 address from either.  I did
> have a v6 address - actually 2:
> 
> 2001:67c:1232:144:c2b:37a1:b7ee:3e38
> 2001:67c:1232:144:20a0:7ed6:6b70:91af
> 
> when I did receive a v4 address, 31.133.149.168, the default router .1
> was NOT pingable, but .4 was.  eventually .1 became pingable.

It just switched to swisshotel again:

ping: sendto: No route to host
ping: sendto: No route to host
<switch backt o ietf-hotel>
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
64 bytes from 31.133.144.1: icmp_seq=14 ttl=64 time=588.757 ms
Request timeout for icmp_seq 15
	...

Request timeout for icmp_seq 57
64 bytes from 31.133.144.1: icmp_seq=58 ttl=64 time=3.636 ms
	...

and it switched again while making tea.  I am not finding any relevant
logs - macos.  Maybe logs will appear in Console.app - which is terrible.

Is there perhaps some device with a small MAC table?

I'm going to use swisshotel for a while to see if it is more stable.

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.