... One note, I did all this because it appears impossible to run static IPs and dhcp simlutaneously on the same router. I had cameras running static but it could not deal with computers while dhcp was up. I would run all static except my kids have wireless notebooks. ...
By the way, it *is* possible to run DHCP and static addressing on the same router. Technically, all addresses DHCP serves, including static addresses, must be allocated to its pool, and all other addresses assigned by other methods must come from outside the pool. In the past, some DHCP servers may have been programmed incorrectly in this respect.
To illustrate, suppose you have a Linksys router (IP 192.168.1.1, netmask 255.255.255.0) that supports static assignments, and suppose you have configured it to assign addresses in the range of .101 through .150. You can manually configure nodes with addresses in the ranges .2-.100 and .151-.254. (.0 is the network address, .1 is the router and .255 is the broadcast address.) You can tell DHCP to assign .101 to your desktop, .102 to your printer, .103 to your kid's computer, etc. This is done by 'relating' a node's MAC address to the respective IP address. Now, when DHCP gets a request, it checks the node's MAC addr; if it finds a match, it assigns the 'related' static address. If it does not find a match, it assigns a dynamic address. Regardless, all addresses it assigns must come from within its pool.
I know DHCP works this way on the Linksys WRT54GC (Linksys firmware) and on the WRT54G with DD-WRT firmware.
N