Bug 3219 – DHCP timeout/assignment of local loop IP is user-unfriendly

Bug 3219 - DHCP timeout/assignment of local loop IP is user-unfriendly

Summary:

DHCP timeout/assignment of local loop IP is user-unfriendly

Status:	CLOSED FIXED

Product:	SB 2/3
Classification:	Unclassified
Component:	Setup
Version:	36
Platform:	PC Windows XP

Importance:	P2 minor (vote)
Target Milestone:	---
Assigned To:	Richard Titmuss

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-03-28 15:11 UTC by Chris Owens
Modified:	2008-12-18 11:38 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Chris Owens 2006-03-28 15:11:30 UTC

When a DHCP server can't be reached, the SB UI counts down to 2, then reports it has acquired the address 169.254.68.195.  This isn't strictly true; the SB has assigned that address to itself.

You mentioned a better solution might be to have the UI notify the user something like: Failed to find a DHCP server.  Would you like to use a local loop address?

Comment 1 Richard Titmuss 2006-04-18 12:05:31 UTC

Fixed in firmware 47

Comment 2 Chris Owens 2006-04-18 18:50:52 UTC

Verified fixed in FW41 (not 47 :)

Comment 3 James Richardson 2008-12-15 12:31:20 UTC

This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.