M1EXP

[pitbull]

The DHCP server in the router allows you to specify a starting and ending address for the addresses to by used by DHCP.
 
For example, on my router,DHCP is set up to start at 192.168.1.100 and end at 192.168.1.254.   That leaves 192.168.1.2 through 192.168.1.99 for static addresses.
 
You didn't say what fixed address you had the M1XEP assigned to originally, but let's say it was 192.168.1.4.   If you change the XEP configuration back to this, 
and then set the router's DHCP start address to something greater than that (and also greater than the ISY99, if that also has a fixed address), you should be ok.
 
In general, it's nice to set DHCP to leave a reasonably large block of addresses for static addresses and let DHCP manage the rest.   For most home networks, you probably won't have a reason to assign more than a handful of static addresses.   Setting DHCP to start at .100 gives you more room than you're likely to ever need, while leaving plenty of dynamic addresses as well, so you'll probably never have to change the configuration.

mine starts at 192.168.1.2 to 192.168.1.254 so this means I can use 192.168.1.100 to 192.168.1.1 correct?

 

[RAL]

mine starts at 192.168.1.2 to 192.168.1.254 so this means I can use 192.168.1.100 to 192.168.1.1 correct?

 
With that setting, DHCP is managing all the addresses and there is no place to assign a static address.  So yes, you can change it to start at 192.168.1.100 and end at 192.168.1.254.  Then assign the XEP an address below 100 (don't use 192.168.1.1, since that is the router's address).  Once you do that, it should work ok.

 

[drvnbysound]

I'm looking for the homeowner who has 155 DHCP devices (.100-.254)... please stand up. Holy crap!
 
I have no more than 15 DHCP devices and I feel like that's a lot. I have my DHCP pool set to 50 addresses.

 

[tmbrown97]

Its become habit for me now to set DHCP to do .100-.199 and leave the rest open.  I think I've seen up to ~30-ish devices on my DHCP, and another 20 or so on static IP's.
 
I generally use some sort of pattern such as:
1 - Router
2-15= Switches
20-50 = static IP's - servers, san's, whatever
220-239 = Cameras
240+ printers
 
I have no idea where that started but I've kinda stuck with a pattern like that in about a hundred houses now.  VOIP phones are usually left on DHCP unless special inbound routing is required but I only do that if the phone line is on a VPN.
 
It'll be interesting to see when things like the Ube/Plum switches come out - that'd be nearly 100 light switches alone...  might still barely fit within a class C network - but will certainly get closer to the limits requiring another VLAN or subnet.  I've also previously subnetted my own house - VLANs for video, security, guest wifi, regular use, and VPN to the office (telephone mainly) - but that grew tiresome and served no useful purpose so I flattened my network again.

 

[mikefamig]

The DHCP server in the router allows you to specify a starting and ending address for the addresses to by used by DHCP.
 
For example, on my router,DHCP is set up to start at 192.168.1.100 and end at 192.168.1.254.   That leaves 192.168.1.2 through 192.168.1.99 for static addresses.
 
You didn't say what fixed address you had the M1XEP assigned to originally, but let's say it was 192.168.1.4.   If you change the XEP configuration back to this, 
and then set the router's DHCP start address to something greater than that (and also greater than the ISY99, if that also has a fixed address), you should be ok.
 
In general, it's nice to set DHCP to leave a reasonably large block of addresses for static addresses and let DHCP manage the rest.   For most home networks, you probably won't have a reason to assign more than a handful of static addresses.   Setting DHCP to start at .100 gives you more room than you're likely to ever need, while leaving plenty of dynamic addresses as well, so you'll probably never have to change the configuration.

RAL:
 
I'm self taught in networking among other things and did not know that you couldn't assign a static address in the DHCP range of addresses. I have three IP video cameras that I have assigned to static addresses that are shared with DHCP and have been getting away with it for years. I just assumed that because I assigned it as static in the router menus that the DHCP would know to avoid the address. It is a 2-wire router/gateway that ATT installed and maybe it allows this or maybe I've just been lucky. If memory serves me the DHCP assignments don't expire for 30 days or so and that  may be why I'm getting away with it.
 
I think I'll do it your way just for good measure when I feel like playing with it.
 
Mike.

 

[BraveSirRobbin]

I'm not going to speak for RAL and my networking knowledge is pretty limited, but you can 'reserve/assign' a DHCP address via MAC id in most home routers.

 

[RAL]

I'm not going to speak for RAL and my networking knowledge is pretty limited, but you can 'reserve/assign' a DHCP address via MAC id in most home routers.

 
Yes, you could also do it with a reserved DHCP address.  It doesn't work quite the same way as a static address since the XEP needs to be set up for DHCP rather than a static address.  But for the purposes here, it would accomplish pretty much the same thing.  
 
If the XEP should ever die and be replaced, you need to remember to update the table in the router to reflect the new MAC address.   That's one of those details that has kept me scratching my head for a while when I replaced an ethernet interface in a server.   With a true static address, you wouldn't need to change anything on the router side.

 

[wuench]

Or if your router should ever get replaced, with DHCP reservations, you would be in the same boat.