Bug 11668 – DHCP failure menu, fails to appear in setup

Bug 11668 - DHCP failure menu, fails to appear in setup

Summary:

DHCP failure menu, fails to appear in setup

Status:	RESOLVED FIXED

Product:	SB Touch
Classification:	Unclassified
Component:	Setup
Version:	unspecified
Platform:	PC Windows XP

Importance:	-- normal (vote)
Target Milestone:	MPQ
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-04-06 03:31 UTC by Richard Titmuss
Modified:	2009-09-08 09:28 UTC (History)
CC List:	2 users (show)

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 Richard Titmuss 2009-04-06 03:31:44 UTC

This means when DHCP fails you get the wrong error screen, telling you the wireless password was wrong, when really it was a DHCP failure. This may also be a problem is you choose the encryption type.

Comment 1 Richard Titmuss 2009-04-06 06:55:59 UTC

So it turns out this was a failure of the setup flow when DHCP failed. Fixed in r5193.

** QA PLEASE RETEST ALL NETWORK FAILURE MODES DURING SETUP ONCE THIS FIRMWARE IS AVAILABLE**

Comment 2 Jim McAtee 2009-04-12 00:10:29 UTC

I just tested this in r5265 and it appears to be fixed.  The DHCP failure menu came up as expected when making a successful connection to a wireless network without a DHCP server available.

A couple of comments, however:

It might make sense to display interstitial screens, similar to the way it works on Squeezebox, that shows "Connected to network" and "Obtaining a DHCP address", so a user a)doesn't have to wait so long while nothing appears to happen and b)so that they'll more easily troubleshoot connection problems.  As it works now, you can never really be certain that the wireless connection was made.

Secondly, if the user retries the DHCP server via "Detect DHCP automatically" they see a "Connecting to <network name>" screen again.  If I'm not mistaken, the SBT is already connected to the wireless network... it just couldn't obtain an IP address.