Jason Hensley wrote:

> I'm really going to need to have a routed network.

You're probably right there. Our legacy bridged network still causes the
occasional weird problem, because of all the MACs flying around three

> My biggest question is, how do you manage your CPE remotely in a routed
> network?

The same way as in a bridged network?

(If this sounds like a silly response, I apologize, but things will be
pretty much the same, only you might have to keep track of a couple
different subnet masks. Obviously I don't know your network, but it
shouldn't cause any major changes in how you manage things, aside from
having to change a few IPs here and there.)

> Also, I would ideally like to have a public IP assigned to each CPE. 

I'm not familiar with the specific gear you're using, but I'd suggest
avoiding that if possible. It's a bit wasteful of public IPs. (I'm
guilty of this, I'll admit it.)

If your gear will support it, just do an "overlay" network, and for the
sake of convenience, just use similar IPs for both networks.

Example: give your AP both and (one IP from a
private block, one from a public block). Then, for the first customer,
make his radio, and his router (or whatever) (the
public IP - note that the last octet is the same).

That gives you the benefit of private IPs you can use to manage your CPE
and your network, gives the customer a public IP address, and by virtue
of having your customer gear in a separate subnet, makes it a bit harder
for your users to poke around in your network :)

This assumes your CPE is all basically "transparent bridge" gear. Again,
I'm not familiar with your network, and that may not be the case.

If you've only got a /24 worth of public IPs now, this is an especially
good idea, because it will allow you to conserve those IPs. Better to do
it now, and do it right, than when you have many hundreds of end-users
and it's more of a trial to do.

David Smith
WISPA Wireless List: wireless@wispa.org


Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to