[WISPA] Email Providers?
Hi Folks, We're looking at possibly migrating our customer mail from local servers to a cloud provider (full service, not a build-our-own at AWS/google/azure/etc hopefully), though the discussion is still very much at the "talking about it" stage. Assuming that anyone here uses a cloud provider for email, does anyone on the list want to share who they are using and what their migration experience was like? Pricing would also be great, assuming no NDA. Thanks! Tim Densmore ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
[WISPA] GPON
Hi Folks, Has anyone deployed the ubnt GPON solution, and are they happy with it? If not, what are folks using for GPON? We've been using zhone gear, and while it has been reasonably solid, the management interface could be better, so we're looking for other options. Thanks for any info, Tim Densmore ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] help with kubuntu and Dude
It doesn't appear that you're escaping the space in "Program Files" - try: kdesudo wine ~/.wine/drive_c/Program\ Files/Dude/dude.exe Post full error otherwise. On 09/05/2014 07:23 PM, Scott Lambert wrote: why are you trying to run a windows app with root privileges? it might help to know what the "..." was. it might not. On September 5, 2014 7:37:36 PM CDT, "J. Van Kort" supp...@oregononline.net wrote: running kubuntu 14.04LTS cannot get Dude to run in root mode. Having issue with the proper command line syntax. Dude is installed at: /home/.wine/drive_c/Program Files/Dude/dude.exe Attempted command line entry: kdesudo wine ~/.wine/drive_c/Program Files/Dude/dude.exe generates an error. #2758 Cannot find /Home/. Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Net neutrality, The beginning of the end
On 07/31/2014 11:15 AM, Joe Fiero wrote: Netflix, Hulu, and the like have created a business model where they have no cost to deliver a product to their users. They are using the infrastructure built and paid for by others, then stirring up the ignorant masses to complain to the FCC about the free Internet. Hi Folks, Just a question - is this the general consensus among list members? I ask because in a recent similar thread on the NANOG list there was a WISP owner presenting the same argument. I'm curious whether this is the viewpoint held by many WISPs. Thanks, Tim Densmore ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Net neutrality, The beginning of the end
Absolutely - I didn't mean to rekindle it here. I'm just surprised when I see that kind of viewpoint, and I'm I'm trying to understand it a little better, hopefully with a lot less saber rattling than in that thread. I currently agree with most of the posters in the NANOG thread, but I've been wrong before. Many, many times. Tim On 07/31/2014 08:42 PM, Mike Lyon wrote: And that was an extremely painful thread on NANOG, BTW On Thursday, July 31, 2014, Mike Lyon mike.l...@gmail.com wrote: Not this WISP... -Mike On Thursday, July 31, 2014, Tim Densmore tdensm...@tarpit.cybermesa.com wrote: On 07/31/2014 11:15 AM, Joe Fiero wrote: Netflix, Hulu, and the like have created a business model where they have no cost to deliver a product to their users. They are using the infrastructure built and paid for by others, then stirring up the ignorant masses to complain to the FCC about the free Internet. Hi Folks, Just a question - is this the general consensus among list members? I ask because in a recent similar thread on the NANOG list there was a WISP owner presenting the same argument. I'm curious whether this is the viewpoint held by many WISPs. Thanks, Tim Densmore -- Mike Lyon 408-621-4826 mike.l...@gmail.com http://www.linkedin.com/in/mlyon -- Mike Lyon 408-621-4826 mike.l...@gmail.com http://www.linkedin.com/in/mlyon ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] IPV6 address allocation
Networks longer than /64 break SLAAC which may be desirable or undesirable, depending on what you're doing. The info at this site is what I frequently see/hear currently - http://www.ipbcop.org/ratified-bcops/bcop-ipv6-subnetting/ In general: Subnet at the nibble boundary Do everything you can to make sure that you can aggregate routes Use /48 for customer allocations (though many people use /56 currently) Use /64 or /126 or /127 (or LL) for P2P links Use /128 for loopbacks As with anything, look at what other forks are doing, read the BCPs and RFCs, and then do what you feel makes the most sense. TD On 12/10/2012 1:07 PM, Arthur Stephens wrote: Thinking of splitting our /32 up into large enough subnets to cover existing and future equipment on our network. Seems that assigning /112 IPV6 to currently assigned /24 IPV4 networks would be more than enough addresses. Any thoughts? Ideas? -- Arthur Stephens Senior Sales Technician Ptera Wireless Inc. PO Box 135 24001 E Mission Suite 50 Liberty Lake, WA 99019 509-927-7837 For technical support visit http://www.ptera.net/support - This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company. ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Mikrotik Books/Study Materials
On 11/28/2012 9:47 PM, Butch Evans wrote: On Wed, 2012-11-28 at 15:46 -0500, Blair Davis wrote: Learn RouterOS. By Dennis out at Link Technologies A better book, IMO, is this one: http://www.amazon.com/RouterOS-by-Example-ebook/dp/B006U3MP7W for kindle andhttp://www.learnmikrotik.com/index.php/get-the-book.html for the paper. So, what I guess I'm hearing is that the two obvious book options on amazon are more or less the *only* two options. I Have read some of ROS by Example, and while I'm sure it's a fantastic book for some purposes, it's not really what I'm looking for (contains lots of motivational speak, contains lots of winbox screenies, doesn't appear to cover the CLI, and doesn't give an in depth view of the technologies). The other book gets a couple of really bad reviews, but I'll certainly download the kindle sample and read it. Anyone have any info on the videos that Dennis is selling? Looking at them, I can't even tell how long each is or what topics are covered in each, etc. Thanks again, TD ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
[WISPA] Mikrotik Books/Study Materials
Hi Folks, Hopefully this isn't too far off subject for this list. I want to start learning a little more about mikrotik, but I'm having trouble finding good study resources. I've looked at the wiki, and while good, it's more of a cookbook than a tech-pub, at least IMO. I don't want How to replace your linksys with an MT and don't need a lot of extra text to slog through that's mostly present to keep me engaged/motivated. I'm very used to reading Cisco's doc-cd (or whatever they're calling it these days) and honestly prefer technically rich but direct and to the point. I'd also prefer CLI examples rather than looking at rescaled screenies from winbox. Does such a beast exist? If not, what's the standard way to delve in to ROS? As an example of what I'm running up against, I'll use queuing. I use DSCP markings on the network I manage to differentiate traffic. I was stunned to discover that MT (apparently) can't simply match existing DSCP markings and act on them, but instead requires me to match them, give them some internal packet mark, and then act on those non-DSCP markings. I wanted to better understand what was really going on inside the router, and wanted to verify that what I thought I understood was really the case. I read the wiki pages on HTB and Queues, but I still don't truly understand how to guarantee, say EF tagged traffic, a certain amount of bandwidth other than limit-at= and a higher relative priority setting (priority=1?). But is that single queue enough, or do I also need to create what in cisco-land would be class-default? TBH, I still don't even understand how and what MT uses internally to mark packets with tags like VoipTraffic or whatever. Obviously the packet isn't being marked with an ascii string... Ideas? Better place to ask this? Thanks! TD ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Ubiquiti Radios as routers
Hi Fred, I think a lot of the confusion here comes from the fact that you're using generic terms like switching and VLAN to describe complex Metro-E/Carrier-E scenarios. Standard VLANs break up broadcast domains, but they don't create virtual circuits or provide total isolation - this is one of the reasons I initially asked what you were describing. Metro-e q-in-q with stag/ctag UNIs and EVCs behave much differently than standard packet switched ethernet dot1q VLANs in that regard. I'd reference the different metro-e IEEE standards if I were smart enough to keep them all in my head or unlazy enough to look them up. Tons of info available at metroethernetforum.org for folks who are trying to figure out what I'm talking about. I'd be extremely impressed to learn that you could do a decent metro-e roll-out with ubnt and mt. In the WISP world, I'd expect single-tagged dot1q VLANs to be enough to differentiate customer traffic, even in large-ish MPOP scenarios. How many POPs generally hang off a single network segment before hitting a router? Thanks for the interesting discussion! TD On 10/12/2012 10:14 PM, Fred Goldstein wrote: I'm not sure we're talking about the same thing. It is allowing only the VLAN to go from A to B, while nothing else goes to A or B, and the VLAN is invisible to everyone else. Which is really virtual circuit behavior; VLAN is the legacy name of the VC ID. In CE switching, then, the VLAN receives no broadcasts from anyone else on the switch or network, and sends no broadcasts outside. What goes onto that mapped port, or onto a VLAN pre-tagged to go to that port, is totally and completely invisible to all other users. So it's secure enough for public safety use on a shared PMD. This is different from a bridge, where broadcasts go everywhere. One type of MEF service (EP-LAN) does actually emulate a LAN with 2 ports and broadcasts among them, but the more common EPL and EVPL would not know a broadcast frame from anything else, since they just pass the MAC addresses transparently. ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Ubiquiti Radios as routers
Hi Gino, Pardon my ignorance, but what's Mk? TD On 10/13/2012 09:33 AM, Gino Villarini wrote: It can be done with Mk and Canopy, both support qinq ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Ubiquiti Radios as routers
Hi Fred, Could you expand a bit on this? It sounds like you're describing what I'd refer to as virtual circuits rather than switching. Are you setting up per-customer VLANs or something like that? TD On 10/11/2012 06:35 PM, Fred Goldstein wrote: Switching, though, is what Frame Relay and ATM do, and now Carrier Ethernet is the big thing for fiber. It uses the VLAN tag to identify the virtual circuit; the MAC addresses are just passed along. Since it's connection-oriented (via the tag), it can have QoS assigned. I think it's theoretically possible to tag user ports, route on tags and set QoS on RouterOS, but it's not obvious how to do it all. Switching doesn't pass broadcast traffic; it provides more isolation and privacy than plain routing. Mesh routing then works at that layer, transparent to IP. It'll be interesting to set up. ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Ubiquiti next product.... another router?
Hi Matt, As an edge/border router? Will it take full IPv4 and IPv6 tables? Has anyone seen what it takes to tip one over with PPS? I'm not sure about these answers for Tiks, either, but positioning a software-based gui-box as an edge router seems like a recipe for disaster to me. I want to stress that this means *seems to me* not that I'm saying it is for certain. I'm not looking to start fights, arguments, or religious wars here, I'm honestly interested in assessments of the gear. Thanks, TD On 9/14/2012 9:36 AM, Matt Hoppes wrote: Yes... as soon as these things hit production I will be replacing all of the MikroTiks in my network! ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] Ubiquiti next product.... another router?
The GUI wasn't meant to be the focus of my question, sorry if it was a distraction. I see that they're comparing the edgemax to the 3900 now, so nevermind. Edge means something different to me than it means other (marketing?) folks, apparently. Positioned against the 3900, especially starting at $99 I'll be interested to see what it can do. Thanks! TD On 9/14/2012 9:56 AM, Matt Hoppes wrote: It doesn't have to be GUI driven. You can configure it via CLI just like any other router. To that argument a Cisco can be setup with a GUI - but most people don't. I don't have the numbers handy but there was a Tolly report that came out showing the PPS I believe. ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
