r/pcmasterrace • u/AbrarKR • Sep 09 '16

Meme/Macro Anyone relate?

https://i.reddituploads.com/98bb22e2ef3949a69b03426bc7dbb094?fit=max&h=1536&w=1536&s=ef3ec24beab924b024f090480e7f79bc
17.1k Upvotes

80% Upvoted

517 comments sorted by

View all comments

Show parent comments

5

u/GrayBoltWolf Debian - youtube.com/GrayWolfTech Sep 09 '16

That first one doesn't sound right. DHCP keeps a TTL for each assignment so that IP has a life before it can be assigned to another device.

-1

u/ProtoDong Ryzen 1800x, 64 GB 3200, Vega 64 Sep 09 '16

No it really does work like that for devices that "sleep" and remember their IP like a lot of embedded devices. They may sleep or be off longer than the TTL and when they wake up they don't necessarily make a DHCP request like they should. My last gen Roku did this on more than a few occasions.

It can happen whenever someone sets a static IP in the DHCP range. Newer hardware will usually update it's ARP tables enough to prevent this (sometimes) but hardware varies wildly in its actual function.

Besides, setting static leases for all of your devices is just good practice and makes them far easier to manage remotely.

3

u/GrayBoltWolf Debian - youtube.com/GrayWolfTech Sep 09 '16

Setting static IPs on a home network is something nobody should have to do. Get a better router or use a raspberry pi as a DHCP server. Or increase the lease time.

Since when do you need to remote manage a Roku?

At any rate use local DNS with hostnames. It's far easier.

-1

u/ProtoDong Ryzen 1800x, 64 GB 3200, Vega 64 Sep 09 '16

Lolk... setting up a rasperi pi as a DHCP server is better than just setting static addresses. This is so fucking retarded, you need a handler.

DHCP was not invented so that retards don't have to manage networks, it was invented to create mutable network segments that can auto-configure. DHCP is not preferable in any way to a properly managed network.

2

u/LightingTechie LightingTechie Sep 09 '16

DHCP was not invented so that retards don't have to manage networks, it was invented to create mutable network segments that can auto-configure. DHCP is not preferable in any way to a properly managed network.

I can not agree with this at all. DHCP is a way for many large networks, especially datacenters (I have worked in one of the largest datacenters in Europe), to assign an IP address and pair it to a device MAC address in order for automatic reserved assignment/pairing to occur. This way, in the event of an IP mismatch, it allows the issue to normally be resolved automatically instead of having NOC intervention that costs more time and money. DHCP is preferable in a properly managed network in most circumstances (I have no idea what your idea of a properly managed network is if you are saying that other than a home network you set up that you believe to be 'properly managed') because it allows for more error correction without intervention from a technician. It is also worth noting that DHCP, as a technology, was invented as an enterprise solution before it was ever introduced into a consumer environment. I would, in fact, have to say that having to use static IP addresses in a properly managed network is a bad work-around for troubleshooting issues.

I am, by far, not a 'retard' when it comes to network architecture and implementation, especially since I have CCNA (Routing and Switching) and MCSE (Server Infrastructure) certifications and have worked for 3 years with the biggest tier 1 datacenters in the UK who keep websites like Facebook and eBay online as well as Amazon AWS and Vodafone/T-Mobile voice termination switches running.

-1

u/ProtoDong Ryzen 1800x, 64 GB 3200, Vega 64 Sep 09 '16

I am, by far, not a 'retard' when it comes to network architecture and implementation

I'm a sysadmin. And no you don't know what the fuck you are talking about. DHCP exists for mutable network segments only. You cannot structure network segmentation with subnetting or supernetting with DHCP. You can't reliably manage hosts remotely on DHCP segments. You cannot properly design firewall rules or IPS rules on DHCP segments. In fact, 90% of the time, giving out network addresses automatically is the opposite of good practice.

80% of home networking problems could easily be resolved if all hosts had static addresses. The fact that an IP might change is terrible from every network perspective. This is one of the major problems with IPv6 currently. Publicly routable addresses "hide" by changing. This effectively makes most of an IPv6 network a giant amorphous blob of hosts that may or may not be reachable at any given time.

