Thanks so much! Though I'm not a WISPA member (nor do I run a WISP or make a profit from the network I run here in the jungle of Venezuela), since there's so much discussion on the forum about this topic and there's WISPA members who still have bridged networks which they want to some day route I assumed this information would be of use to many members on the forum.
Thank you for taking the time to reply! Greg On Aug 26, 2010, at 8:41 AM, Faisal Imtiaz wrote: > Hi Greg, > > I think I understand what you are asking for... since this type of stuff > tends to me more of an exercise heavily influenced by personal > preference or judgment...Having said that, let me share with you some > starting config... I am sure other can chime in with more suggestions. > > > ------------------ > > We are using a small Mikrotik in each of our Wireless POP's, at the > moment we are using 750g and or 493ah > > Each Radio (Ap / Backhaul etc) is connected to each individual port on > the MK. > > Non of the ports are grouped into a switch group...i.e. each port is > a'routed port'. > > Each port has multiple subnets (block of IP's). I am starting off with > /27's assigned to each port. > > A private block of /27 on each port, that we are using for radio management. > > An initial public block of /27 on each port ( connected to AP's) for end > customer usage. > > We are not doing NAT on the MK, assigning public ip to each customer. or > assigning a small routed block /29 for customer. > (Mostly business customers) > > > On the Up-Stream / Down-Stream Backhaul... we are using a /29, public > for routing and private for Radio management > > > In this type of config, you can run all Static Routing or turn on OSPF > or whatever makes you happy (dynamic routing). > > We create an IPSEC tunnel between the MK and our NOC's Firewall, thus > allowing direct access to the Private IP's (Our MGMT network is on the > private IP's. > > Plus, we also leave a PPTP config on the MK, incase one needs to access > the Mgmt side of the radios they can connect to that MK and access the > mgmt network. > > > There are a lot of other little small details about configuration / > security etc, most of them to suite your needs / standards & taste. > > We run each of the AP's with it's own SSID, in Straight Bridge Mode, so > the CPE's are bridged to AP, or if need be, the CPE can also be in a > Routed Mode to route a public subnet across it. > > > Hope this gives you some ideas on where to start from. > > > > > Faisal Imtiaz > Snappy Internet & Telecom > 7266 SW 48 Street > Miami, Fl 33155 > Tel: 305 663 5518 x 232 > Helpdesk: 305 663 5518 option 2 Email: [email protected] > > On 8/26/2010 8:39 AM, Greg Ihnen wrote: >> Does anyone have an example or wiki on how to set up a simple (just a few >> APs, two backhauls) routed network? I've googled and I've not found anything. >> >> Greg >> >> On Aug 25, 2010, at 11:54 PM, Jeromie Reeves wrote: >> >>> Have a client with the problem do a nslookup before a ping. It sounds >>> much like a dns or a arp issue as mentioned. Can you route each >>> Powerstation ? I like to bridge the AP (with dedicated ports behind >>> them) and WDS the clients (with their radios running internal routed >>> 10.x subnets , no nat!). This has show to be the best balance between >>> speed and stability. Also check the powerstation arp tables as well as >>> the upstream router, before they issue the nslookup or ping, then >>> after. Also try disabling dns caching on the client radios. >>> >>> On Wed, Aug 25, 2010 at 9:09 PM, Mark Dueck<[email protected]> wrote: >>>> I don't think it's a DNS because most clients that are complaining are from >>>> one AP. Today I got one that's from a diff AP that said their net was >>>> intermittent. >>>> >>>> I myself am browsing on the same network and never experience that problem. >>>> I have the same settings. >>>> >>>> Mostly Tranzeo SL2's as clients, with 2 PowerStations as AP's. The rest of >>>> the AP's are all Tranzeo. All clients are routed internally, but after the >>>> client radio everything is bridged. I rebooted the gateway to clear the >>>> arp >>>> cache, but clients are still experiencing the same problem. >>>> >>>> Could it cause a problem with the fact that the gateway is multiwan and 2 >>>> of >>>> it's wan's are on the same network as the clients, but different subnet. I >>>> know I need to VLAN, but had some issues with VLAN not connecting. >>>> >>>> >>>> On 08/25/2010 05:51 PM, Josh Luthman wrote: >>>> >>>> What kind of radios? >>>> >>>> You sure it isn't a problem with the DNS servers? >>>> >>>> On Aug 25, 2010 7:44 PM, "Mark Dueck"<[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> I've got some issues on my network with clients complaining they have no >>>> internet. When I come around, as soon as I ping gateway and then google >>>> dns, the browsing is back up. I showed a client how to do this, and he >>>> says whenever his internet goes down, as soon as he pings it's right >>>> back up. >>>> >>>> Anyone have ideas why this could happen? >>>> >>>> Thanks, >>>> Mark >>>> >>>> >>>> -------------------------------------------------------------------------------- >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> -------------------------------------------------------------------------------- >>>> >>>> WISPA Wireless List: [email protected] >>>> >>>> Subscribe/Unsubscribe: >>>> http://lists.wispa.org/mailman/listinfo/wireless >>>> >>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>> >>>> >>>> >>>> -------------------------------------------------------------------------------- >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> -------------------------------------------------------------------------------- >>>> >>>> WISPA Wireless List: [email protected] >>>> >>>> Subscribe/Unsubscribe: >>>> http://lists.wispa.org/mailman/listinfo/wireless >>>> >>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>> >>>> >>>> >>>> -------------------------------------------------------------------------------- >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> -------------------------------------------------------------------------------- >>>> >>>> WISPA Wireless List: [email protected] >>>> >>>> Subscribe/Unsubscribe: >>>> http://lists.wispa.org/mailman/listinfo/wireless >>>> >>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>> >>> >>> >>> -------------------------------------------------------------------------------- >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> -------------------------------------------------------------------------------- >>> >>> WISPA Wireless List: [email protected] >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: [email protected] >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
