Jump to content

dan24

Member
  • Posts

    4
  • Joined

  • Last visited

Awards

This user doesn't have any awards

  1. I've tweaked the radios in my office to the tune of ~350/350 real world and I think that's a huge win. These radios are only 2x2 mimo, lots of air congestion (urban area), and plenty of devices on my wireless networks. If you want to ensure that you're getting the best wifi experience possible, the things to tweak are: 1. What's Running Around You - Run some kind of a RF analysis. Most prosumer radios have this built in. Ubiquiti's UniFi line does a pretty decent job of scanning surrounding air space. This will allow you to put your devices on a clear channel to maximize the potential bandwidth. 2. Don't Leave Settings in Auto - Channel Width, Channel, and Transmit Power are the primary ways to tweak your signal. 2a. Channel Width - A larger channel width might sound appealing, but most of the time it leaves your wifi unstable and floods the airspace with garbage. Sometimes (when it comes to wifi) a slower network is a better network. 2b. Channel - This is arguably the most important setting. Selecting a clean channel can help your overall stability with less interference and also increase your max potential. 2c. Transmit Power - This is the easiest to mess up. Don't crank this to maximum (if your AP supports it). Imagine trying to talk to someone close to you, but they just yell at you. Directly in your ear. All the time. That's no fun for anyone and the message they're trying to get across is probably lost. Same is true for wifi. If your AP is 5 ft away from all the stuff that's using it, you can probably deal with a very low transmit power. 3. Band Steering - Some APs don't have this and some devices will ignore it even if they do. This tells the device that it prefers to use the 5 ghz spectrum instead of the 2.4 ghz spectrum. 4. Airtime Fairness - This forces slower devices to have an equal time slice as faster devices. Otherwise, it's "first come, first served" over wifi. If a device that only has a "g" radio is talking to the same AP as a device with an "ac" radio, over the same time duration the "ac" radio will transmit a lot more data. This is not that important if all devices on wifi are the same generation of 802.11. Hope that helps!
  2. More on Windspeed's points - don't let him install anything on your computer. This applies especially to certificates. If he installed a cert on your computer, he can potentially see all your encrypted SSL traffic by being a "Man in the Middle." Here's a tutorial on how it's done. It's a little dated, but the principles are the same. There are legitimate reasons for this, but it sounds like this guy is just being a pain in the ass. https://turbofuture.com/internet/Intercepting-HTTPS-Traffic-Using-the-Squid-Proxy-in-pfSense I'd get permission to install your own internet service. If he's trying to intercept all your internet traffic, I'd be looking for another option.
  3. Albeit I tried this months ago when it was fairly new, this service didn't work very well. I was on my work's gig link and I had some massive buffering issues. I might have maintained 60 fps, but graphics quality severely suffered quite often. Input lag wasn't the greatest either. I've put together AWS EC2 headless gaming VPCs using openVPN and Steam in-home streaming and that was better performance over a worse connection. I'd test the beta if you want to actually game over this; it could be a lot better than when I tried it last. As for compute - there are so many other vendors out there (Azure, AWS, Google Cloud to name the big players). I'm not sure that's within the scope of this service. Nvidia might even have their own VPS service already and I just don't know about it. Photo editing is an entirely different animal. My intuition tells me that a VPS is not the right space for this, mostly due to data transferring. For practicality, you'd have to move all your media to their servers first. My fiance is a photographer and let me tell you - we've moved over 100 TB of data to AWS for her clients to be able to download. Granted, our internet connection is screaming (1gbe internet and 10gbe LAN), but most people don't have that and our transfers still took a long long time. Could this work for a non-professional? Possibly, but would they even think to look for this type of service? Maybe that's you and I'm totally wrong! I think most pros would appreciate a way to edit on vacation without their iMac Pro, but unless you're able to upload 200GB of .CR2 over a hotel network, I don't see it happening. Cloud computing is a phenomenally powerful service that we're just starting to see enter some consumer markets. I'm curious how it will evolve, but I'm not sure I'd replace my desktop just yet. If the content doesn't originate on those servers, it has to get there somehow. Until our last mile of internet can support the transfer rates required for things like photos, video, etc... we're going to be doing the editing on our desktops. Probably more info and opinion than you were looking for, but it is an interesting topic! Dan
  4. What these guys have said is true, you can't forward the same port to multiple local hosts. If all of the above fails, (and depending on your networking skills) you could also ask your ISP for a large public subnet. If you get a /29 (5 usable IPs) vs a common /30 (1 usable IP) and your router supports this, you should be able to configure your router/firewall to do 1:1 NAT on multiple public IPs to corresponding local hosts (eg public 198.51.34.2/29 is 1:1 NAT to local 192.168.10.2/24, .3 to .3 etc). You would just need to open the corresponding ports (not forward) for each of these hosts on your WAN interface's firewall rules. PSA - there are security risks every time you port forward or open ports to the internet. These are not trivial. If you know the source address (where this traffic is coming from), I would restrict access to those open ports from that address only. pfSense is very intuitive and can handle these scenarios with a relatively shallow learning curve (pfsense.org). Also, be aware that some ISPs (like mine) will not allow me to have a subnet larger than a /30. I've had to setup a GRE tunnel to a local data center to get another public subnet routed to me (massive PITA). If none of this makes sense to you, it might not be worth it unless you have an interest in learning about networking. Cheers, Dan
×