4 ms·

>it took me less than a week to understand enough to be able to set up an IPv6 LAN. Don't mean to brag but it took the 12 year old me less than an afternoon (a

>it took me less than a week to understand enough to be able to set up an IPv6 LAN. Don't mean to brag but it took the 12 year old me less than an afternoon (armed with a CISCO book) to understand IPv4 syntax/routing/ARP/DHCP + whatever and roll it out to my 2 computers lan. The difficulty curve jump from IPv4 to IPv6 is humongous (IPv6 + ancillaries took me 2 days to setup in my home, and that's with a decade of IT experience.) The issue is there are just so many officially right ways to do the same thing. Even assigning 'static' addresses has 3 official methods. Yes I get why there are so many of them (flexibility!) but it's a lot of stuff to learn and put together.

Arnavion 5y ago
Did you misread the 6s in my comment as 4s? I'm not sure why you're telling me that IPv6 is more complex than IPv4 when my comment said nothing to the contrary.
- ipv4idio 5y ago
  He is telling you because you come off as a know it all who can figure everything out while at the same time you question why can't other people figure out the same as you can while at their own home labs. Apparently though you couldn't figure out this answer to your obviously self answerable question.
  - Arnavion 5y ago
    >who can figure everything out If this is what you got from my comment, it seems you need to read more closely. I listed specifically what I did learn, pointing out how it was not everything but was enough for setting up a LAN.
josteink 5y ago
> Don't mean to brag but it took the 12 year old me less than an afternoon (armed with a CISCO book) to understand IPv4 syntax/routing/ARP/DHCP + whatever and roll it out to my 2 computers lan. Nothing about that is different for IPv6 for your 2 computer lab. But did you understand how your LAN differs from the internet, how NAT works, all about port-forwards, firewall traversal and why some apps could traverse firewalls (UDP) and some ones not (TCP)? Or did that come later? IPv4 has tons of hidden complexities people conveniently forget exist when they lament how terribly inaccessible IPv6 "really" is.

Arnavion 5y ago

Did you misread the 6s in my comment as 4s? I'm not sure why you're telling me that IPv6 is more complex than IPv4 when my comment said nothing to the contrary.

ipv4idio 5y ago
He is telling you because you come off as a know it all who can figure everything out while at the same time you question why can't other people figure out the same as you can while at their own home labs. Apparently though you couldn't figure out this answer to your obviously self answerable question.
- Arnavion 5y ago
  >who can figure everything out If this is what you got from my comment, it seems you need to read more closely. I listed specifically what I did learn, pointing out how it was not everything but was enough for setting up a LAN.

josteink 5y ago

> Don't mean to brag but it took the 12 year old me less than an afternoon (armed with a CISCO book) to understand IPv4 syntax/routing/ARP/DHCP + whatever and roll it out to my 2 computers lan. Nothing about that is different for IPv6 for your 2 computer lab. But did you understand how your LAN differs from the internet, how NAT works, all about port-forwards, firewall traversal and why some apps could traverse firewalls (UDP) and some ones not (TCP)? Or did that come later? IPv4 has tons of hidden complexities people conveniently forget exist when they lament how terribly inaccessible IPv6 "really" is.