Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DHCPv6-PD – First Steps

sha256.net

Post reply on HN
Print view View original

81–90 of 91 posts

Re: DHCPv6-PD – First Steps

#81

Post by yjftsjthsd-h »

hairyplanter wrote: post #80
yjftsjthsd-h wrote: post #37

Earlier quoted context omitted.

I guess I'll ask here... How do I learn this? I'm comfortable with IPv4, including DHCP, DNS, VPNs, NAT, whatever. I'd like to be able to set up a v6 network[0] in whatever is the Correct and sane way. Is there a good end-to-end tutorial to set it all up by hand and explain what all these things (RA/DHCPv6/fe80::/ULA/etc.) are and how to use them or why not to use them? [0] Ideally pure v6 if possible; I think there'…

I wrote one: https://news.ycombinator.com/item?id=40603777

Thank you; that helped:)

Re: DHCPv6-PD – First Steps

#82

Post by tssva »

robhlt wrote: post #22
tssva wrote: post #4

Earlier quoted context omitted.

I have never been able to get DHCPv6PD working with systemd-networkd on my Verizon Fios connection at home. I have using other software.

It's working on my fios connection, but I remember that wasn't always the case. Verizon may have changed something recently or the issue was fixed in a recent systemd release. My config looks like this with systemd 255: wan.network: [Network] DHCP=yes IPv6AcceptRA=yes IPForward=yes [IPv6AcceptRA] UseDNS=no DHCPv6Client=yes [DHCPv6] UseDNS=no UseHostname=no UseDomains=no PrefixDelegationHint=::/56 [Link] RequiredForOn…

I haven't tried it in about 6 months using whatever version was packaged with Ubuntu 22.04. My configuration was basically the same as yours. systemd-networkd seemed to always be a moving target as far as configuration syntax but mine was mostly the same as yours syntactically and functionally the same.

It is mute now. I deployed a new Ubiquiti network including cameras about 6 months ago resulting in the linux router/firewall being replaced with a Dream Machine Pro.

Re: DHCPv6-PD – First Steps

#83

Post by FireBeyond »

lloeki wrote: post #35
hairyplanter wrote: post #30

Earlier quoted context omitted.

> or just bite the bullet and use ULA. This is the proper ipv6 solution. With ipv6, one ethernet interface is _supposed_ to have multiple addresses. You wouldn't want your lan routing to stop working when your ISP goes down, right? So configure your internal DNS with ULA (which should be stable for each machine for a given prefix, even with SLAAC) and be done with it, much like internal DNS using private addresses in…

> the ISPs want a stateless solution, so customers get a dynamic prefix. Maintaining the same prefix across power outages needs a stateful solution, so only business plans offer them for an extra fee, much like static ipv4 addresses. I'm surprised based on my experience: in 15 years of residential IPv6 usage I've always had the same IPv6 prefix (for a given ISP contract of course), even for those ISPs that insisted o…

> in 15 years of residential IPv6 usage

Out of curiosity, what residential ISPs were handing out IPv6 15 years ago?

Re: DHCPv6-PD – First Steps

#84

Post by ac29 »

FireBeyond wrote: post #83
lloeki wrote: post #35

Earlier quoted context omitted.

> the ISPs want a stateless solution, so customers get a dynamic prefix. Maintaining the same prefix across power outages needs a stateful solution, so only business plans offer them for an extra fee, much like static ipv4 addresses. I'm surprised based on my experience: in 15 years of residential IPv6 usage I've always had the same IPv6 prefix (for a given ISP contract of course), even for those ISPs that insisted o…

> in 15 years of residential IPv6 usage Out of curiosity, what residential ISPs were handing out IPv6 15 years ago?

Comcast started rolling out IPv6 in 2011

Re: DHCPv6-PD – First Steps

#85

Post by hamandcheese »

mikepavone wrote: post #24
hamandcheese wrote: post #12

Earlier quoted context omitted.

Did Sonic start offering native IPv6? Last I looked, it was only covered via tunnel only.

They turned on native IPv6 end of last year, at least in some areas (including Berkeley where I live). You wouldn't know it from their help pages, but there are some post in the forum to that effect.

I checked and I indeed have an ipv6 assigned to my router! Now I just need to figure out how to make it request a prefix.

Re: DHCPv6-PD – First Steps

#86

Post by lloeki »

FireBeyond wrote: post #83
lloeki wrote: post #35

Earlier quoted context omitted.

> the ISPs want a stateless solution, so customers get a dynamic prefix. Maintaining the same prefix across power outages needs a stateful solution, so only business plans offer them for an extra fee, much like static ipv4 addresses. I'm surprised based on my experience: in 15 years of residential IPv6 usage I've always had the same IPv6 prefix (for a given ISP contract of course), even for those ISPs that insisted o…

> in 15 years of residential IPv6 usage Out of curiosity, what residential ISPs were handing out IPv6 15 years ago?

Can't recall the exact timeline but:

