Let's settle this once and for all

this

...

The 10. class A is easy for organization. Second octet is Region or Site, third octet is VLAN / subnet.

10.0.0.0/8 - wired and internal wireless
172.16.0.0/20 - Remote access VPN, VPN tunnel interfaces, out of band management, other misc. L3 interfaces
192.168.0.0/16 - Untrusted networks (e.g., guest wifi) and DMZ

How you assign private IP space is completely arbitrary. The only important part is that it is organized and simple for you as an admin to understand.

based and checked

IPv6

What's the fucking difference?

Attached: 1549917947101.png (303x279, 18K)

I HATE the fact that both 192 and 168 are 1 off from being primes

10.0.0.0/8 obviously, that's what we run at work

I use 224.0.0.0/24 for all my devices. It just werks

Attached: 1462173244607.jpg (441x228, 39K)

patrician's choice

This

Me stupid when it comes to ayepees

fc00::/7 is the only correct answer

Engie for a big network here
10.0.0.0/8 is taken by a sister network
172.0.0.0.0/8 was fucked up by my predecessor. Yes, all of it, not just 172.16.0.0/12.
192.168.0.0/16 is getting quite crammed.
IPv6 is not an option yet.

FML.

IPv5 doesn't have this problem.

If I just type the IP of a website into my browser, does my request still go through via dns.
>Yeah, actually I am that clueless.

I remember reading an article a few years ago about how the US DoD, which has 11.0.0.0/8, finally started actually using it. For decades it'd never been announced, then it started. apparently a lot of places had a really bad day because they'd either gotten cramped in or just made a mess of 10/8 and had been squatting on 11/8 as ersatz private address space.

>using default addresses
>not using 10.x.x.x
shiggydiggy it's like you want to be gateway exploited

are you me?

No Satan. You are unique.

>triple sixes
absolutely based wooooooo

Attached: 1551026899736.gif (700x704, 295K)

Also, when is it appropriate to use question marks.

>2019
>IPv4

Attached: 1526751052715s.jpg (250x183, 8K)

Well, given our mess with 172/8, and that Google also lives within 172/8, we had to get creative with the routing in order for "the Internet" to work (google.com, gmail, and the sort)

>he works in a teeny weeny indie studio with no legacy
I envy the peace of mind your insignificance must bring you

172.16.x.x

>not using IPV6

get with the time gramps

>Wanting to stay on a system that WILL run out of space soon
Ishiggydiggy

0.0.0.0 god tier

169.254.x.x

Attached: 1481161629826.gif (499x499, 45K)

currently 10.11.2.x/24, don't ask me why it's top secret

Attached: 1551084294735.jpg (240x240, 24K)

I'd love to get out of it, but The Powers that Be aren't interested, and IPv4 werks "Just Fine". Of course, they then complain about all the NATting as if it were my fault.

NAT is a hassle, but it's about an order of magnitude less hassle than properly deploying IPv6.

IPv6 will remain way, way, way down the list of priorities until there's some website or service out there on the internet that is only accessible on it. Some website or service that people care about, that is, not just a few "test your IPv6" pages. Such a service is unlikely to ever appear while its the case that everyone has IPv4 connectivity but only some have v6 connectivity.

A shame, isn't it? What would need to happen to help push the movement for IPv6? I liked the idea of new sites being IPv6 only but that requires enough people to have IPv6 access in the first place.

>192.168.0.x
There's chinks squatting in ur network
>192.168.1.x
Pajeets sitting between .34-.72

Use 10.x.x.x. and stop being a nigger. C-class isn't scalable for shit

>What would need to happen to help push the movement for IPv6? I liked the idea of new sites being IPv6 only but that requires enough people to have IPv6 access in the first place.
Tragicomically, in order for my org to contemplate using IPv6, our sister orgs would have to be using it, which they aren't using because their sister orgs (us and each other) aren't using it, and nobody wants to be the first one to migrate because they wouldn't have anybody to talk to and make it worthwhile. Of course, taking any such step with two orgs at the same time would be impossible.

So in order for my group of orgs to migrate to IPv6, it should already have migrated to IPv6.

It's the suits, fucking suits I tell you.

webpages (most) will remain (at least partially) on ipv4. IOT, will on the other hand, be using ipv6.

>IOT, will on the other hand, be using ipv6
Not in its entirety, unfortunately.

>What would need to happen to help push the movement for IPv6?
essentially there's no way to make it happen at anything other than the glacial pace its going. The expansion of address space benefits people who aren't currently on the internet but might want to be in the future, while all the work has to be done by people who are already on the internet.

There have been a few big shifts to IPv6 - Facebook in 2014 is the one you hear about the most. They moved all their internal networking to IPv6, they only do IPv4 at the edge to talk to the outside world. But the reason they went to all the trouble was because IPv4 stopped working for them - the short version of it being due to exhausting the whole of 10/8. That is, IPv6 wasn't just a good-for-the-internet, right-thing-to-do, warm-fuzzy-feelings project, it was something they did because they had to to solve real problems. That's a common theme in IPv6 deployments, it only happens when there's a large benefit to the organization doing the work. And that doesn't happen very often.

Also keep in mind we're talking about dual-stack here, talk v6 to what you can, support v4 for everything else. v4 won't start to go away until everything (or within delta of everything) can talk v6, and we aren't even close to that today. IPv4 will be with us for decades to come.

127.0.0.0/8

i unironically use a 172.x.x.x /28

172.16.0.0

the question is, which one is faster?