Couple of pointS:
DHCP
Really? Really? Please explain how, once you have a (good) lease, there is some impact?
(DISCLAIMER: I use either fixed IPs or reserve addresses based on MACs, but that's a personal preference of mine for various reasons -- NONE of which have anything to do with somehow communication getting messed up magically.)
WiFi
Needs to be mentioned a few thing:
1) You (most likely for all the following statements) have a cell phone (or four if a family). You have tablets. You have an AppleTV/Roku/fire/whatever. You have a smart TV. You have Hue light bulbs. You have a security cam/front door cam/baby cam. You have a smart fridge. You have IoT toys. Etc. etc. People have a lot more devices on their LAN than they think. That's all potential competition.
2) WiFi is in *UNLICENSED" spectrum. There is a lot of pollution in unlicensed spectrum. Few sub-points here:
a) non-wifi communication. (Cordless phones aren't really a thing anymore, and most baby monitors are wifi now, but still potentially legacy device that are easy to forget about.)
b) non-communication pollution (devices that produce noise unintentionally in the spectrum)
c) Neighbors. You most likely have them. And they have all the devices that you do, if not more. If you live in suburbs, bad enough. If you live in, say an apartment building in San Fransisco, good luck getting a good signal more than 3 feet from your AP.
[spoiler]Yeah, wireless has gotten much better at addressing these issues. But still not 100%. Plus *shudder*, some people still running 802.11b hardware...[/spoiler]
English
-
Edited by An Oracle: 8/27/2016 10:05:49 PM[quote]Neighbors. You most likely have them. And they have all the devices that you do, if not more.[/quote] Good point. I told someone else that they may want to lower their channel width in hopes of finding a less noisy channel. Your bandwidth is decreased, but that often isn't a big deal. [quote]Yeah, wireless has gotten much better at addressing these issues. But still not 100%. Plus *shudder*, some people still running 802.11b hardware...[/quote] And don't forget that if any of your random equipment runs b and is far away from the router, it could be connecting at speeds as low as 1Mbps, or whatever your lowest mandatory rate. Since all of your wireless hosts are competing over your wireless network, that piece of equipment can hog substantial time on your wireless network at the detriment of much faster hosts, like your console. I'm not sure most consumer grade routers allow you to disable lower data rates. Also, unrelated, but something I have always found funny: Liquid sucks for wireless signals. I've had to place directional antennae in warehouses that have shelving stacked high with liquid products.
-
And you'd be surprised at the number of building materials that can make a house into a pseudo-faraday cage. In term of the "communicate at the lowest speed", there is an issue that used to affect 802.11 (and may still on the newer standards???), but APs used to function more like a hub than a switch, in the sense that all bandwidth was shared. So there would be a bottleneck there. What I don't know is if they act like USB hubs used to (think is fixed in 3.0??) and drop all communication to least common denominator. If so, that makes that 1.0 mbps you spoke of even more painful. Fairly certain all modern gear doesn't, but we were talking about ppl on older hardware...
-
DHCP just makes this easier. I personally use DHCP with reservations for all my kit, and a DHCP scope with 2 free IPs for guests. On WiFi I thought I covered that by saying just don't use it for online PvP games. I mostly just did it for simplification purposes. I could go into detail about the 7 layers of the OSI model, and describe how packets are put together on your network, but most people only need to know how to work their routers control panel. Good info there thanks
-
I still fail to understand how a dynamic address (once negotiated and no conflicts or other issues) is a problem. And the points about the wifi, were to address the "just don't use it" statement... or more particularly to address the "but I use it with no problem" replays. Trying to point out to those people that there are real world problems (that are easy to understand) that go beyond a simple "don't do it"
-
Well Dynamic adresses can change, and normally this is OK for most things, but if your port forwarding then it immediately breaks all the good work you just did. While it will always try to give you the same address, it doesn't always acomplish the task. Also in the case of DHCP with uPnP, the routers uPnP can fill up. Think about a dhcp change then all the ports get auto forwarded, then it changes in a few days and the port tables fill up. This will lead to a router crash in most cases or an intermitant slowdown on the route as the memory slowly gets eaten up.