Opened 3 years ago

Closed 3 years ago

Last modified 2 months ago

#922 closed defect (LOL WHUT?)

intermittent v6 failures on ietf-hotel

Reported by: Paul_Ebersman@… Owned by: nkukich@…
Priority: tbd Milestone: ietf-092
Component: network Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

I have had multiple short failures where v4 worked but v6 didn’t on ietf-hotel

this is a 10.9.x mac osx box.

i’m attaching to c4:01:7c:88:a4:38, channel 6 at moment. that’s from 7th floor south tower.

ifconfig gives me the following v6:

        inet6 fe80::8e29:37ff:fef0:15fc%en0 prefixlen 64 scopeid 0x4 
        inet6 2001:67c:370:136:8e29:37ff:fef0:15fc prefixlen 64 autoconf 
        inet6 2001:67c:370:136:3c24:41f6:b3b3:2135 prefixlen 64 autoconf temporary 

and resolv.conf has working DNS yet “ping6 pendor.dragon.net” gives "UDP connect: No route to host”

and netstat -rn shows no v6 default route.

This does come and go and mos to of the time v6 is working.

let me know what additional info you need.

Change history (7)

comment:1 Changed 3 years ago by llynch@…

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

comment:2 Changed 3 years ago by Paul_Ebersman@…

Quick guess would be RA message expiration?

Don’t know off hand what mac osx command is to see RA message info.

On 25Mar, 2015, at 5:29 PM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:

> #922: intermittent v6 failures on ietf-hotel
> ----------------------------------+---------------------------------
>      Reporter:  Paul_Ebersman@…  |                Owner:  nkukich@…
>          Type:  defect           |               Status:  assigned
>      Priority:  tbd              |            Milestone:  ietf-92
>     Component:  network          |           Resolution:
>      Keywords:                   |  My Current Location:
> My MAC  Address:                  |                My OS:
> ----------------------------------+---------------------------------
> Changes (by llynch@…):
> 
> * owner:  llynch@… => nkukich@…
> * status:  new => assigned
> * component:  incoming => network
> * type:  request => defect
> 
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/922#comment:1>
> IETF Meeting/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting - NOC pages

comment:3 Changed 3 years ago by nkukich@…

Is this location dependent or is it happening consistently throughout the venue?

comment:4 Changed 3 years ago by Paul_Ebersman@…

Seems to be network dependent. I’ve only noticed it on ietf-hotel. But since that means
it’s in places that ietf network isn’t visible, i suppose it could be location dependent...


On 26Mar, 2015, at 8:22 AM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:

> Is this location dependent or is it happening consistently throughout the
> venue?

comment:5 Changed 3 years ago by Paul_Ebersman@…

Seems to be network dependent. I’ve only noticed it on ietf-hotel. But since that means
it’s in places that ietf network isn’t visible, i suppose it could be location dependent...


On 26Mar, 2015, at 8:22 AM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:

> Is this location dependent or is it happening consistently throughout the
> venue?

comment:6 Changed 3 years ago by bzeeb+ietf@…

Resolution: LOL WHUT?
Status: assignedclosed

comment:7 Changed 2 months ago by Rick Alfvin

Milestone: ietf-92ietf-092

Milestone renamed

Note: See TracTickets for help on using tickets.