Max IP Addresses

[ryan8382]

At the risk of stating the obvious: Unless you want to start filtering with MAC addresses (which would be a pain to administer), you have to issue an IP address to every device that asks for it. Only after it's connected can you find out how to prioritize the traffic from it - be it by what it's requesting or by the person's login.

And, just because you give a device an IP address, does't mean you have to give it any Internet bandwidth. So I don't see limiting IP addresses as a valid means of rationing bandwidth. Not unless you hold the limited pool over the leaders heads so as to not overshare the network password.

If you split the networks between IP ranges that would do then bandwidth management. So LDS equipment would be 192.168.1.x and public equipment would be 172.16.1.x. Bandwidth throttling would only be on the public. That also gibe you a full class c to expand to. And because you put a put a class c out there doesn't mean you have set dhcp for whole range. Leave yourself room to expand.

[ryan8382]

They could setup netflow on the firewalls to give everyone an idea of traffic. I have used manage engine net flow.at with we use solar winds. Which is expensive but is really powerful.

Do we know for sure if lease times were changed to 39 minutes?

[paulscherbel]

Do we know for sure if lease times were changed to 39 minutes?

The lease times for the majority of 881Ws in the U.S. and Canada have been changed to 30 minutes.

[ryan8382]

Thanks for the response. Has there been any talk about using netflow or a proxy server at all locations?