Too long! Too long a post, but I am really keen to acknowledge the
suggestions Ive received, and I very much appreciate the continued
interest and suggestions.
In real life Im a member of a Pipe Band (Scottish bagpipes). Were
not exactly renowned for our sobriety,:o and the band were playing at a
wedding today. In that respect Im a little below par, but I did want
to come back and reply to the latest posts rather than leave too much of
> However you should setup the DHCP range on your router to not include
> these static adresses so that the DHCP won't dole out an used address to
> something else.What I did, following advice received here (and absolutely no question
of any criticism being implied or inferred) was to set the DHCP range on
the router to 192.168.0.100 and upwards i.e. xx.101; 102. etc. This
leaves 192.168.0.000 to 099 for static addresses. I did set this up
in the router admin settings. Im happy this has stuck as it shows up
on the routers admin pages whether the router is actually
implementing this is something else.
> Your network has more than one wifi ap ?
I dont think so. Currently the router is the only real WAP. There is a
powerline WAP, but it was set to the same SSID and password as the main
router. I do wonder if this is a weakness, but I suspect this only
potentially affected one device (a Touch) and I also suspect this Touch
was bypassing this WAP anyway and looking directly at the main
My network is currently built around one device, Netgear D6200,
performing the function of ADSL modem; router; and WAP.
> There are two ways of setting up a "static" address. The first one
> involves configuring the Touch with a fixed address (this gives you a
> real static address), but you must not re-enable DHCP on the Touch, and
> you must select an addres that is not part of the router DHCP pool, but
> still part of the address space the router lets through and routes. Im not sure Im following this precisely.
As above, using the routers admin pages I did set it to a DHCP range
beyond xx.xx.xx.100. I then disabled DHCP on the router, and went around
all the devices, one by one, setting up static IP addresses in the
sub-100 range. When this process was complete, I re-enabled DHCP on the
router. My understanding is that this then allocates IP addresses above
xx.xx.xx.100 on a DHCP basis, but keeps the addresses below that for
specified static routes?
I thought DHCP was enabled by both the device (asking for a specific
address) and the router (being unable to allocate a dynamic address in a
specified range?). I didnt think I could disable DHCP on the Touch
> The other way involves using DHCP, but configuring the router to always
> give out the same address. In this method, the Touch gets a dynamic
> address, but the router ensures it is always the same one.
This is reserved DHCP addresses? I think I did try that first, then
went to proper static addresses as above. But Im just not sure the
router is managing this correctly, or might be faulty.
> I hope this was helpful.
Definitely! As Ive said, Im not at my best, but I sincerely appreciate
this. Ill just select specific bits at the moment, but I will use the
totality to develop my understanding.
> IP networking has to be configured properly for all hosts to
> communicate with each other. By far the most important rule is each IP
> address is uniquely assigned to one host. .....
> All hosts on the same network segment should have the same subnet mask,
> gateway address (typically the router's internal IP address) and DNS
> servers (typically those provided by your ISP and/or your router's
> internal IP address). The gateway is the IP address of the device that
> should receive data for hosts not on the local network segment, i.e.
> anything that doesn't start with 192.168.1.
Im quite sure that I have got this set up right that the subnet mask
is the same, the gateway address in each case is the routers internal
IP address, and my DNS server setting is 1) the routers internal IP
address 192.168.0.1 or 2) the google one of 220.127.116.11
> As the network administrator, you are responsible for planning and
> configuring your network........
> You could assign manually IP addresses to all devices on your network
> and maintain a list of them. These are static addresses and the
> configuration for each is stored on the individual devices. New devices
> have to be manually configured as needed.... For small networks that
> rarely change, assigning static IPs may be tolerable but for most people
> it quickly becomes unmanageable.
As above, I really think I did set this up properly and it did work
for a significant length of time several weeks. ....
> Of particular interest is the lease duration, an important DHCP feature
> that is rarely addressed specifically by home routers. In the
> negotiation between the DHCP server and the network device, the server
> only provides an IP address that it considered available within its
> scope; one that does not have a current lease, reservation or
> exclusion). When it provides it do the network device it does so only
> for a specific length of time which could be as little as minutes or
> hours or as long as days. If the device does not renew its lease, the
> DHCP server will make it available within the scope to assign to another
> device. So it's important that the DHCP server and the devices that use
> it are kept in sync. If the DHCP server is reset, it may consider all
> addresses in the scope to be available which could lead to it handing
> out leases for IP addresses already in use by devices on the network.
Im wondering if this isnt part of my problem. Its possible that one
or other of my squeezedevices wont get used for several weeks. Then I
get a day when Im working around the house and trying to sync them all.
Maybe the leases are expiring?
One way to mitigate DHCP issues is to assign a reservation for devices
which are typically on your network (your router has this feature). By
entering the MAC address of the device and assigning an IP address from
the DHCP server's scope, no other device will be assigned that IP
address and that device will always be assigned that IP address when it
makes a DHCP request. You can make reservations for wired and wireless
devices. The other IP addresses in the scope will be used for transient
devices, presumably your guests' laptops, cell phones, tablets, etc.
Reserved DHCP addresses? I did try this, and cant remember why I tried
to move to proper static addresses. Probably because I was still getting
I hope this was helpful. It doesn't address wireless issues but we can
examine that later. As above definitely helpful.
As mentioned in my earlier posts in this thread, I do think I have
wireless issues. Theyre forecasting rain later tomorrow. I think Ill do
a factory reset on the router (to clear the slate of any static vs DHCP
conflicts) and then install a second WAP to try and address wireless
issues. If that seems to go OK, I can try rebuilding my squeezenetwork
one player at a time.
SB "user" since 2000...
3 x Touch; 2 x Boom ; 3 x Classic; 1 x Controller
Spares - 1xClassic; 2xSB1
Controlled by iPad using 'Squeezepad'
Vortexbox appliance running LMS version 7.8
donmacn's Profile: http://forums.slimdevices.com/member.php?userid=36036
View this thread: http://forums.slimdevices.com/showthread.php?t=101601