Opened 2 years ago

Closed 22 months ago

Last modified 8 months ago

#1014 closed defect (fixed)

DHCP

Reported by: Michael.Bishop@… Owned by: rob@…
Priority: tbd Milestone: ietf-096
Component: dns Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Responding to the appeal to report any problems....

Had trouble getting an IP address on any of the IETF networks in Charlottenburg II/III for ~10 minutes at the beginning of this session.  Tried refreshing, rebooting, etc. and never got any DHCP response until about 4 PM.  Nothing more useful to add, though I've observed the same thing a couple other times this meeting.

Obviously, I'm online now, and presumably can stay that way for the duration of my DHCP lease.

Change history (7)

comment:1 Changed 2 years ago by llynch@…

Component: incomingdns
Owner: changed from llynch@… to rob@…
Status: newassigned
Type: requestdefect

thanks - handing ticket to dhcp expert

  • Lucy

comment:2 Changed 2 years ago by rob@…

Michael,

Thank you so much for your ticket. Can you send me the mac address of the coient that was experiencing the issues?

I will dig into it!

-Rob

comment:3 Changed 2 years ago by Michael.Bishop@…

I'm not certain that I can, actually....  MAC address randomization is on, and I've rebooted for an OS change since then, so I may not still have the same IP address.

In case I do, I think it's currently 9A-8F-AD-5E-17-C9.  If I see this again, I'll note my MAC address then.

-----Original Message-----
From: IETF Tickets/NOC [mailto:tickets@meeting.ietf.org] 
Sent: Wednesday, July 20, 2016 4:35 PM
Subject: Re: [IETF Tickets/NOC] #1014: DHCP

#1014: DHCP
-----------------------------------+--------------------------------
      Reporter:  Michael.Bishop@…  |                Owner:  rob@…
          Type:  defect            |               Status:  assigned
      Priority:  tbd               |            Milestone:  ietf-96
     Component:  dns               |           Resolution:
      Keywords:                    |  My Current Location:
My MAC  Address:                   |                My OS:
-----------------------------------+--------------------------------

Comment (by rob@…):

 Michael,

 Thank you so much for your ticket. Can you send me the mac address of the  coient that was experiencing the issues?

 I will dig into it!

 -Rob

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

comment:4 Changed 2 years ago by rob@…

Michael,

Unfortunately I don't have that MAC in either the dhcpd logs or in the leases file. If you have issues again, please do let me know and I will dig into it!

comment:5 Changed 2 years ago by Michael.Bishop@…

Let's try a different angle....  It looks like MAR uses the same MAC address consistently for the same network.  I just can't figure out how to find out what that MAC is.  However, my current IP address is 31.133.180.244, which should let you backtrack to the MAC address.

That won't let you follow me to the other SSIDs, which I also tried, but that's the point of MAR.  :-)

-----Original Message-----
From: IETF Tickets/NOC [mailto:tickets@meeting.ietf.org] 
Sent: Wednesday, July 20, 2016 4:55 PM
Subject: Re: [IETF Tickets/NOC] #1014: DHCP

#1014: DHCP
-----------------------------------+--------------------------------
      Reporter:  Michael.Bishop@…  |                Owner:  rob@…
          Type:  defect            |               Status:  assigned
      Priority:  tbd               |            Milestone:  ietf-96
     Component:  dns               |           Resolution:
      Keywords:                    |  My Current Location:
My MAC  Address:                   |                My OS:
-----------------------------------+--------------------------------

Comment (by rob@…):

 Michael,

 Unfortunately I don't have that MAC in either the dhcpd logs or in the  leases file. If you have issues again, please do let me know and I will  dig into it!

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

comment:6 Changed 22 months ago by rob@…

Resolution: fixed
Status: assignedclosed

comment:7 Changed 8 months ago by Rick Alfvin

Milestone: ietf-96ietf-096

Milestone renamed

Note: See TracTickets for help on using tickets.