Are you on IPv4 or IPv6 (Poll)

somiksomik OG Hostbusters

This is an extension to the thread:
https://lowendspirit.com/discussion/7625/why-are-people-still-using-ipv4

Instead of asking why are people still using it, I want to how many people are on IPv6.

For me, my home router is on IPv4 + IPv6 however all of my servers are on IPv4 only. Is it the same for you?

I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

Are you using IPv6 on any of your devices/router/servers?
  1. Yes, on all mobile devices, home router & servers63 votes
    1. Yes, but only on some home devices & servers
      25.40%
    2. Yes, only on all of my home devices
        9.52%
    3. Yes, only on all of my servers
        4.76%
    4. Yes, only on some of my servers
      11.11%
    5. No, all my home devices and servers run on IPv4
      44.44%
    6. Others (in comments)
        4.76%
«1

Comments

  • Beware, the first "option" when creating the poll is a trap!

  • It is missing "Yes for everything" option

    LumanexAI: Our in-house AI model for free 🚀

  • What a scam poll.

  • Otus9051Otus9051 The Original Freeloader

    You have been fooled by Vanilla.

    youtube.com/watch?v=k1BneeJTDcU

  • tentortentor Provider
    edited April 2024

    Technically, I have IPv6 on all of my devices thanks to VPN. However, no home/mobile connection has native IPv6 connectivity, only servers.

    Check our KVM VPS plans in 🇵🇱 Warsaw, Poland and 🇸🇪 Stockholm, Sweden

  • somiksomik OG Hostbusters

    @wankel said:
    Beware, the first "option" when creating the poll is a trap!

    Damn... I even checked it over to make sure it was ok. Totally missed that. Now I cannot even edit it...

    __> @c1vhosting said:

    It is missing "Yes for everything" option

    Sorry for that.

    @rm_ said:
    What a scam poll.

    :lol:

    @Otus9051 said:
    You have been fooled by Vanilla.

    Lol, yep, you got that right!

    @skhron said:
    Technically, I have IPv6 on all of my devices thanks to VPN. However, no home/mobile connection has native IPv6 connectivity, only servers.

    My home has native IPv6 but only the newer phones/computers support it. None of the IOT devices support IPv6...

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • tentortentor Provider
    edited April 2024

    @somik said: My home has native IPv6 but only the newer phones/computers support it.

    How old is your phone? Wikipedia says IPv6 is supported since Android 4.2 (released 12 years ago)

    Check our KVM VPS plans in 🇵🇱 Warsaw, Poland and 🇸🇪 Stockholm, Sweden

  • somiksomik OG Hostbusters

    @skhron said:

    @somik said: My home has native IPv6 but only the newer phones/computers support it.

    How old is your phone? Wikipedia says IPv6 is supported since Android 4.2 (released 12 years ago)

    I am not sure if it is the phone OS customization, but one of the chinese phones in the house do not support IPv6. All samsung/iPhones phones we use supports IPv6.

    I still have not figured out how to enable IPv6 on any of the Linux home-servers I run in my house (all ubuntu/debian based), including my proxmox server...

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • tentortentor Provider

    @somik said: I still have not figured out how to enable IPv6 on any of the Linux home-servers I run in my house (all ubuntu/debian based), including my proxmox server...

    Unless you use custom kernel with IPv6 support disabled or sysctl -w net.ipv6.conf.all.disable_ipv6=1, it is enabled.

    Check our KVM VPS plans in 🇵🇱 Warsaw, Poland and 🇸🇪 Stockholm, Sweden

  • somiksomik OG Hostbusters
    edited April 2024

    @skhron said:

    @somik said: I still have not figured out how to enable IPv6 on any of the Linux home-servers I run in my house (all ubuntu/debian based), including my proxmox server...

    Unless you use custom kernel with IPv6 support disabled or sysctl -w net.ipv6.conf.all.disable_ipv6=1, it is enabled.

    IPv6 is enabled, but I cant get them to request a IP from my router... The windows PC does it just fine. So does my raspberry Pi, but proxmox config for IPv6 still confuses me and any LXC container running on proxmox can get a IPv4 ip from the router but not any IPv6 IP...

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • tentortentor Provider

    Might be misconfiguration of firewall I believe

    Check our KVM VPS plans in 🇵🇱 Warsaw, Poland and 🇸🇪 Stockholm, Sweden

  • somiksomik OG Hostbusters

    @skhron said:
    Might be misconfiguration of firewall I believe

    No, it's probably a misconfiguration on the Proxmox network config itself. It picked up the IPv4 from the DHCP but can't do the same for IPv6 and I got no idea how to configure it properly... Last time I tried it, had to revert it cause it was no longer able to connect to the internet...

    Any VM on the KVM is able to get a IPv6 just fine, so some weird configuration miss-out on my end.

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • edited April 2024

    My Proxmox LXC and KVM gets IPv6 from my router just fine...

    DM us for private tracker invite.

  • Otus9051Otus9051 The Original Freeloader

    All of my devices at home get v6 via AS55836, and Airtel was good enough to provide v6 with mobile networks, so there's that.

    youtube.com/watch?v=k1BneeJTDcU

  • somiksomik OG Hostbusters

    @terrorgen said:
    My Proxmox LXC and KVM gets IPv6 from my router just fine...

    Please share your configuration! I could not even get my proxmox server to pick up my ipv6...

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • somiksomik OG Hostbusters

    @Otus9051 said:
    All of my devices at home get v6 via AS55836, and Airtel was good enough to provide v6 with mobile networks, so there's that.

    India? Wow! They are improving fast!

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • edited April 2024

    @somik said: India? Wow! They are improving fast!

    "According to Google's statistics, India has reached an IPv6 adoption level of around 68.94% in January 2023. As of 2022, APNIC placed India at more than 75% preferring IPv6.

    Countries including France, Germany and India now run the majority of their traffic to Google over IPv6, with other countries including the United States, Brazil and Japan approaching 50%."

    Source: https://en.wikipedia.org/wiki/IPv6_deployment

  • For Gaming, Windows machine runs IPv4 only.
    Otherwise Dualstack if available.

  • I run ipv6 on everything and some, but not all, of my servers are dual stacked with ip4 as well. Couldn't really find an option in the poll that matches that.

  • @somik said:

    @terrorgen said:
    My Proxmox LXC and KVM gets IPv6 from my router just fine...

    Please share your configuration! I could not even get my proxmox server to pick up my ipv6...

    Make sure your proxmox's and the lxc's net.ipv6.conf.all.disable_ipv6 has the value 0.
    set your lxc's IPv6 address to be SLAAC.

    DM us for private tracker invite.

  • @somik said: why are people still using it

    Because we can afford premium, IPv4-only connectivity.

    • IPv6 is soy milk, IPv4 is rich full cream milk;
    • IPv6 is margarine, IPv4 is dairy butter;
    • IPv6 is instant noodles, IPv4 is pasta Bolognaise;
    • IPv6 is roasted cockroaches, IPv4 is Wagyu steak.

    VDS & StorageBudget AMD EPYC VDS (ref) from $4/m / Big HDD VPS (ref) from $2/TB/mo / EPYC/Gold/Platinum dedis (ref) w/ GPU support

  • @DataRecovery said:

    @somik said: why are people still using it

    Because we can afford premium, IPv4-only connectivity.

    • IPv6 is soy milk, IPv4 is rich full cream milk;
    • IPv6 is margarine, IPv4 is dairy butter;
    • IPv6 is instant noodles, IPv4 is pasta Bolognaise;
    • IPv6 is roasted cockroaches, IPv4 is Wagyu steak.

    premium only exists in your mind.

    DM us for private tracker invite.

  • @terrorgen said:

    @DataRecovery said:

    @somik said: why are people still using it

    Because we can afford premium, IPv4-only connectivity.

    • IPv6 is soy milk, IPv4 is rich full cream milk;
    • IPv6 is margarine, IPv4 is dairy butter;
    • IPv6 is instant noodles, IPv4 is pasta Bolognaise;
    • IPv6 is roasted cockroaches, IPv4 is Wagyu steak.

    premium only exists in your mind.

    I think he means to say: "Like it or not, but IPv6 is healthier for you!"

  • Yes, only on all of my home devices and only on some of my servers
    And the most powerful of the VPSs are using ipv9

  • @DataRecovery said:

    @somik said: why are people still using it

    Because we can afford premium, IPv4-only connectivity.

    • IPv6 is soy milk, IPv4 is rich full cream milk;
    • IPv6 is margarine, IPv4 is dairy butter;
    • IPv6 is instant noodles, IPv4 is pasta Bolognaise;
    • IPv6 is roasted cockroaches, IPv4 is Wagyu steak.

  • somiksomik OG Hostbusters

    @Mumbly said:

    @somik said: India? Wow! They are improving fast!

    "According to Google's statistics, India has reached an IPv6 adoption level of around 68.94% in January 2023. As of 2022, APNIC placed India at more than 75% preferring IPv6.

    Countries including France, Germany and India now run the majority of their traffic to Google over IPv6, with other countries including the United States, Brazil and Japan approaching 50%."

    Source: https://en.wikipedia.org/wiki/IPv6_deployment

    Singapore's statistics are not that good yet...
    https://ipv6-test.com/stats/country/SG

    @rcy026 said:
    I run ipv6 on everything and some, but not all, of my servers are dual stacked with ip4 as well. Couldn't really find an option in the poll that matches that.

    My dedicated server DC do not support IPv6 for my server...

    @DataRecovery said:

    @somik said: why are people still using it

    Because we can afford premium, IPv4-only connectivity.

    • IPv6 is soy milk, IPv4 is rich full cream milk;
    • IPv6 is margarine, IPv4 is dairy butter;
    • IPv6 is instant noodles, IPv4 is pasta Bolognaise;
    • IPv6 is roasted cockroaches, IPv4 is Wagyu steak.

    Explains why people love IPv6 :lol:

    As for me, I'll take my dairy butter grilled Wagyu steak with a side of rich full cream milk shake :D

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • somiksomik OG Hostbusters

    @terrorgen said:

    @somik said:

    @terrorgen said:
    My Proxmox LXC and KVM gets IPv6 from my router just fine...

    Please share your configuration! I could not even get my proxmox server to pick up my ipv6...

    set your lxc's IPv6 address to be SLAAC.

    This was the issue. I did not use SLAAC but was trying with DHCP. Once I assigned a static IPv6 to the proxmox node and set the LXC to SLAAC and rebooted the container, it immediately got the IPv6 address!

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • @somik said:

    @terrorgen said:

    @somik said:

    @terrorgen said:
    My Proxmox LXC and KVM gets IPv6 from my router just fine...

    Please share your configuration! I could not even get my proxmox server to pick up my ipv6...

    set your lxc's IPv6 address to be SLAAC.

    This was the issue. I did not use SLAAC but was trying with DHCP. Once I assigned a static IPv6 to the proxmox node and set the LXC to SLAAC and rebooted the container, it immediately got the IPv6 address!

    You probably don't have DHCPv6 set up. Which is why you are not getting an address via DHCP.

    SLAAC does not require DHCPv6. Rather, it takes the router advertisement containing prefix information and its own MAC address to formulate an IPv6 address.

    Glad I can help!

    DM us for private tracker invite.

  • somiksomik OG Hostbusters

    @terrorgen said:

    @somik said:

    @terrorgen said:

    @somik said:

    @terrorgen said:
    My Proxmox LXC and KVM gets IPv6 from my router just fine...

    Please share your configuration! I could not even get my proxmox server to pick up my ipv6...

    set your lxc's IPv6 address to be SLAAC.

    This was the issue. I did not use SLAAC but was trying with DHCP. Once I assigned a static IPv6 to the proxmox node and set the LXC to SLAAC and rebooted the container, it immediately got the IPv6 address!

    You probably don't have DHCPv6 set up. Which is why you are not getting an address via DHCP.

    SLAAC does not require DHCPv6. Rather, it takes the router advertisement containing prefix information and its own MAC address to formulate an IPv6 address.

    Glad I can help!

    Ya, forgot that native IPv6 support do not need a DHCPv6. As most other devices were picking up IPv6 automatically, it was my assumption that it was DHCP and not auto-self-assigned native IPv6.

    Again, thank you very much! This had been bugging me for over 2 years now that my server could not get IPv6 even though my ISP provides it!

    Now the new issue is my internal servers are accessible over the internet without going through my router's NAT firewall... Time to up the security on all! :(

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • @somik said:

    Now the new issue is my internal servers are accessible over the internet without going through my router's NAT firewall... Time to up the security on all! :(

    It's not NAT but it should still pass the firewall. Default to deny becomes more important than ever when you run ipv6. :smile:

  • edited April 2024

    @somik said: My dedicated server DC do not support IPv6 for my server...

    Get yourself a server in a semi-decent DC. We are in 21st century. Don't skimp on yourself.

  • YmpkerYmpker OG
    edited April 2024

    Our home internet has DSLite (shared ipv4 and own ipv6 or whatever it was).
    "DualStack Lite"

  • somiksomik OG Hostbusters

    @Mumbly said:

    @somik said: My dedicated server DC do not support IPv6 for my server...

    Get yourself a server in a semi-decent DC. We are in 21st century. Don't skimp on yourself.

    I would but I like paying $10 per month for a dedicated server :lol:

    Anyway, I do not use it for anything other then offsite backups so doesn't matter if it has IPv4 only network :)

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • Then you're not so "premium" as you want to believe. But don't worry, throughout history, there have always been retrogressive individuals who objected to changes, progress, and so on.

    @somik said:

    @DataRecovery said:

    @somik said: why are people still using it

    Because we can afford premium, IPv4-only connectivity.

    • IPv6 is soy milk, IPv4 is rich full cream milk;
    • IPv6 is margarine, IPv4 is dairy butter;
    • IPv6 is instant noodles, IPv4 is pasta Bolognaise;
    • IPv6 is roasted cockroaches, IPv4 is Wagyu steak.

    Explains why people love IPv6 :lol:

    As for me, I'll take my dairy butter grilled Wagyu steak with a side of rich full cream milk shake :D

  • somiksomik OG Hostbusters

    @Mumbly said:
    Then you're not so "premium" as you want to believe. But don't worry, throughout history, there have always been retrogressive individuals who objected to changes, progress, and so on.

    They say you want what you don't have. Singapore only have processed butter and low fat milk on sale. So I want it cause I can't get it :lol:

    As for IPv6, I do not see how it affects regular users. It is not like SSL which was implemented for a genuine security concern. IPv6 will eventually replace IPv4 (unless something better comes along). So debating about it is useless :)

    This thread is about checking what percentage of people on LES are on IPv6 and given nearly 50% is still on IPv4, it aligns well with the worldwide IPv6 adoption statistics.

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • @somik said:
    This thread is about checking what percentage of people on LES are on IPv6 and given nearly 50% is still on IPv4, it aligns well with the worldwide IPv6 adoption statistics.

    I like the initiative, but the poll is very confusing. It mixes "home devices" and servers, all and any, and makes it basically impossible to correctly answer the question. None of the alternatives correctly describes my situation.
    I would assume that a majority of users are on both ip4 and ipv6 so asking "are you on ip4 or ipv6?" makes it a logical fallacy.

    A simple "Do you use ipv6 (yes/no)" question would have been enough.

  • Otus9051Otus9051 The Original Freeloader

    @Ympker said:
    Our home internet has DSLite (shared ipv4 and own ipv6 or whatever it was).
    "DualStack Lite"

    Same thing for my FTTH by AS55836.
    They probably assign a /56 to each router, maybe, didnt test it properly.

    youtube.com/watch?v=k1BneeJTDcU

  • somiksomik OG Hostbusters

    @rcy026 said:

    @somik said:
    This thread is about checking what percentage of people on LES are on IPv6 and given nearly 50% is still on IPv4, it aligns well with the worldwide IPv6 adoption statistics.

    I like the initiative, but the poll is very confusing. It mixes "home devices" and servers, all and any, and makes it basically impossible to correctly answer the question. None of the alternatives correctly describes my situation.
    I would assume that a majority of users are on both ip4 and ipv6 so asking "are you on ip4 or ipv6?" makes it a logical fallacy.

    A simple "Do you use ipv6 (yes/no)" question would have been enough.

    Lets say my mobile telco uses IPv6. So i can say "yes" to using IPv6 even if my home network and all of my servers are on IPv4. Similarly, if one of my vps is on IPv6, even if the remaining 20+ are on IPv4 / NAT, I am technically using IPv6 :lol:

    The poll is not perfect, but it does give a bit more granularity to catch some of the common cases. If this does not apply to the user, they are asked to select other and post in the thread (like in your case :) )

    @Otus9051 said:

    @Ympker said:
    Our home internet has DSLite (shared ipv4 and own ipv6 or whatever it was).
    "DualStack Lite"

    Same thing for my FTTH by AS55836.
    They probably assign a /56 to each router, maybe, didnt test it properly.

    That's 4,722,366,482,869,645,213,696 IPs...

    I only get a /64 from my ISP which is only 18,446,744,073,709,551,616 IPs...

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • You need /64 to get SLAAC to work though.

    DM us for private tracker invite.

  • somiksomik OG Hostbusters

    @terrorgen said:
    You need /64 to get SLAAC to work though.

    That explains why they issue /64 most of the time. Then again, when you have 3.4×10 pow(38) addresses to play with, giving every client a 1.8 x 10 pow(19) you will still have too many IPs left over...

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • edited April 2024

    That perspective is entirely incorrect when considering IPv6. IPv6 differs from IPv4, don't look at it through the lens of old IPv4 perspectives.
    Its design differs fundamentally. It's not about the number of individual /128 addresses or if you can't switch completely yet have in your mind something like /64 = one IPv4 address for easier transition.
    You're not getting from your ISP 18,446,744,073,709,551,616 IPs, but one /64. Work with that.

    That's also how the internet sees your IPv6. Do shit and your /64 will get banned, blacklisted, etc.

  • tentortentor Provider

    @Mumbly said:
    That perspective is entirely incorrect when considering IPv6. IPv6 differs from IPv4, don't look at it through the lens of old IPv4 perspectives.
    Its design differs fundamentally. It's not about the number of individual /128 addresses or if you can't switch completely yet have in your mind something like /64 = one IPv4 address for easier transition.
    You're not getting from your ISP 18,446,744,073,709,551,616 IPs, but one /64. Work with that.

    That's also how the internet sees your IPv6. Do shit and your /64 will get banned, blacklisted, etc.

    Just adding Spamhaus FAQ as a reference: https://www.spamhaus.org/faqs/combined-spam-sources-css/#css-how-handle-ipv6

    CSS lists /64 subnets of IPv6 addresses.

    • IPv6: CSS lists “/64” or larger CIDR blocks.
      • A very large number of spam-emitting IPv6 addresses in different /64 blocks within the same network could cause listings to extend to larger blocks.
      • Without such extensions/aggregations, the IPv6 zone size could become unworkably large.
      • Various strategies used by spammers to game the system are made much more difficult by the use of aggregated blocks rather than single “/128” IPs.

    Check our KVM VPS plans in 🇵🇱 Warsaw, Poland and 🇸🇪 Stockholm, Sweden

  • @Mumbly said:
    That perspective is entirely incorrect when considering IPv6. IPv6 differs from IPv4, don't look at it through the lens of old IPv4 perspectives.
    Its design differs fundamentally. It's not about the number of individual /128 addresses or if you can't switch completely yet have in your mind something like /64 = one IPv4 address for easier transition.
    You're not getting from your ISP 18,446,744,073,709,551,616 IPs, but one /64. Work with that.

    That's also how the internet sees your IPv6. Do shit and your /64 will get banned, blacklisted, etc.

    This is a good point.
    I try to think of it as "a /64 is an endpoint". An endpoint can be a single node, a local network, a dc or whatever, but its still a single endpoint, it's one "unit" or whatever you prefer to call it.
    This is why you should never subnet smaller than /64 in ipv6 unless you really know what you are doing, it is highly frowned upon and most carriers refuses (rightfully so) to route anything smaller than /64.

    I think this is one of the hurdles for ipv6 adoption, a lot of people simply looks at it as a ip4 with more characters which takes a way a lot of the fundamental design improvements and advantages it actually has over ip4.

  • somiksomik OG Hostbusters

    @rcy026 said:

    @Mumbly said:
    That perspective is entirely incorrect when considering IPv6. IPv6 differs from IPv4, don't look at it through the lens of old IPv4 perspectives.
    Its design differs fundamentally. It's not about the number of individual /128 addresses or if you can't switch completely yet have in your mind something like /64 = one IPv4 address for easier transition.
    You're not getting from your ISP 18,446,744,073,709,551,616 IPs, but one /64. Work with that.

    That's also how the internet sees your IPv6. Do shit and your /64 will get banned, blacklisted, etc.

    This is a good point.
    I try to think of it as "a /64 is an endpoint". An endpoint can be a single node, a local network, a dc or whatever, but its still a single endpoint, it's one "unit" or whatever you prefer to call it.
    This is why you should never subnet smaller than /64 in ipv6 unless you really know what you are doing, it is highly frowned upon and most carriers refuses (rightfully so) to route anything smaller than /64.

    I think this is one of the hurdles for ipv6 adoption, a lot of people simply looks at it as a ip4 with more characters which takes a way a lot of the fundamental design improvements and advantages it actually has over ip4.

    Damn, so it's like 1234:5678:9abc:de01:: is just 1 IP while anything expanded from there is the sub IP/routes under that one ip...

    So basically instead of using NAT, all devices in one client are put on the internet through that one block of /64 IP while each device gets a /128 part of that IP block?

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • Otus9051Otus9051 The Original Freeloader

    @somik said:

    @Otus9051 said:

    @Ympker said:
    Our home internet has DSLite (shared ipv4 and own ipv6 or whatever it was).
    "DualStack Lite"

    Same thing for my FTTH by AS55836.
    They probably assign a /56 to each router, maybe, didnt test it properly.

    That's 4,722,366,482,869,645,213,696 IPs...

    I only get a /64 from my ISP which is only 18,446,744,073,709,551,616 IPs...

    I was wrong, they do only provide a /64
    I think the /56 was a one time terrible mistake they did lmaO

    youtube.com/watch?v=k1BneeJTDcU

  • location, indonesia

    home 1, ftth as7713 : native ipv6 + ipv4
    home 2, ftth as7713 : native ipv6 + ipv4
    home 3, ftth local isp : ipv4 only
    work , ftth as17451 : native ipv6 + ipv4
    mobile 1, xl axiata : native ipv6 + ipv4
    mobile 2, indosat ooredoo : native ipv6 + ipv4

  • @somik said:

    @rcy026 said:

    @Mumbly said:
    That perspective is entirely incorrect when considering IPv6. IPv6 differs from IPv4, don't look at it through the lens of old IPv4 perspectives.
    Its design differs fundamentally. It's not about the number of individual /128 addresses or if you can't switch completely yet have in your mind something like /64 = one IPv4 address for easier transition.
    You're not getting from your ISP 18,446,744,073,709,551,616 IPs, but one /64. Work with that.

    That's also how the internet sees your IPv6. Do shit and your /64 will get banned, blacklisted, etc.

    This is a good point.
    I try to think of it as "a /64 is an endpoint". An endpoint can be a single node, a local network, a dc or whatever, but its still a single endpoint, it's one "unit" or whatever you prefer to call it.
    This is why you should never subnet smaller than /64 in ipv6 unless you really know what you are doing, it is highly frowned upon and most carriers refuses (rightfully so) to route anything smaller than /64.

    I think this is one of the hurdles for ipv6 adoption, a lot of people simply looks at it as a ip4 with more characters which takes a way a lot of the fundamental design improvements and advantages it actually has over ip4.

    Damn, so it's like 1234:5678:9abc:de01:: is just 1 IP while anything expanded from there is the sub IP/routes under that one ip...

    So basically instead of using NAT, all devices in one client are put on the internet through that one block of /64 IP while each device gets a /128 part of that IP block?

    Technically that should work (as long as you get the arp stuff right) but if you are to be true to the rfc's, no, that's not how you should do it. Each customer should actually get a /48 or /56. :smile:

    The correct way would be that the ISP assigns a /48 or /56 to the customers router. The customers router then splits this into /64's. The reason for this is that SLAAC, the automatic assigning of ipv6 addresses, only works in /64 networks so if the devices on the "inside" should be able to use SLAAC they need to be in a /64 network.
    SLAAC is a multiple step process but basically it boils down to the clients on the network using their own mac-adress combined with the network prefix to calculate their own ipv6 adress. There is no server that assigns addresses like in dhcp, the clients simply figures out their ip and gateway on their own.

    Google SLAAC and EUI-64 if you want to read up on it, ipv6 gets really fun once you start to understand it. :smile:
    https://www.networkacademy.io/ccna/ipv6/stateless-address-autoconfiguration-slaac is a good start.

  • I am on Crack v10

    The Yeti has left the building.

  • IPv6 adoption here is inane, I setup a Wireguard VPN on all my devices in order to have IPv6 connectivity.

  • somiksomik OG Hostbusters

    @shell said:
    location, indonesia

    home 1, ftth as7713 : native ipv6 + ipv4
    home 2, ftth as7713 : native ipv6 + ipv4
    home 3, ftth local isp : ipv4 only
    work , ftth as17451 : native ipv6 + ipv4
    mobile 1, xl axiata : native ipv6 + ipv4
    mobile 2, indosat ooredoo : native ipv6 + ipv4

    That's almost fulll IPv6 adoption for your country. Weird how Indonesia and India are leading IPv6 adoption!

    @rcy026 said:

    @somik said:

    Damn, so it's like 1234:5678:9abc:de01:: is just 1 IP while anything expanded from there is the sub IP/routes under that one ip...

    So basically instead of using NAT, all devices in one client are put on the internet through that one block of /64 IP while each device gets a /128 part of that IP block?

    Technically that should work (as long as you get the arp stuff right) but if you are to be true to the rfc's, no, that's not how you should do it. Each customer should actually get a /48 or /56. :smile:

    The correct way would be that the ISP assigns a /48 or /56 to the customers router. The customers router then splits this into /64's. The reason for this is that SLAAC, the automatic assigning of ipv6 addresses, only works in /64 networks so if the devices on the "inside" should be able to use SLAAC they need to be in a /64 network.
    SLAAC is a multiple step process but basically it boils down to the clients on the network using their own mac-adress combined with the network prefix to calculate their own ipv6 adress. There is no server that assigns addresses like in dhcp, the clients simply figures out their ip and gateway on their own.

    Google SLAAC and EUI-64 if you want to read up on it, ipv6 gets really fun once you start to understand it. :smile:
    https://www.networkacademy.io/ccna/ipv6/stateless-address-autoconfiguration-slaac is a good start.

    Ya, my routers get /64 IP from the network provider. Since I got 3 lines, I got 3 blocks of /64 IPv6, one for each of my routers. Bookmarked the url. Will go through it tomorrow.

    @AuroraZero said:
    I am on Crack v10

    It is not good to be on crack...

    @mfs said:
    IPv6 adoption here is inane, I setup a Wireguard VPN on all my devices in order to have IPv6 connectivity.

    If IPv6 connects all devices over the internet, is there a need to setup wireguard to connect the devices to one another?

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

Sign In or Register to comment.