Context navigation

← Previous ticket
Next ticket →

#1009 closed request (fixed)

ietf network no ipv4 addresses

Reported by:	fneves@…	Owned by:	jclarke@…
Priority:	tbd	Milestone:	ietf-096
Component:	incoming	Keywords:
Cc:		My Current Location:
My MAC Address:		My OS:

Description (last modified by jclarke@…)

Are we running out of v4 addresses this morning?

V6 works just fine, v4 I only get 169.254/16 error address.

I'm currently using the Hotel network that works just fine.

OSX 10.11.6
MAC 68:a8:6d:50:90:ca

Thanks,
Fred

Fred, can you jump on ietf or ietf-legacy now? I want to troubleshoot in real-time. Thanks.

Change history (10)

comment:1 Changed 5 years ago by jim@…

Fred,

Which network are you on? We'll be glad to look into it!

comment:2 Changed 5 years ago by rob@…

I am looking through the dhcp logs to see what the issue is. I will update shortly.

-Rob (aka Alice)

comment:3 Changed 5 years ago by fneves@…

On Wed, Jul 20, 2016 at 09:10:29AM -0000, IETF Tickets/NOC wrote:
> #1009: ietf network no ipv4 addresses
> ---------------------------+--------------------------------
>       Reporter:  fneves@…  |                Owner:  llynch@…
>           Type:  request   |               Status:  new
>       Priority:  tbd       |            Milestone:  ietf-96
>      Component:  incoming  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+--------------------------------
> 
> Comment (by jim@…):
> 
>  Fred,
>      Which network are you on? We'll be glad to look into it!
> 
>      - Jim

ietf

> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:1>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:4 Changed 5 years ago by jclarke@…

Description:	modified (diff)
Owner:	changed from llynch@… to jclarke@…
Status:	new → assigned

comment:5 Changed 5 years ago by fneves@…

On Wed, Jul 20, 2016 at 09:25:21AM -0000, IETF Tickets/NOC wrote:
> #1009: ietf network no ipv4 addresses
> ---------------------------+---------------------------------
>       Reporter:  fneves@…  |                Owner:  jclarke@…
>           Type:  request   |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-96
>      Component:  incoming  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+---------------------------------
> Changes (by jclarke@…):
> 
>  * owner:  llynch@… => jclarke@…
>  * status:  new => assigned
> 
> 
> Old description:
> 
> > {{{
> > Are we running out of v4 addresses this morning?
> >
> > V6 works just fine, v4 I only get 169.254/16 error address.
> >
> > I'm currently using the Hotel network that works just fine.
> >
> > OSX 10.11.6
> > MAC 68:a8:6d:50:90:ca
> >
> > Thanks,
> > Fred
> > }}}
> 
> New description:
> 
>  {{{
>  Are we running out of v4 addresses this morning?
> 
>  V6 works just fine, v4 I only get 169.254/16 error address.
> 
>  I'm currently using the Hotel network that works just fine.
> 
>  OSX 10.11.6
>  MAC 68:a8:6d:50:90:ca
> 
>  Thanks,
>  Fred
>  }}}
> 
>  Fred, can you jump on ietf or ietf-legacy now?  I want to troubleshoot in
>  real-time.  Thanks.

1 min and I'll be there.

> 
> --
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:4>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:6 Changed 5 years ago by fneves@…

