erland;563565 Wrote: 
> For which type of users ?
> I'm pretty sure it's the same type of users that is able to use the
> current workaround which already exists. 
> 
> Using static IP's isn't a solution for the rest who is barely able
> setup their router with DHCP and connect the network cables correctly.
> I'm just trying to say that if we want to improve the current
> situation, we should focus on improving it for non technical users who
> aren't able to use the already existing workaround. Adding more
> advanced settings which only advanced users understand doesn't help the
> kind of non technical users which I suspect Logitech wants to be able to
> use the device, we really need to start thinking about making this
> device less geeky instead of more.  
> 
> Several of my friends wouldn't have clue what IP address to enter when
> prompted for it. A DHCP solution on the other hand means that it's
> basically plug and play. Yes, I understand that DHCP would still be the
> preferred choice when setting up the device. My concerns is more about
> the fact that this will use development time which could be used for
> something related to the music listening experience and it would still
> not be usable for the main target group of the Squeezebox devices.
> 
> By the way, isn't the existing workaround something you do once for
> each new Squeezebox and then can forget ? Or does is have to be
> re-applied after each firmware upgrade? If it's a one time
> configuration I really doesn't understand why it's a big issue.
> 
> I should say that I'm not regularly using my Duet so I might be missing
> something here, but to me it really feels like we are just requesting
> another workaround that still wouldn't work for non technical users,
Very good points and I don't disagree generally, however a couple of
points are worth emphasising:

- Not all DHCP problems are caused by the SqueezeBox (it may be the
Router), so trying to fix potential issues with an improved Controller
firmware is only part of the solution.  Setting a fixed IP for the
Controller is a simple and effective workaround for both SqueezeBox and
router DHCP problems and would take up a very great deal less Developer
time than trying to make the Controller DHCP client compatible with
*all* DHCP server implementations.

- DHCP issues have been an ongoing sore point for both the Duet devices
ever since I started following these forums in 2008.  If they have not
fixed them by now I doubt if they ever will.

- The workarounds are *not reliable*. They work for some and not for
others. There are plenty of people out there who could fill out an IP
address configuration page easily enough but would have real trouble
using SSH/Putty or Net:UDAP

- The Controller and Receiver *already have a way to enter a manual
IP!* However currently it *only* appears if the Controller fails to
find an IP by DHCP, and then only intermittently and unpredictably. 
Would it really take up so much Developer time to simply add a link to
that already existing routine in the Settings/Advanced menu?

- What is particularly exasperating is that it *is* already an option
in the Boom and Classic menus.  Why was it not implemented in the
Controller?


-- 
TheLastMan

Matt

*SqueezeBoxes:* SB Duet (Controller + two receivers)
*Server:* Synology Diskstation 107+ NAS (with firmware 2.3-1157)
running Squeezebox Server 7.5.0 on Synology Package Manager
*Network:* Netgear DG834GT ADSL modem/router, 2 x Buffalo WHR-HP-G54 as
access points
*Livingroom:* Receiver into Naim 42/110 amp, B&W CM2 speakers
*Kitchen:* Receiver into Denon DM37 mini-system, B&W 686 speakers
*Study:* Linn LP12, Naim 72/Hi-cap/Headline. LPs ripped usingBehringer
UCA202 USB into Windows XP PC
------------------------------------------------------------------------
TheLastMan's Profile: http://forums.slimdevices.com/member.php?userid=16021
View this thread: http://forums.slimdevices.com/showthread.php?t=80577

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss

Reply via email to