- I think Free had it since forever and a half, although IIRC it was some weird 6rd or something. Freebox v6 (2011) for sure had it, v5 (2006) may had supported it from the start and for sure supported it down the road, I think v4 could have had it too through an update at least but honestly can't recall.

- Orange in France had a public opt-in experiment for native IPv6 over ADSL to which I enrolled at the time.

- Then I lost IPv6 because I moved to a cable operator which did not support DOCSIS 3.0 (a requirement for IPv6 on cable connections) at the time.

- After that FTTH rolled out and basically every ISP provided native IPv6 on it from the get go.

Non-biz IPv6 support in France is sitting in the ballpark of 99% these days, both residential and mobile. National regulations helped a lot. Residentially there has been a huge plan towards a national FTTH rollout, including in remote areas (the idea being that no one should be cast aside of a full speed internet); this plan also had specific requirements to enforce competition to prevent regional or local monopolistic situations such as the one that historically happened with cable operators (or like the ones I keep hearing about in the US). For mobile it was simpler: you want a radio license for 5G? you have to support IPv6, or else.

Re: DHCPv6-PD – First Steps

#87

Post by simoncion »

semi wrote: post #77
simoncion wrote: post #58

Earlier quoted context omitted.

Homie likes to pretend to overcomplicate things. Check the comment history, this rant isn't new. And yeah, folks need to understand that ULA addresses are functionally equivalent to RFC 1918 addresses, and ask themselves why they'd expect an ISP who charges extra for an unchanging globally-routable IPv4 address to give you an unchanging globally-routable IPv6 prefix for free.

id assume those unchanging ipv4 addresses are not shared and natted with other customs and thus charging for them makes sense as you're consuming a limited resource they are paying for. That's not the same for not changing an ipv6 address

> id assume those unchanging ipv4 addresses are not shared and natted with other customs...

Over the last several decades of me having residential Internet service from a variety of ISPs here in the US, I've never had an IPv4 address that was not globally-accessible. Relatedly, I've never had a guaranteed-static IPv4 address, but I COULD get one if I paid the ISP additional money.

I understand that in other regions of the world NOT being behind CGN is not guaranteed.

> That's not the same for not changing an ipv6 address

Hopefully you now understand the context in which I made my remarks. In the world that I (and many other folks) live in, I get one globally-accessible, but definitely-not-static IPv4 address.

Re: DHCPv6-PD – First Steps

#88

Post by simoncion »

ninkendo wrote: post #67
simoncion wrote: post #59

Earlier quoted context omitted.

> ...they don’t drop the old one until the lifetime expires... That's a configuration problem on your end. Your border router needs to notice that it's being instructed to switch delegated prefixes and instruct radvd (or whatever route advertising daemon it's using) to advertise the now-defunct prefixes with a zero lifetime just before or just as you're advertising the new prefixes. With this information, devices on…

rtadvd does support advertising old prefixes with zero lifetime to rescind them. rad does not. I’ll let you guess what daemon is deprecated, and what daemon is the new one you’re supposed to use in OpenBSD. https://undeadly.org/cgi?action=article;sid=20180724072205

[flagged]

Re: DHCPv6-PD – First Steps

#89

Post by ninkendo »

simoncion wrote: post #88
ninkendo wrote: post #67

Earlier quoted context omitted.

rtadvd does support advertising old prefixes with zero lifetime to rescind them. rad does not. I’ll let you guess what daemon is deprecated, and what daemon is the new one you’re supposed to use in OpenBSD. https://undeadly.org/cgi?action=article;sid=20180724072205

[flagged]

Oh just fuck right off. You’re already following me around from thread to thread calling me names and now you’re saying I’m using “bad software” for using the built-in, recommended router advertisement daemon on the operating system that has historically always been the absolute best in class at IPv6. You’re being argumentative, you won’t admit when you’re wrong, you treat me like an idiot; in short, you’re a fucking troll. Stop posting.

Re: DHCPv6-PD – First Steps

#90

Post by simoncion »

ninkendo wrote: post #89
simoncion wrote: post #88

Earlier quoted context omitted.

[flagged]

Oh just fuck right off. You’re already following me around from thread to thread calling me names and now you’re saying I’m using “bad software” for using the built-in, recommended router advertisement daemon on the operating system that has historically always been the absolute best in class at IPv6. You’re being argumentative, you won’t admit when you’re wrong, you treat me like an idiot; in short, you’re a fucking…

Ah. Apologies. With the benefit of hindsight, I can see how my "Oh, that's sad." comment could be misconstrued.

My intention here was to say that the fact that the 'rad' software fails to advertise prefixes with a zero lifetime is sad. That's like basic, essential functionality and it's always sad when software fails to implement basic, essential functionality.

My intention was NOT to assert that your configuration (or -worse- you, yourself) was sad or whatever.

> ...now you’re saying I’m using “bad software” for using the built-in, recommended router advertisement daemon...

Yes? It's possible for the recommended thing to be bad software. If you haven't discovered this, you DEFINITELY will as time goes on.

Post reply on HN