4

Fuck you Windows 10!
Trying to help a sales guy setup his adapter to work on a manual network setup (not DHCP). It shows familiar IPV4 settings and then I see this:
"IPV4 Subnet Prefix Length" I decided it was related to netmask "255.255.255.0" or whatever. Tried the number 3. Worked fine. Talked to a colleague and he said it should be the bits of the netmask. So 24.

So WHY THE FUCK does Windows 10 on an update change the way we setup manual networks that has been in use for 40 years?! I realize you can still do the netmask version via Control Panel. I get that. However, the last time I helped this sales person it asked for netmask using the exact method for setting up manual network setting. So why change this on an update?

I like Windows 10 mostly, but this kind of fuckery is stupid. Stop changing shit just to change shit!

Comments
  • 7
    Don't blame them because you don't know the technical terms. It's okay to be wrong sometimes. The original "written out" way to define the netmask is obsolete and that's it.
  • 2
    It's kind of the reason I was stalling to switch from ifconfig to ip :) the verbose netmask feels more familiar.

    Well, I guess it's time to learn alternative ways now! For both of us
  • 1
    @Kimmax Certain part of networking really feels like the 80s.
Add Comment