On Wed, Jul 20, 2016 at 09:27:03AM -0000, IETF Tickets/NOC wrote:
> #1009: ietf network no ipv4 addresses
> ---------------------------+---------------------------------
>       Reporter:  fneves@…  |                Owner:  jclarke@…
>           Type:  request   |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-96
>      Component:  incoming  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+---------------------------------
> 
> Comment (by fneves@…):
> 
>  {{{
>  On Wed, Jul 20, 2016 at 09:25:21AM -0000, IETF Tickets/NOC wrote:
>  > #1009: ietf network no ipv4 addresses
>  > ---------------------------+---------------------------------
>  >       Reporter:  fneves@…  |                Owner:  jclarke@…
>  >           Type:  request   |               Status:  assigned
>  >       Priority:  tbd       |            Milestone:  ietf-96
>  >      Component:  incoming  |           Resolution:
>  >       Keywords:            |  My Current Location:
>  > My MAC  Address:           |                My OS:
>  > ---------------------------+---------------------------------
>  > Changes (by jclarke@…):
>  >
>  >  * owner:  llynch@… => jclarke@…
>  >  * status:  new => assigned
>  >
>  >
>  > Old description:
>  >
>  > > {{{
>  > > Are we running out of v4 addresses this morning?
>  > >
>  > > V6 works just fine, v4 I only get 169.254/16 error address.
>  > >
>  > > I'm currently using the Hotel network that works just fine.
>  > >
>  > > OSX 10.11.6
>  > > MAC 68:a8:6d:50:90:ca
>  > >
>  > > Thanks,
>  > > Fred
>  > > }}}
>  >
>  > New description:
>  >
>  >  {{{
>  >  Are we running out of v4 addresses this morning?
>  >
>  >  V6 works just fine, v4 I only get 169.254/16 error address.
>  >
>  >  I'm currently using the Hotel network that works just fine.
>  >
>  >  OSX 10.11.6
>  >  MAC 68:a8:6d:50:90:ca
>  >
>  >  Thanks,
>  >  Fred
>  >  }}}
>  >
>  >  Fred, can you jump on ietf or ietf-legacy now?  I want to troubleshoot
>  in
>  >  real-time.  Thanks.
> 
>  1 min and I'll be there.

Same thing

% ifconfig en1
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
     ether 68:a8:6d:50:90:ca 
     inet6 fe80::6aa8:6dff:fe50:90ca%en1 prefixlen 64 scopeid 0x5 
     inet6 2001:67c:370:176:6aa8:6dff:fe50:90ca prefixlen 64 autoconf 
     inet6 2001:67c:370:176:4483:1c47:9c9e:d42e prefixlen 64 autoconf
     temporary 
     inet 169.254.154.144 netmask 0xffff0000 broadcast 169.254.255.255
     nd6 options=1<PERFORMNUD>
     media: autoselect
     status: active

> 
>  >
>  > --
>  >
>  > --
>  > Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:4>
>  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>  > IETF Meeting Tickets - NOC pages
>  }}}
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:5>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:7 Changed 5 years ago by fneves@…

Forgot to tell, I'm at the glass terminal room. IETF Lounge

Fred

On Wed, Jul 20, 2016 at 09:28:33AM -0000, IETF Tickets/NOC wrote:
> #1009: ietf network no ipv4 addresses
> ---------------------------+---------------------------------
>       Reporter:  fneves@…  |                Owner:  jclarke@…
>           Type:  request   |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-96
>      Component:  incoming  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+---------------------------------
> 
> Comment (by fneves@…):
> 
>  {{{
>  On Wed, Jul 20, 2016 at 09:27:03AM -0000, IETF Tickets/NOC wrote:
>  > #1009: ietf network no ipv4 addresses
>  > ---------------------------+---------------------------------
>  >       Reporter:  fneves@…  |                Owner:  jclarke@…
>  >           Type:  request   |               Status:  assigned
>  >       Priority:  tbd       |            Milestone:  ietf-96
>  >      Component:  incoming  |           Resolution:
>  >       Keywords:            |  My Current Location:
>  > My MAC  Address:           |                My OS:
>  > ---------------------------+---------------------------------
>  >
>  > Comment (by fneves@…):
>  >
>  >  {{{
>  >  On Wed, Jul 20, 2016 at 09:25:21AM -0000, IETF Tickets/NOC wrote:
>  >  > #1009: ietf network no ipv4 addresses
>  >  > ---------------------------+---------------------------------
>  >  >       Reporter:  fneves@…  |                Owner:  jclarke@…
>  >  >           Type:  request   |               Status:  assigned
>  >  >       Priority:  tbd       |            Milestone:  ietf-96
>  >  >      Component:  incoming  |           Resolution:
>  >  >       Keywords:            |  My Current Location:
>  >  > My MAC  Address:           |                My OS:
>  >  > ---------------------------+---------------------------------
>  >  > Changes (by jclarke@…):
>  >  >
>  >  >  * owner:  llynch@… => jclarke@…
>  >  >  * status:  new => assigned
>  >  >
>  >  >
>  >  > Old description:
>  >  >
>  >  > > {{{
>  >  > > Are we running out of v4 addresses this morning?
>  >  > >
>  >  > > V6 works just fine, v4 I only get 169.254/16 error address.
>  >  > >
>  >  > > I'm currently using the Hotel network that works just fine.
>  >  > >
>  >  > > OSX 10.11.6
>  >  > > MAC 68:a8:6d:50:90:ca
>  >  > >
>  >  > > Thanks,
>  >  > > Fred
>  >  > > }}}
>  >  >
>  >  > New description:
>  >  >
>  >  >  {{{
>  >  >  Are we running out of v4 addresses this morning?
>  >  >
>  >  >  V6 works just fine, v4 I only get 169.254/16 error address.
>  >  >
>  >  >  I'm currently using the Hotel network that works just fine.
>  >  >
>  >  >  OSX 10.11.6
>  >  >  MAC 68:a8:6d:50:90:ca
>  >  >
>  >  >  Thanks,
>  >  >  Fred
>  >  >  }}}
>  >  >
>  >  >  Fred, can you jump on ietf or ietf-legacy now?  I want to
>  troubleshoot
>  >  in
>  >  >  real-time.  Thanks.
>  >
>  >  1 min and I'll be there.
> 
>  Same thing
> 
>  % ifconfig en1
>  en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>       ether 68:a8:6d:50:90:ca
>       inet6 fe80::6aa8:6dff:fe50:90ca%en1 prefixlen 64 scopeid 0x5
>       inet6 2001:67c:370:176:6aa8:6dff:fe50:90ca prefixlen 64 autoconf
>       inet6 2001:67c:370:176:4483:1c47:9c9e:d42e prefixlen 64 autoconf
>       temporary
>       inet 169.254.154.144 netmask 0xffff0000 broadcast 169.254.255.255
>       nd6 options=1<PERFORMNUD>
>       media: autoselect
>       status: active
> 
>  >
>  >  >
>  >  > --
>  >  >
>  >  > --
>  >  > Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:4>
>  >  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>  >  > IETF Meeting Tickets - NOC pages
>  >  }}}
>  >
>  > --
>  > Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:5>
>  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>  > IETF Meeting Tickets - NOC pages
>  }}}
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:6>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:8 Changed 5 years ago by fneves@…

