I am not seeing results like this at all, I am using nstream on several PTP links w/ SR5 cards w/ great success, (polling on) - throughput is awesome and I have replaced all of my karlnet backhaul links (well not replaced but turned the karlnet links into backup links), I believe mikrotik is definitely the next wave, so much that I have started offering complete AP/CPE solution kits through my web store @ http://store.wbisp.com/ (site just went up last night so its under construction)
Mikrotik is really bringing a great product to the market and w/ the coming sr9 cards there will be a lot of options on the table for the WISP's > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Tom DeReggi > Sent: Thursday, February 09, 2006 1:29 AM > To: WISPA General List > Subject: Re: [WISPA] Mikrotik Bridging w-Nstreme > > This problem was solved thanks to prompt tech support from Wisp-Router. > > With NStreme enabled, it is necessary to assign the IP to the Bridged port, > not ether1. > However, without Nstreme enabled, it works fine with IP assigned to Ether1, > as long as bridged to WLAN. > (The same way that always worked with Star OS) > > There were also a couple odd things related to what order setting were > checked converting from one config to another, that kept Nstreme from > working, which we were able to replicate after the fact (after tech > support), to prove we weren't crazy. Unfortuneately, I can't remember now, > what exactly the sequence was, 5 hours later. For example, there were times > when we enabled Nstreme correctly , and it just wouldn't connect. But we > then disabled it, got WDS to talk again, and then re-enabled it > successfully. It may have had something todo with one side of the link being > completely configured before the other. Because if both aren't on Nstreme > they dont talk at the radio level. So the rule was when a configuration > didn't talk, disble NStreme, make it talk, then re-enable, and it would > work. > > What I do like about Mikrotik, is that its all there infront of you, all the > tools, all the features, as needed. Its pretty well laid out, once you get > the hang of it. > > Probably the biggest feature I saw missing, was it didn't support diversity > mode on the Wireless driver. It was A or B or Full Duplex. But not > diversity. > > One of the nice things about Star-OS was that it supported diversity mode, > but also it was less critical to configuration errors. > > Tom DeReggi > RapidDSL & Wireless, Inc > IntAirNet- Fixed Wireless Broadband > > > ----- Original Message ----- > From: "Tom DeReggi" <[EMAIL PROTECTED]> > To: "WISPA General List" <[email protected]> > Sent: Wednesday, February 08, 2006 5:44 PM > Subject: Re: [WISPA] Mikrotik Bridging w-Nstreme > > > > Thats exactly what we are trying to do, but its not working, using version > > 9.12. > > > > If I try ping radios.... > > > > When sniffing, the station sees traffic comming in, but the AP-bridge, > > sees no traffic comming in. > > > > I correctly have put both interfaces Ether1 and WDS1 to the same bridge1. > > Won't pass traffic the second Nstreme gets selected. > > > > The IP is assigned to the ether1 port on each of the sides. > > > > I have the same problem trying to do it without WDS and straight WLAN1. I > > can;t pass traffic the second Nstreme gets selected. > > > > Tom DeReggi > > RapidDSL & Wireless, Inc > > IntAirNet- Fixed Wireless Broadband > > > > > > ----- Original Message ----- > > From: "JNA" <[EMAIL PROTECTED]> > > To: "'WISPA General List'" <[email protected]> > > Sent: Wednesday, February 08, 2006 12:32 AM > > Subject: RE: [WISPA] Mikrotik Bridging w-Nstreme > > > > > >> > >>> However, it appears their may be is a flaw in config options, in the > >>> sense > >>> that there is no way to get NStreme to work in PTMP modes as a True > >>> bridge, > >>> as that would require WDS-AP and WDS-Slave which is not a supported > >>> config. > >>> Am I correct on this? Or when NStreme is used, can I safely use WDS- > >>> station, > >>> and be a true bridge? > >> > >> Tom, > >> > >> We are doing this. We have the base set to ap bridge, with dynamic wds > >> enabled using nstream and polling. Backhaul on the towers using wds > >> station > >> WDS with dynamic wds enabled using nstream and polling. We then have an > >> omni > >> off the routerboard and the Ethernet connected to a trango 900 base via > >> cross over. It is working as a full bridge and our clients get dhcp from > >> the > >> gateway server at the other end with no problem. I think this is what you > >> are looking at doing and If so it is working for us. > >> > >> John > >> > >> -- > >> WISPA Wireless List: [email protected] > >> > >> Subscribe/Unsubscribe: > >> http://lists.wispa.org/mailman/listinfo/wireless > >> > >> Archives: http://lists.wispa.org/pipermail/wireless/ > > > > -- > > WISPA Wireless List: [email protected] > > > > Subscribe/Unsubscribe: > > http://lists.wispa.org/mailman/listinfo/wireless > > > > Archives: http://lists.wispa.org/pipermail/wireless/ > > -- > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.375 / Virus Database: 267.15.2/253 - Release Date: 02/07/2006 > -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/253 - Release Date: 02/07/2006 -- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
