> Don’t put 5 GHz on its own band. Uhh, do they mean "don't put 5 GHz on its own SSID"?
I thought it was considered and GOOD idea to put the 5 GHz and 2.4 GHz APs on different SSID is because some clients won’t connect to the faster one automatically. Or maybe it was because all traffic slow down to the lowest level. Is that no longer an issue? Or maybe these aren’t problems as long as the 2.4 and 5 access points are physically separate.
How we solved our office Wi-Fi problems
101–110 of 252 posts
Re: How we solved our office Wi-Fi problems
#102It’s only sort of passively mentioned in the article but I am AMAZED at the number of people who don’t hardwire everything they can. Obviously phones are out, but why not hardwire every laptop when it’s at the desk? If someone’s using a actual desktop computer like an iMac then what’s the point of Wi-Fi? Clear up the signal space and get a 100% reliable and ultra fast connection.
I'm AMAZED at the number of people that bother hardwiring everything they can for no reason when they have no interference issues.
Why go to all the effort of hardwiring every laptop at every desk?
If someone's using a laptop and moving around the office, why cable every desk when you can have gigabit wifi wherever you are?
Re: How we solved our office Wi-Fi problems
#103>Assign static IPs for infrastructure like access points. This makes them easy to reach when reconfiguration is needed Am I missing something, or did they buy consumer routers to use as access points? Triplebyte, I can save you a ton of management, troubleshooting, and learning time: switch to Ubiquiti Unifi or an equivelant now, youll have one pane of glass to reconfigure every device. The devices will talk to each…
Unfortunately because they're primarily in the business of slapping a slick web interface on Vyatta they don't have the skill required to debug the hardware acceleration. They don't have a single clue how to get RADIUS to work with their fork of Vyatta. And their support is fine for a home lab situation.
And let's not speak of the chronically overheating stuff.
Re: How we solved our office Wi-Fi problems
#104Also don't be afraid to hire someone to do a wireless survey - or do it yourself. Someone will walk around with a laptop, and try to find wifi blackspots/hotspots, and can recommend adjustments to AP power and/or placement.
Re: How we solved our office Wi-Fi problems
#105>Assign static IPs for infrastructure like access points. This makes them easy to reach when reconfiguration is needed Am I missing something, or did they buy consumer routers to use as access points? Triplebyte, I can save you a ton of management, troubleshooting, and learning time: switch to Ubiquiti Unifi or an equivelant now, youll have one pane of glass to reconfigure every device. The devices will talk to each…
I know it's not a common setup, but some of the ISPs that do fiber to high-rises offer that.
Re: How we solved our office Wi-Fi problems
#106Generally pretty solid advice. I say that as someone who is known for solving tough wireless problems. :-) On the cable termination part: I've (mostly) stopped crimping cables because I've had too many go flaky and don't have 4-5 figure testing equipment. One thing I'll add is that there are ends for solid conductor and stranded, make SURE you have the right ones for the cable you are using. These days I always just…
Been There, Done That, Bought The T-Shirt. Solid core is generally for premise wiring (PVC jacketed in walls, PTFE-jacketed through ducts); stranded is typically for patch cables. If you try like the first place I worked at in the mid-90's trying to put stranded ends on solid-core wire, breaking of tools and unreliable cables will make. There's cheapo Chinese cable tester kits on eBay, AliBaba and Amazon that do a go…
Re: How we solved our office Wi-Fi problems
#107>Assign static IPs for infrastructure like access points. This makes them easy to reach when reconfiguration is needed Am I missing something, or did they buy consumer routers to use as access points? Triplebyte, I can save you a ton of management, troubleshooting, and learning time: switch to Ubiquiti Unifi or an equivelant now, youll have one pane of glass to reconfigure every device. The devices will talk to each…
Fine, I'll say it: Ubiquiti is not suitable for a business environment. They don't have a good track record of pushing out security fixes. They've blatantly violated the GPL (and introduced security vulns in the process). Their "enterprise" features don't work well (e.g. hardware acceleration, WPA+Radius). Depending on what you buy the PoE may be non-standard passive or it may not. Unfortunately because they're prima…
Re: How we solved our office Wi-Fi problems
#108It’s only sort of passively mentioned in the article but I am AMAZED at the number of people who don’t hardwire everything they can. Obviously phones are out, but why not hardwire every laptop when it’s at the desk? If someone’s using a actual desktop computer like an iMac then what’s the point of Wi-Fi? Clear up the signal space and get a 100% reliable and ultra fast connection.
You could say the opposite I guess. I'm AMAZED at the number of people that bother hardwiring everything they can for no reason when they have no interference issues. Why go to all the effort of hardwiring every laptop at every desk? If someone's using a laptop and moving around the office, why cable every desk when you can have gigabit wifi wherever you are?
Re: How we solved our office Wi-Fi problems
#109* Most of my client devices are from Apple, and I easily got the best WiFi performance overall with 802.11ac-capable Airport Extremes, which is impressive given how relatively cheap they are. However, I'd like multiple SSIDs, and Apple gear can't do that (the guest network support doesn't count). Regardless, Apple is out of the game, so this isn't a long-term solution.
* The UniFi gear had terrible 802.11ac performance, even when my devices were in the same room as the WAP. At the time, I was using first-gen 802.11ac hardware from UniFi, so it's somewhat understandable, but the poor performance combined with 2 of the units failing within the first 6 months didn't leave a good impression.
* The Aruba Instant WAPs were reliable and got good performance (though not as good as the Apple WAPs), but I'm not a fan of their licensing. Without a support contract, it was possible to hunt down the latest firmware updates, but they didn't make it easy.
I recently bought a PC Engines APU3C4 with a mini-PCIe WiFi card and a couple of Chaohang antennas [1], and I'm contemplating build my own WAP. This would give me all of the configurability and tweaking that I want, and I could deploy it as just another piece of my personal little devops pipeline.
However, I don't know much about the RF side of things. I'm aware there's a lot of black magic involved, but it's not clear to me how much performance and/or range I'm going to lose by piecing together COTS stuff versus a professionally-engineered solution from Ubiquiti et al. If anyone who's reading has built their own WAPs, I'd love to hear from you.
Re: How we solved our office Wi-Fi problems
#110Earlier quoted context omitted.
Same as this , except with one change. For the router, use the (cheaper and more powerful) Mikrotik Routerboards. We don't use a Poe switch - we just use cheap Poe adapters and connect directly to the routerboard. For those who have never touched a Ubiquiti, configuring it could be a little iffy . I normally advise setting up DHCP 43 advertisement on the router before trying to setup the access points. But seriously,…
I'm currently using Mikrotik happily for AP and router needs, but considering switching to a Ubnt setup for ease of management that does not depend on Windows/Wine and without having to write my own configuration management tooling. As central management is somewhat lacking. What are your considerations for not choosing Ubnt for routing?