Now that I grok OSPF (yeah, not really), I must now move on to everything 

We're rolling out our first WiFi based system (Wavion Beam-forming) with 
Mikrotik routers on the backend. I have ideas how I can set it up, but before I 
get started down my own path I'm hoping to glean some wisdom from some who have 
been here before.

Overall, we have about 1000 wireless customers. We have about 500 public IPs to 
support the WISP operation, I have a new /24 block for this new setup and as I 
free up (most of) the old /24 I can move them over to the Mikrotik.

For the simpler example, I'll have a new site that backhauls over fiber to the 
RB1000 at our main office. The Wavion gear supports a management vlan, and 
vlan-per-ssid. All the standard WiFi AP features I'm sure (for the price, it 
better). The possibly more complex example would be adding an AP to a 
"repeater" site that backhauls off another existing wireless site (Trango) and 
will probably need a routerboard locally.

To date, we have been running NAT in our core router for the bulk of our 
customers, assigning static public IPs as needed (the issue is almost always 
the NAT, not the dynamic IP).

Given that info, how would you recommend configuring the mikrotik and the APs? 
I tend to make things more complex than they need to be. Questions that pop 
into my head: Can/should I run hotspot and PPPoE over the same SSID? Should I 
set my first PPPoE pool to hand out publics and overflow to NAT privates, or 
should I had out NAT addresses and assign publics as requested? How does IP 
assignment work between VLANs so as to prevent conflicts. I would be 
configuring a PPPoE server per-vlan right? What is a good methodology to 
assigning addresses for CPE management? What are issues you have encountered 
along the way that I should be on the watch for?

- Paul

WISPA Wants You! Join today!
WISPA Wireless List:



Reply via email to