Bug 11699 - Diagnostics reports a self-assigned IP before IP should be assigned yet
: Diagnostics reports a self-assigned IP before IP should be assigned yet
Status: RESOLVED WONTFIX
Product: SB Touch
Classification: Unclassified
Component: Setup
: unspecified
: PC Other
: -- normal (vote)
: MP
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-07 16:22 UTC by Dan Evans
Modified: 2009-09-08 09:15 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-04-07 16:22:34 UTC
(using r5156)

If no DHCP server is found, and you select "Enter IP information manually", you are brought to the IP address entry keyboard.  

Press the Help button there and make your way to the Diagnostics screen.  You'll see that Fab4 thinks it already has an IP address in the 169.254.x.x range.

Shouldn't this be unassigned or blank at this stage?

Not sure if this bug is about:
 * the Diagnostics screen's query getting the IP wrong  
 * Fab4 getting a self-assigned IP when it shouldn't
Comment 1 Mark Miksis 2009-04-07 16:30:52 UTC
Isn't this how auto-IP is supposed to work?  If the DHCP server doesn't respond, how would the client know whether or not to expect you to assign a static IP instead of using the auto IP?
Comment 2 Blackketter Dean 2009-04-07 17:47:02 UTC
That's right.  a 169.254. address is one that has been self assigned.  

The way the Mac handles this is to show the address and say "(Self Assigned)" next to it.

Not sure if we have room for this, but it would be a nice to have.
Comment 3 Richard Titmuss 2009-04-08 01:05:44 UTC
This works as designed, if DHCP fails then a self assigned address will be used. The UI detects the DHCP failure be observing the self assigned address, then allows the user options to enter a static ip address (to replace the self assigned address), or use the self assigned address (that just continues).

Changing this would be a) hard and b) a significant risk.
Comment 4 Dan Evans 2009-04-08 08:41:42 UTC
Understood.  It was the order of things that threw me off, but I suspect I didn't think it through.  No change necessary.