Browse Source

add draft blog article

products
Nico Schottelius 3 years ago
parent
commit
96868313b7
  1. 68
      content/u/blog/what-is-wrong-with-ipv4/contents.lr

68
content/u/blog/what-is-wrong-with-ipv4/contents.lr

@ -0,0 +1,68 @@
title: What is wrong with IPv4?
---
pub_date: 2019-10-01
---
author: Nico Schottelius
---
twitter_handle: NicoSchottelius
---
_hidden: yes
---
_discoverable: no
---
abstract:
Why are people talking about moving to IPv6?
What is wrong with running application on IPv4?
---
body:
## TL;DR
Nothing is wrong with IPv4. There is just too less of it.
## IPv6 vs. IPv4 for end users
At home
Not big difference at the moment
But: big potential for independence
### Example: home automation
All devices talk to a vendor
You already have a bridge. Why sending data elsewhere?
If enough IPv4: give all devices a public address. Can directly
connect to your home bridge. But you can't. NAT.
## IPv6 vs. IPv4 for developers
This is the section I like most. Forums with posts from developers who
recommend to turn off IPv6, to ignore it, complain about the new
format.
All of these are valid points. IPv6 is an additional protocol that
applications need to handle.
New apps: develop IPv6 only.
## IPv6 vs. IPv4 for ISPs
- SKT
- Multiple NATs
- Need to run IPv6 anyway to provide reachability
- Easier to run end point NAT64
## IPv6 vs. IPv4 for cloud providers
Probably highest pressure for IPv4 users is on cloud
## Other applications
If you know about other applications or want to enhance one of our
configuration, we invite you to join the [IPv6
chat](https://IPv6.chat) or [write to us on
Twitter](https://twitter.com/ungleich).
Loading…
Cancel
Save