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

source specific routing and /56s #36

Open
dtaht opened this issue Jun 18, 2015 · 1 comment
Open

source specific routing and /56s #36

dtaht opened this issue Jun 18, 2015 · 1 comment

Comments

@dtaht
Copy link

dtaht commented Jun 18, 2015

My external interface gets a /56 (I changed the example script to use table 16 (dhcp))

2601:646:8301:c500::/56 from :: via fe80::22e5:2aff:feb8:14f dev eth2 metric 512 pref medium
2601:646:8301:c500::/56 from 2601:646:8301:c5f0::/60 via fe80::22e5:2aff:feb8:14f dev eth2 proto dhcp metric 512 pref medium

But I only get a "default from" what the local dhcp-pd server could fetch (a /60 in that range)

default from 2601:646:8301:c5f0::/60 via fe80::22e5:2aff:feb8:14f dev eth2 proto dhcp metric 512 pref medium

And then the /56 is just routable internally, but no default until this or some other dhcp-pd enabled server fetches another /60 AND then if it announced it, it would direct traffic back to itself.

shouldn't the "default from" be the entire /56 for the edge gateway? and an interior box not do source specific at all?

@sbyx
Copy link
Member

sbyx commented Jun 19, 2015

There is no way it could know whether it is connected to an internal router doing downstream PD or to the ISP so it assumes the latter.

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

No branches or pull requests

2 participants