consider two halves; The ISP side and the LAN side.

On the LAN, you only need static addresses where there is a server; all the clients
that come and go get DHCP assigned addresses. eg

set your servers statically at or above 100
and config the router to hand out DHCP address from 2->99
which is far more than you will need

As long as the clients have tcp set to use DHCP for both IP and DNS, they will be good to go

On the ISP side; the only way to get a static address (which will be given to your modem or router) is to PURCHASE a static ip -- typically registering a domain name.

You can FAKE it by using www.dyndns.com

I've found that each router has a different implementation of MAC filtering

1. one form is {Black.White}list specific MACS for access
2. the other, is mapping MAC-> IP address to be assigned

my Netgear does the latter -- and I love it
with this implementation, I've set my systems to be known and thus there addresses
look like STATIC but the are not.

This allows known systems to have different firewall rules than the unknown!

Yeah that's why I wanted to avoid getting a Static IP (ISP)...Funds aren't very lenient...

I'm not sure what the jazz is with my Belkins MAC filtering...It just shows to add an address (And block it if need be)...