Opened 4 weeks ago

Closed 4 weeks ago

#1339 closed request (fixed)

intermittent failure to receive functional DHCP lease on ietf-hotel in swissotel guest room

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

Description

Hi all,

This morning (Sun 17 Nov 2019 12:57:28 PM PST) in the swissotel guest
rooms, on ssid 'ietf-hotel' I find my debian system reporting that I am
successfully associated but my tools report that I only get ipv6 service:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
kaduk@prolepsis:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
122: wlp58s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 30:52:cb:e7:7c:45 brd ff:ff:ff:ff:ff:ff
    inet6 2001:67c:1232:144:9f96:e9a0:3a6f:8de/64 scope global dynamic noprefixroute 
       valid_lft 2592000sec preferred_lft 2592000sec
    inet6 fe80::95ba:c96b:d420:7871/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
kaduk@prolepsis:~$ ping6 www.google.com
ping6: www.google.com: Temporary failure in name resolution
kaduk@prolepsis:~$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 2001:67c:370:229::7
nameserver 2001:67c:370:229::6
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

And even that doesn't help me very much, as the name-resolution failure
from ping6 indicates..

Using the software rfkill to stop/restart the wireless connection and try
again, however, does get me ipv4 service:

kaduk@prolepsis:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
122: wlp58s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 30:52:cb:e7:7c:45 brd ff:ff:ff:ff:ff:ff
    inet 31.133.157.178/20 brd 31.133.159.255 scope global dynamic noprefixroute wlp58s0
       valid_lft 21466sec preferred_lft 21466sec
    inet6 2001:67c:1232:144:9f96:e9a0:3a6f:8de/64 scope global dynamic noprefixroute 
       valid_lft 2591966sec preferred_lft 2591966sec
    inet6 fe80::95ba:c96b:d420:7871/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

and I could use that connectivity to do my normal work.

I'm no longer in that room, but hopefully there is some useful data in the
report.

Thanks,

Ben

Change history (3)

comment:1 Changed 4 weeks ago by odonoghue@…

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

Hi Ben,

Thank you for the detailed information in the trouble ticket. We have a number of ongoing ietf-hotel issues. The hotel made some unexpected changes yesterday afternoon that have further impacted ietf-hotel. There is a meeting with the hotel at 10:00 am to get better insight into what has been changed on their side. We will report back when we have an update.

comment:2 Changed 4 weeks ago by odonoghue@…

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!

comment:3 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.