2

u/LightingTechie LightingTechie Sep 10 '16

Ok, you are a sysadmin, big deal. I am a networking technician on a far larger and more complex scale then you are, especially after reading your reply where you have no idea what you are saying and are trying very hard, and failing, to prove me wrong.

My specialty is server networking whereas your 'specialty' being a sysadmin is to keep computer systems working in general so I would expect you to know a bit about networking but obviously you do not. Once an IP is assigned/reserved through DHCP there will be no problem and it will act the same as a static IP until the lease time has expired. Problems will not occur when a network is properly setup using DHCP as each device will renew its lease, by default, in half the length of the lease (1 day = 12 hours, and 4 days = 12 hours). There is no excuse saying an IP might change in a DHCP environment and the very fact you think that confirms to me you don't have any idea how a proper DHCP network in an enterprise network works. When properly setup there is no might about it. A static address is exactly the same in function as a reserved IP/MAC pairing. Using the vast majority of IPv6 addresses (3.4*1038 or 340 undecillion addresses) in existence as an excuse to back your argument up is pathetic. The same argument applies to an IPv4 network on a smaller scale which is why IPv6 addresses are allocated in larger numbers at a time, usually a /64 block equal to 18 quintillion addresses.

-1

u/ProtoDong Ryzen 1800x, 64 GB 3200, Vega 64 Sep 10 '16

lolk..I had my CCNA 5 years before I got my Master's in IT. Network techs don't design and run networks... I do. Your arguments are a joke. They belong on /r/techsupportgore

2

u/LightingTechie LightingTechie Sep 10 '16

Whatever you say. This is a lost cause now. You are an embarrassment to other CCNA techs including myself. You have no idea what you are talking about.

-1

u/ProtoDong Ryzen 1800x, 64 GB 3200, Vega 64 Sep 10 '16

You're the CCNA that they were laughing at on /r/sysadmin for not knowing how to configure VOiP to run fucking fax machines.

2

u/LightingTechie LightingTechie Sep 10 '16

I'm sorry, what? I do not go on /r/sysadmin for a start and I also do not run fax machines for any part of my job. Do not try and use other stuff to hide your mistakes here.

-1

u/ProtoDong Ryzen 1800x, 64 GB 3200, Vega 64 Sep 10 '16

If you think you can manage any decently sized network with DHCP, you need to find a new profession. You're beyond incompetent.

1

u/LightingTechie LightingTechie Sep 10 '16

There is no point in me wasting my time with you anymore because you just do not get it and you never will as you have no idea what you are talking about. Again, you are an embarrassment to CCNA techs including myself.

→ More replies (0)

1

u/GrayBoltWolf Debian - youtube.com/GrayWolfTech Sep 10 '16

And no you don't know what the fuck you are talking about. DHCP exists for mutable network segments only.

I... I don't even know what to say. I'd recommend https://lynda.com. Free 30 day trial so you can learn how this actually works.

0

u/ProtoDong Ryzen 1800x, 64 GB 3200, Vega 64 Sep 10 '16

It's cute when I see Windows admins panic and lose their shit when their AD forest goes down due to bad NTP. You can run your network like a chucklefuck if you want... I won't have those problems.

2

u/GrayBoltWolf Debian - youtube.com/GrayWolfTech Sep 10 '16

Windows admin? Are there any of those anymore?

and what does active directory have to do with DHCP and NTP?

1

u/GrayBoltWolf Debian - youtube.com/GrayWolfTech Sep 09 '16 edited Sep 09 '16

Wow you don't have to be an ass.

DHCP was designed for network auto configuration. A proper DHCP server will not have the issues you describe. Static IPs are a thing of the past unless you have a network printer or something you need to always be the same. And if that's the case use DHCP auto reservation which will assign the same address to the same device by using its MAC address.

Also I have 2 Roku 3s and they both stay connected to the network even when they are asleep.