Duet issues now appear resolved with fixed IP

**springtide9** · 2012-02-21, 13:11

Well it has been weeks trying to figure out what has been going wrong with my Duet & 3 receivers.

I have constantly been having to reboot the receivers and controller to get them all recognised, and then they would disappear again - then have to run through the setup etc... it's been driving me mad.

After a bit of searching I discovered how to setup the Duet and the Recievers with Fixed IP Addresses. You basically disable DHCP on the router and setup the Duet - which forces it to use fixed IP when it fails with DHCP (it would be much better to allow this during the standard setup - especially as DHCP appears to be a common problem???). It's also a shame that the setup for fixed ip isn't a documented process.

Anyway, once the Duet is setup with a fixed IP, then when you setup the receivers - these also default to fixed ip.

Did this last night and the Squeezebox's that were destined for EBay (as I had almost thrown in the towel with this things), all now appears to be working.

The moral of this story appears to be, if you have issues connecting to the receivers etc when they haven't been used for a little while - the fix appears to be setting them up with fixed ip.

As above, it would really be beneficial for the Fixed IP setup to be simplified, as well as the Fixed IP setup being documented within an FAQ.

**paulster** · 2012-02-21, 13:43

That's cool. I always thought the only way to get a fixed IP on them was to use Net::UDAP.

Shows how well documented this feature is(n't)!

**springtide9** · 2012-02-21, 13:55

Originally Posted by paulster

That's cool. I always thought the only way to get a fixed IP on them was to use Net::UDAP.

Shows how well documented this feature is(n't)!

FYI... just looked at the 'stuck on blue' bug in your sig - that is exactly what I was seeing on the receivers (which fixed ip appears to have resolved)

**Mnyb** · 2012-02-21, 13:57

there is an old bug.

http://bugs.slimdevices.com/show_bug.cgi?id=7502

There is really no valid argument for not having this option . A completely unfathomable omission .

Work around.

You can turn of the DHCP server .

Use net udap for a receiver .

Controller,Radio,Touch has another option use SSH and edit the network scripts directly

**paulster** · 2012-02-21, 14:18

Originally Posted by springtide9

FYI... just looked at the 'stuck on blue' bug in your sig - that is exactly what I was seeing on the receivers (which fixed ip appears to have resolved)

Cool. Can you vote on it if you haven't!

Not that it seems to have any bearing on whether Logitech will fix a particular problem (thinking of the static IP addressing right away) it all helps with the justification.

**Mnyb** · 2012-02-22, 01:57

This is an old chestnut with Squeezeboxes it should be mentioned more often .

I would not be surprised if a very large part of the frequent posters on this forum run the whole squeeze eco system with static-ip .

I do that with all players controllers and servers and stationary computers, I started doing it with the SB3 in 2007 been doing it ever since .

How many beta testers are using DHCP ?

in my case i want things to work to so I use static IP it is truly bombproof I never have conection problems

**garym** · 2012-02-22, 04:46

Originally Posted by Mnyb

This is an old chestnut with Squeezeboxes it should be mentioned more often .

I would not be surprised if a very large part of the frequent posters on this forum run the whole squeeze eco system with static-ip .

I do that with all players controllers and servers and stationary computers, I started doing it with the SB3 in 2007 been doing it ever since .

How many beta testers are using DHCP ?

in my case i want things to work to so I use static IP it is truly bombproof I never have conection problems

+1 All my SB stuff (and server) is static (not just reserved) IP.

**virgiliomi** · 2012-02-22, 05:48

With the exception of my router, Slingbox and switches (four devices total), everything else on my network - PCs, NAS, VoIP adapter, all Squeeze devices, etc. - is DHCP, no reservations.

All of the important stuff is on and always able to renew the same lease IP, so IPs for my NAS and Squeeze devices rarely change anyway. But since you were wondering, yes, I am running my network with nearly everything using DHCP with no defined reservations.

**Mnyb** · 2012-02-22, 05:58

Originally Posted by virgiliomi

With the exception of my router, Slingbox and switches (four devices total), everything else on my network - PCs, NAS, VoIP adapter, all Squeeze devices, etc. - is DHCP, no reservations.

All of the important stuff is on and always able to renew the same lease IP, so IPs for my NAS and Squeeze devices rarely change anyway. But since you were wondering, yes, I am running my network with nearly everything using DHCP with no defined reservations.

And your reciever renew it leases without problems when it needs to .

Note that there is some indication in the bug that networks where router is not 192.168.0.1 or 192.168.1.1 may be more problemtatic ie anything but the bog standard rigth out off the box setup for a router .

Supose reciever expect DHCP server to be on ..x.1 ?

**springtide9** · 2012-02-23, 08:57

I think the DHCP issue might be a timeout issue or maybe just an "incomparability bug", and maybe some routers (if they are the DHCP Servers) work better with SB than others.

My main issue is not that the bug (or issue) exists, and I don't even care whether the bug is with SB or the router, but it was better documented within a SB FAQ, as well as SB making the fixed IP setup more user friendly.

Anyway, a couple more days have past and my SB is still working without any issues

Thread: Duet issues now appear resolved with fixed IP

Thread Tools

Search Thread

Display

Duet issues now appear resolved with fixed IP

Posting Permissions