Opened 15 months ago

Closed 15 months ago

Last modified 7 months ago

#1069 closed defect (worksforme)

IPv6 from ietf-fairmont SSID seems to have an outage

Reported by: FredBaker.IETF@… Owned by: Clemens Schrimpe
Priority: tbd Milestone: ietf-098
Component: network Keywords: IPv6 Outage
Cc: My Current Location: Fairmont, room 2417
My MAC Address: c4:b3:01:cf:a4:83 My OS: MacOS 10.12.3

Description

IPv6 connectivity on ietf-fairmont appears to have issues:

My status:

MacBook? Pro running 10.12.3 (e.g., MacOS latest)

dhcp-b868:curl-aaaa fred$ ifconfig en0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether c4:b3:01:cf:a4:83
inet6 fe80::1895:f9f3:e8d3:348b%en0 prefixlen 64 secured scopeid 0x4
inet 31.133.184.104 netmask 0xfffff800 broadcast 31.133.191.255
inet6 2001:67c:1233::104c:4bed:7964:4862 prefixlen 64 autoconf secured
inet6 2001:67c:1233::b052:670d:e9f:4a06 prefixlen 64 autoconf temporary
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active

e.g., I have an IPv6 address.

A representative query:

dhcp-b868:curl-aaaa fred$ dig AAAA alsudanalyoum.com

; <<>> DiG 9.8.3-P1 <<>> AAAA alsudanalyoum.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3660
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;alsudanalyoum.com. IN AAAA

;; ANSWER SECTION:
alsudanalyoum.com. 60 IN AAAA 2400:cb00:2048:1::6818:7ca4
alsudanalyoum.com. 60 IN AAAA 2400:cb00:2048:1::6818:7da4

;; Query time: 2 msec
;; SERVER: 74.82.42.42#53(74.82.42.42)
;; WHEN: Sun Mar 26 04:55:45 2017
;; MSG SIZE rcvd: 91

The target website (and perhaps 20K others I have accessed overnight in a test) has an IPv6 address

dhcp-b868:curl-aaaa fred$ curl -6 alsudanalyoum.com
curl: (7) Couldn't connect to server

I have a screen capture from http://ipv6-test.com, which in summary says "IPv4 working, IPv6 complete bust". Happy to email that to you; don't see a place here to attach it.

Change history (8)

comment:1 Changed 15 months ago by llynch@…

Component: incomingnetwork
Owner: changed from llynch@… to nick@…
Status: newassigned
Type: requestdefect

comment:2 Changed 15 months ago by nick@…

Owner: changed from nick@… to Clemens Schrimpe

comment:3 Changed 15 months ago by Clemens Schrimpe

Status: assignedaccepted

I need to have your device on the net to dig deeper into your problem, because IPv6 works for others in the Fairmont.

Please contact me at +1 (321) 355-1649 when your device is back on the net (I presently cannot detect your MAC address).
Thanks,

Clemens

comment:4 Changed 15 months ago by llynch@…

updating due to trac notification issue for reporter

comment:5 Changed 15 months ago by jim@…

[Resending Clemens' comment from when email was impacted]

I need to have your device on the net to dig deeper into your problem, because IPv6 works for others in the Fairmont.
Please contact me at +1 (321) 355-1649 when your device is back on the net (I presently cannot detect your MAC address).
Thanks,
Clemens

comment:6 in reply to:  6 ; Changed 15 months ago by fredbaker.ietf@…

I believe that you can close the ticket. I came on the next morning, and IPv6 connectivity had been restored. Whatever the outage was, it had passed.

> On Mar 27, 2017, at 11:36 AM, IETF Tickets/NOC <tickets@meeting.ietf.org> wrote:
> 
> #1069: IPv6 from ietf-fairmont SSID seems to have an outage
> -------------------------------------+-------------------------------------
>      Reporter:  FredBaker.IETF@…    |                Owner:  Clemens
>                                     |  Schrimpe
>          Type:  defect              |               Status:  accepted
>      Priority:  tbd                 |            Milestone:  ietf-98
>     Component:  network             |           Resolution:
>      Keywords:  IPv6 Outage         |  My Current Location:  Fairmont,
>                                     |  room 2417
> My MAC  Address:  c4:b3:01:cf:a4:83  |                My OS:  MacOS 10.12.3
> -------------------------------------+-------------------------------------
> 
> Comment (by jim@…):
> 
> [Resending Clemens' comment from when email was impacted]
> 
> I need to have your device on the net to dig deeper into your problem,
> because IPv6 works for others in the Fairmont.
> Please contact me at +1 (321) 355-1649 when your device is back on the net
> (I presently cannot detect your MAC address).
> Thanks,
> Clemens
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1069#comment:5>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:7 Changed 15 months ago by Clemens Schrimpe

Resolution: worksforme
Status: acceptedclosed

Ok, we close it for now. If you ever experience trouble again please do not hesitate to open another ticket.

Thanks,

Clemens

comment:8 Changed 7 months ago by Rick Alfvin

Milestone: ietf-98ietf-098

Milestone renamed

Note: See TracTickets for help on using tickets.