|
|
|
My views (except when I am looking out their windows) are not those of my employer.
hairy1: I thought that each individual device got an IPV6 address so no more NATing?
hamish225: oh i see, why would a residential customer need more than one ipv6 address though?
myfullflavour:hairy1: I thought that each individual device got an IPV6 address so no more NATing?
This. You'll still need NAT for IPv4 services though.
*Insert big spe*dtest result here*
hamish225: what's wrong with NAT?
Klipspringer: I make use of dyndns.org. If you router supports it its pretty easy to setup.
Its solved my problem of ever requiring a static IP address. But then Im not running a business
Twitter: ajobbins
My views (except when I am looking out their windows) are not those of my employer.
hairy1: Nothing is wrong with NAT'ing. I was referring to your post about why a customer would end up with more than one IPV6 address.
hamish225:myfullflavour:hairy1: I thought that each individual device got an IPV6 address so no more NATing?
This. You'll still need NAT for IPv4 services though.
what's wrong with NAT?

I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup. Opinions are my own and not the views of my employer.
Zeon:hamish225:myfullflavour:hairy1: I thought that each individual device got an IPV6 address so no more NATing?
This. You'll still need NAT for IPv4 services though.
what's wrong with NAT?
NAT is horrible and breaks many things as well as making it harder for developers of thing like voice/video real time communications. I have public IPv4 on all my server salso as it makes DNS sooo much simpler
insane:Zeon:hamish225:myfullflavour:hairy1: I thought that each individual device got an IPV6 address so no more NATing?
This. You'll still need NAT for IPv4 services though.
what's wrong with NAT?
NAT is horrible and breaks many things as well as making it harder for developers of thing like voice/video real time communications. I have public IPv4 on all my server salso as it makes DNS sooo much simpler
That's fine for frontend servers, however security is all about layers of defense, having a 'target' on a publicly routable address allows someone one step closer to your soft gooey center which you want to protect.
Too many times I have seen someone botch up an ACL or firewall policy allowing WAY more access to servers than should be allowed.
Totally agree that NAT makes some things difficult though
*Insert big spe*dtest result here*
Lias: Out of curiosity, anyone know how much a /27 or /28 would cost these days?
I've long toyed with the idea of getting one for home, but I suspect it would be expensive these days.
|
|
|