Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#461 - Mass Cascade of DHCP ULA Prefix Assignments with DHCP-PD #5496

Open
openwrt-bot opened this issue Feb 4, 2017 · 3 comments
Open

FS#461 - Mass Cascade of DHCP ULA Prefix Assignments with DHCP-PD #5496

openwrt-bot opened this issue Feb 4, 2017 · 3 comments
Labels

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Feb 4, 2017

EricLuehrsen:

Here is one that gets a bit ugly. Lets say we chain a bunch of LEDE based routers together. Lets also enable a nice numbering system in IP4 and IP6. Lets enable DHCP-PD through the network, because our ISP was generous with a /56. The IP4 is only static and is easy to control, see table below. Its tedious, but easy. The problem is in parallel the IP6 addresses compound in the ULA region. Each router DHCP-PD the ULA above it, and gets its own ULA from Global settings in Network UCI. There seems no easy way to control this mass cascade of ULA, and get good fail over.

Ideal Requirements:
(1) If router above is unavailable, then next tier router uses ULA (network global UCI) to begin assigning addresses to clients and subnets.
(2) If router above is available, then next tier router expires its self-generated ULA and subnets, and gets ULA from delegation above to then re-delegate to subnets.
(*) Bonus: make some parts optional

IP4 WAN Name Serves Subnet
(NAT) Router-1 172.16.0.1/24
172.16.0.2 Router-2A 172.17.0.1/24
172.17.0.2 Router-3A 172.24.0.1/24
172.17.0.3 Router-3B 172.25.0.1/24
172.16.0.3 Router-2B 172.18.0.1/24

IP6 Roots Name Serves Subnet Delegates Subnet
2001:db8/56 Router-1 2001:db8::1/64 2001:db8:0:10/60
fd00:ac10/48 fd00:ac10::1/64 2001:db8:0:20/60
fd00:ac10:0:10/60
fd00:ac10:0:20/60

2001:db8:0:10/60 Router-2A 2001:db8:0:10::1/64 2001:db8:0:14/62
fd00:ac10:0:10/60 fd00:ac10:0:10::1/64 2001:db8:0:18/62
fd00:ac11/48 fd00:ac11::1/64 fd00:ac10:0:14/62
fd00:ac10:0:18/62
fd00:ac11:0:14/62
fd00:ac11:0:18/62

  • please, i don't want to type more. see how the ULA prefixes just keep multiplying.
    ** '172.16' = 'ac10'
@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Feb 4, 2017

EricLuehrsen:

... and flyspray just reformatted my table into garbage. fantastic :-/

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Feb 4, 2017

dtaht:

This is no doubt related to the other issues I'd had with dhcp-pd....

I gave up on pd entirely for now.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Apr 4, 2017

cfriedt:

Ahh... so it isn't just me.

I've come to believe that my ULA ip's are not getting assigned correctly on my subnet because of dhcpv6-pd.

E.g. On one client, I expect to have

192.168.1.12 / fd27:fcc0:fa2a::c

but the host is getting assigned

192.168.1.12 / fd27:fcc0:fa2a:10bc:c89e:b72b:f675

Dnsmasq actually resolves properly to fd27:fcc0:fa2a::c which is both reassuring and frustrating.

Even having a bit of information about the best way to debug the "automagically" generated init scripts / lua code (for luci) would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant