{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/27/2016 9:16:04 PM
1
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
English
-
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.
