I tend to look at this as if it were ethernet, right or wrong. Most of my customers that need a public ip for a specific reason I would rather pseudobridge as if it were a bridge on an ethernet or cable system. This helps me so that I don't have to mess with port forwarding etc for special aps in mostly incoming aps to the customer. I have run into the occasional outbound from the customer ap that doesn't like the nat etc we have for our usual customers. That way they deal with whatever networking issues instead of me having to mess with it. Its just simpler for me. For the few pseudobridges I have instituted so far, I have not seen a problem with traffic and it has worked well for the customer (mostly businesses or home offices). For instance, I configured a pseudobridge for a customer who ran certain aps and his performance increased, aps worked and he no longer had complaints. I have not had issues with performance on the ap as a result. Now maybe if I had a lot of them on a particular AP that would be different. But so far no.
Terri Kelley Network Engineer 254-697-6710 This email message is intended only for the named recipient(s) above, and may contain, together with any attachment(s), confidential information that is privileged. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, copying or distribution of this message and any attachment(s) is strictly prohibited. On Apr 30, 2008, at 3:18 PM, Butch Evans wrote: > On Wed, 30 Apr 2008, Keith Barber wrote: > >> Right, which we'll have a fair split of customer's that don't have >> publics running in plain station mode. But in some of the business >> districts about 90% of those clients are going to be putting the >> public IP into their equipment, with the ap as the gateway, so we >> don't have to do any NATing above their router. > > For most of them, it may work without issues to use pseudobridge in > MT (or any other "ethernet bridge" gear), but if there will be a lot > of INBOUND connections, then you may see trouble due to the > realities of how 802.11 works. If they just need the public IP on > their gear so that they can establish OUTBOUND connections (for > corporate VPN or whatever), then they should work just fine with > pseudobridge. > > -- > ******************************************************************** > *Butch Evans *Professional Network Consultation * > *Network Engineering *MikroTik RouterOS * > *573-276-2879 *ImageStream * > *http://www.butchevans.com/ *StarOS and MORE * > *Mikrotik Certified Consultant *Wired or Wireless Networks * > ******************************************************************** > _______________________________________________ > Mikrotik mailing list > Mikrotik@mail.butchevans.com > http://www.butchevans.com/mailman/listinfo/mikrotik -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.butchevans.com/pipermail/mikrotik/attachments/20080501/0d0ebefb/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: LogoHzlsigtest.jpg Type: image/jpeg Size: 2158 bytes Desc: not available Url : http://www.butchevans.com/pipermail/mikrotik/attachments/20080501/0d0ebefb/attachment.jpg