Just got an address

% ifconfig en1
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
     ether 68:a8:6d:50:90:ca 
     inet6 fe80::6aa8:6dff:fe50:90ca%en1 prefixlen 64 scopeid 0x5 
     inet6 2001:67c:370:176:6aa8:6dff:fe50:90ca prefixlen 64 autoconf 
     inet6 2001:67c:370:176:4483:1c47:9c9e:d42e prefixlen 64 autoconf
     temporary 
     inet 31.133.179.245 netmask 0xfffff800 broadcast 31.133.183.255
     nd6 options=1<PERFORMNUD>
     media: autoselect
     status: active


On Wed, Jul 20, 2016 at 09:29:57AM -0000, IETF Tickets/NOC wrote:
> #1009: ietf network no ipv4 addresses
> ---------------------------+---------------------------------
>       Reporter:  fneves@…  |                Owner:  jclarke@…
>           Type:  request   |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-96
>      Component:  incoming  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+---------------------------------
> 
> Comment (by fneves@…):
> 
>  {{{
>  Forgot to tell, I'm at the glass terminal room. IETF Lounge
> 
>  Fred
> 
>  On Wed, Jul 20, 2016 at 09:28:33AM -0000, IETF Tickets/NOC wrote:
>  > #1009: ietf network no ipv4 addresses
>  > ---------------------------+---------------------------------
>  >       Reporter:  fneves@…  |                Owner:  jclarke@…
>  >           Type:  request   |               Status:  assigned
>  >       Priority:  tbd       |            Milestone:  ietf-96
>  >      Component:  incoming  |           Resolution:
>  >       Keywords:            |  My Current Location:
>  > My MAC  Address:           |                My OS:
>  > ---------------------------+---------------------------------
>  >
>  > Comment (by fneves@…):
>  >
>  >  {{{
>  >  On Wed, Jul 20, 2016 at 09:27:03AM -0000, IETF Tickets/NOC wrote:
>  >  > #1009: ietf network no ipv4 addresses
>  >  > ---------------------------+---------------------------------
>  >  >       Reporter:  fneves@…  |                Owner:  jclarke@…
>  >  >           Type:  request   |               Status:  assigned
>  >  >       Priority:  tbd       |            Milestone:  ietf-96
>  >  >      Component:  incoming  |           Resolution:
>  >  >       Keywords:            |  My Current Location:
>  >  > My MAC  Address:           |                My OS:
>  >  > ---------------------------+---------------------------------
>  >  >
>  >  > Comment (by fneves@…):
>  >  >
>  >  >  {{{
>  >  >  On Wed, Jul 20, 2016 at 09:25:21AM -0000, IETF Tickets/NOC wrote:
>  >  >  > #1009: ietf network no ipv4 addresses
>  >  >  > ---------------------------+---------------------------------
>  >  >  >       Reporter:  fneves@…  |                Owner:  jclarke@…
>  >  >  >           Type:  request   |               Status:  assigned
>  >  >  >       Priority:  tbd       |            Milestone:  ietf-96
>  >  >  >      Component:  incoming  |           Resolution:
>  >  >  >       Keywords:            |  My Current Location:
>  >  >  > My MAC  Address:           |                My OS:
>  >  >  > ---------------------------+---------------------------------
>  >  >  > Changes (by jclarke@…):
>  >  >  >
>  >  >  >  * owner:  llynch@… => jclarke@…
>  >  >  >  * status:  new => assigned
>  >  >  >
>  >  >  >
>  >  >  > Old description:
>  >  >  >
>  >  >  > > {{{
>  >  >  > > Are we running out of v4 addresses this morning?
>  >  >  > >
>  >  >  > > V6 works just fine, v4 I only get 169.254/16 error address.
>  >  >  > >
>  >  >  > > I'm currently using the Hotel network that works just fine.
>  >  >  > >
>  >  >  > > OSX 10.11.6
>  >  >  > > MAC 68:a8:6d:50:90:ca
>  >  >  > >
>  >  >  > > Thanks,
>  >  >  > > Fred
>  >  >  > > }}}
>  >  >  >
>  >  >  > New description:
>  >  >  >
>  >  >  >  {{{
>  >  >  >  Are we running out of v4 addresses this morning?
>  >  >  >
>  >  >  >  V6 works just fine, v4 I only get 169.254/16 error address.
>  >  >  >
>  >  >  >  I'm currently using the Hotel network that works just fine.
>  >  >  >
>  >  >  >  OSX 10.11.6
>  >  >  >  MAC 68:a8:6d:50:90:ca
>  >  >  >
>  >  >  >  Thanks,
>  >  >  >  Fred
>  >  >  >  }}}
>  >  >  >
>  >  >  >  Fred, can you jump on ietf or ietf-legacy now?  I want to
>  >  troubleshoot
>  >  >  in
>  >  >  >  real-time.  Thanks.
>  >  >
>  >  >  1 min and I'll be there.
>  >
>  >  Same thing
>  >
>  >  % ifconfig en1
>  >  en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>  >       ether 68:a8:6d:50:90:ca
>  >       inet6 fe80::6aa8:6dff:fe50:90ca%en1 prefixlen 64 scopeid 0x5
>  >       inet6 2001:67c:370:176:6aa8:6dff:fe50:90ca prefixlen 64 autoconf
>  >       inet6 2001:67c:370:176:4483:1c47:9c9e:d42e prefixlen 64 autoconf
>  >       temporary
>  >       inet 169.254.154.144 netmask 0xffff0000 broadcast 169.254.255.255
>  >       nd6 options=1<PERFORMNUD>
>  >       media: autoselect
>  >       status: active
>  >
>  >  >
>  >  >  >
>  >  >  > --
>  >  >  >
>  >  >  > --
>  >  >  > Ticket URL:
>  <https://tickets.meeting.ietf.org/ticket/1009#comment:4>
>  >  >  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>  >  >  > IETF Meeting Tickets - NOC pages
>  >  >  }}}
>  >  >
>  >  > --
>  >  > Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:5>
>  >  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>  >  > IETF Meeting Tickets - NOC pages
>  >  }}}
>  >
>  > --
>  > Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:6>
>  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>  > IETF Meeting Tickets - NOC pages
>  }}}
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1009#comment:7>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:9 Changed 5 years ago by jclarke@…

Resolution:	→ fixed
Status:	assigned → closed

Thanks, Fred. If this happens again, please turn off wireless and turn it back on. If you still don't get an address and you can, come by the NOC. I'd like to troubleshoot this in more detail. Thanks.

comment:10 Changed 3 years ago by Rick Alfvin

Milestone:	ietf-96 → ietf-096

Milestone renamed

Note: See TracTickets for help on using tickets.

Download in other formats: